Self-host Bisibility, connect an approved SERP provider, and store positions, ranking URLs, and check history in Postgres you operate.
Best fit when security review, retention rules, and export access matter as much as the ranking chart. Use Bisibility when your team needs an inspectable, portable rank-check workflow inside infrastructure it operates.
Store positions, ranking URLs, timestamps, and provider-reported costs in the database you operate.
Connect DataForSEO or SerpAPI with your own account so provider billing and review stay direct.
Read projects, keywords, and rank checks through REST API v1 and OpenAPI instead of manual exports.
Run daily, weekly, manual, or custom-cron checks so history builds without a teammate babysitting it.
Add your DataForSEO or SerpAPI key and keep the contract outside Bisibility.
Create projects, add target URLs, choose markets and devices, then let schedules run.
Query Postgres or REST API v1 when dashboards, audits, or reports need rank history.
The self-hosting guide lists the current services and deployment paths. Connect a supported SERP provider before the first real rank check.
Review the deployment optionsUse the playbook for a repeatable SEO process, estimate provider cost, or explore the closest product workflow.
You run the app, database, and worker yourself. Rank history and provider credentials stay in your deployment, while SERP checks use provider keys you control.
No. Bisibility uses a bring-your-own-provider model for DataForSEO and SerpAPI, so billing and data access stay between you and the provider.
Yes. The data lives in Postgres and can also be read through REST API v1, OpenAPI, and CSV-oriented workflows.
