Straight answers about how Bisibility works: self-hosting, bring-your-own SERP providers, pricing, the API and agents, team roles, and what is still on the roadmap.
What Bisibility is, who it is for, and what it does today.
Bisibility is an open-source Google rank tracker that ships self-hosting. In a self-hosted deployment, you add keywords, it checks where your pages rank, and it keeps that history in your own database.
It is built to be small and inspectable on purpose. You get rank tracking and schedules, REST API v1 and OpenAPI, MCP endpoint and tools, and rank history in your own Postgres, without a heavy SEO suite around it.
Agencies that want to own client rank data, SaaS teams proving organic growth, local businesses tracking classic rankings, and open-source developers who want a stack they can read.
If you mainly want a hosted suite that buys SEO data for you and bundles dozens of modules, a larger platform may fit you better today.
The app ships self-hosting under the AGPL-3.0 license. bisibility is open core: paid features may exist alongside the open application, and we don't take working features out of it.
You still pay your SERP provider directly for the rank checks you run. Hosted Bisibility Cloud is planned, while self-hosting comes first.
Yes. Future versions may be released under different terms, and the Contributor Licence Agreement is what gives the project the right to do that.
Everything already released under AGPL-3.0 stays under AGPL-3.0 permanently. You can always fork the code from any AGPL-3.0 release and continue from that point.
How you run it and where your rank history lives.
Use self-hosting with Docker or your own cloud, point it at a Postgres database, and add your SERP provider key. Once the key is set, rank checks start working.
The app, database, rank history, and provider credentials stay in your deployment. SERP provider portability sends rank-check requests directly to the DataForSEO or SerpAPI account you connect, not through a Bisibility-hosted data proxy.
Bisibility ships a customer-controlled PostgreSQL database. Keyword positions, ranking URLs, check timestamps, and provider costs are all rows you control.
Because you own the database, direct SQL access and full-history export let you retrieve history without asking a vendor.
Yes. Bisibility ships Owner, Admin, Editor, and Viewer team roles, with invitations and server-side authorization, plus an append-only audit log for sensitive actions.
Self-hosters still control the surrounding network, database permissions, retention, backups, and infrastructure logs. Application roles and the audit log complement those controls rather than replacing them.
How bring-your-own SERP providers and pricing work.
Bisibility ships SERP provider portability: you connect your own DataForSEO or SerpAPI account instead of buying rank data through Bisibility. The app calls your provider with your key.
This keeps billing direct and lets you switch providers when cost or coverage changes, without moving your rank history.
Your cost is mostly your provider's SERP pricing. As a reference, DataForSEO standard pricing is around $0.60 per 1,000 SERPs at the time of writing.
Bisibility ships per-check provider cost tracking, so you can see spend per keyword and per schedule instead of guessing.
Use the rank tracking cost calculator at /rank-tracking-cost-calculator before you connect credentials. Enter keyword count, locations, devices, schedule, and provider to estimate monthly SERP spend.
It follows the same bring-your-own provider model as the app: you pay the SERP provider directly, and Bisibility helps you preview the checks and cost before you turn on a schedule.
Bisibility ships SERP provider portability across DataForSEO and SerpAPI today. You configure your own account and drop in the key.
Provider coverage and pricing change over time, so each check records the request context and cost for later review.
How tools, scripts, and AI agents read your rank data.
Yes. Bisibility ships REST API v1 and OpenAPI, covering keywords, checks, and projects, plus API keys and idempotency for safe automation.
You can wire rankings into your own reports, internal tools, or scheduled jobs without scraping the dashboard.
Yes. Bisibility ships an MCP endpoint and tools plus agent-discovery endpoints, so AI agents can read rank data through a typed interface instead of a brittle scrape.
This is designed for the era of agents and assistants: the same data the dashboard shows is available to your tools and models.
What is not shipped yet and how to read our honest gaps.
Slack alert delivery is planned. Prebuilt signal connectors is in progress. SEO enrichment integrations is planned. Context-aware alerts is planned. Keyword suggestions from connected data sources is in progress. Keyword research workspace is in progress. Notification preferences, quiet hours, and language is in progress. Tag and group schedules is planned. AI Overview and LLM visibility tracking is planned. Native geo-grid local tracking is planned. GA4 and GSC conversion attribution is planned. Push alert delivery is planned. Hosted Bisibility Cloud is planned.
What ships today: rank alerts in-app and by email, outbound webhooks, competitor benchmarking and Share of Voice, Owner, Admin, Editor, and Viewer team roles, and an audit log.
We list these gaps plainly on our comparison and use-case pages so you can decide based on what is real today, not a feature wishlist.
AI Overview and LLM visibility tracking is planned. Today, evaluate Bisibility as a classic Google rank tracker.
If answer-engine visibility is your primary need right now, use a specialist AI-visibility tool while this capability remains planned.
Self-host the rank loop, keep provider credentials in your deployment, and read the data through REST, OpenAPI, and MCP for agents.