Your own keys (BYOK)
Bring your own key (BYOK): connect API keys from your own provider accounts. Providers bill you directly, and bisibility adds no markup to that usage.
Explore BYOKKeep the installation and your research history on infrastructure you control.
Keep saved research and ranking history in your own database, under your own retention rules.
Decide where the application runs and who can reach it.
Choose your provider accounts and checking schedules, so you control data spend.
Follow the production self-hosting guide to configure the application, database, secrets and backups.
Add a supported provider account and set a budget. Choose coverage for your competitor research and rank checks.
Build a shortlist of keyword ideas. When you publish a page, add its keywords to tracking and review the ranking history.
Running the instance: hosting, configuration, updates, backups, security and availability. Scheduled checks also need the worker and Temporal.
The software has no license fee under AGPL-3.0. You pay for your infrastructure, your maintenance time and the provider API usage your research and rank checks need.
Your database, saved research and ranking history stay on your infrastructure. Research and rank checks call external providers, so those requests and their parameters leave your server.
Follow the self-hosting guide in the documentation. It covers Docker setup, configuration, secrets and backups. You can evaluate the local demo with synthetic data before connecting a provider.
BYOK and Credits share one Cloud subscription. You can use your own keys, credits, or both in the same account. Self-hosting runs on your infrastructure with your own provider keys.
Bring your own key (BYOK): connect API keys from your own provider accounts. Providers bill you directly, and bisibility adds no markup to that usage.
Explore BYOKStart research without opening your own provider accounts. Paid operations use prepaid credits, and you see the estimated cost before you run them.
Explore Cloud credits