Know what you are running before you connect a provider.

bisibility is an open-source SEO research and search visibility application.

Research keyword opportunities, inspect backlink data, track Google rankings and related SEO signals, then work with the results through the app, versioned REST API, CLI, MCP, signed webhooks, CSV exports, or PostgreSQL in a self-hosted deployment.

Available workflows include competitor benchmarking and Share of Voice, rank alerts, Owner, Admin, Editor, and Viewer roles with an audit log, opt-in Search Console and Google Analytics 4 metrics, and a timeline for deploy and CMS signals.

bisibility is a good fit when you want to choose your own data providers, keep long-term search visibility history, automate workflows through APIs or MCP, or run the application in your own infrastructure.

A bundled SEO suite may fit better if you want one subscription that includes all data sources, managed reporting, content optimization, site auditing, and specialist AI visibility tracking.

bisibility does not currently provide a general-purpose technical site audit or content optimizer, native Maps geo-grid tracking, or AI Overview and LLM citation tracking.

Some product areas, including domain overview, a hosted uptime SLA, and backup restore targets, are planned but not available yet. The public roadmap is the source of truth for current status.

bisibility is a pre-1.0 release. Core workflows are available, but you may encounter rough edges and breaking changes.

For a self-hosted production deployment, configure real authentication and email delivery, protect the database and application network, create backups, and review release notes before upgrading.

No. The hosted beta does not require a card, and self-hosting does not require one either.

You still need your own SERP provider account for rank checks and research. That provider bills you directly for its usage; bisibility never charges or resells those requests.

The self-hosted application is released under AGPL-3.0 and has no bisibility subscription or per-keyword license fee.

You still pay for the infrastructure you operate, provider requests made with your accounts, and any optional services such as email delivery. The hosted service is free during the beta and is planned to become a paid service after the beta.

Today the open application and the hosted service offer the same features. Hosted pricing after the beta will pay for managed hosting and operations, not unlock features. If paid capabilities ever ship alongside the open application, features already released in the open application are not moved behind a paywall or removed.

Provider support differs by capability. Connecting SerpApi enables Google rank checks, but it does not currently enable bisibility's keyword or backlink research.

Provider spend depends on the number of keywords, locations, devices, scheduled runs, result depth, provider mode, and paid research requests.

bisibility does not add a markup to self-hosted provider usage. Use the cost calculator to compare DataForSEO pay-as-you-go rank checks with SerpApi subscription allowances before enabling a schedule.

Paid research and backlink requests show a maintained estimate before the provider call. When DataForSEO returns a provider-reported cost, bisibility records it; when no dollar cost is reported, bisibility uses the configured estimate.

Features that exist today stay free. Some special future feature might be paid one day, but it is not time for those decisions - it is time to provide value, for free (and stars). And whatever gets removed instead of reworked, gets removed from both versions.

Because with Cloud, running bisibility becomes our job instead of yours: the scheduler that never sleeps, upgrades, backups, monitoring, security patches. You pay to not think about any of it. It is also what keeps the project alive - every Cloud subscription funds development of the open-source version.

We will give beta users at least one month's notice before anything changes. Nothing switches to paid automatically, and there is no charge unless you add a card first.

Your account keeps working while you choose what is right for you: subscribe to the hosted service, self-host the AGPL-3.0 application for free, or export your full history and leave.

Yes. Download a project package from the hosted app to keep its keywords and completed ranking history together, then restore that package into a self-hosted project. Provider keys, analytics tokens, and user passwords are intentionally excluded.

You can also export project rank history as CSV through the app or REST API. The API supports the same history filters as the app and streams completed checks as CSV.

Yes. The hosted beta is available in open beta, so you can use the hosted application without operating PostgreSQL, Valkey, or the Temporal worker.

The beta is currently free, with usage limits, and does not require a payment method. It does not yet include a production uptime SLA or restore guarantee. Connected data providers still use your own accounts, quotas, and billing.

The hosted service keeps your data portable through full-history export and a migration path to self-hosting; you do not own or operate the managed database.

You can also self-host the open-source application and operate the full stack yourself.

The Docker setup includes the web application, PostgreSQL, and Valkey. Manual rank checks can run from the base stack. Recurring schedules also require the scheduled profile, which adds Temporal and the bisibility worker.

You also need an account with a supported SERP provider. Email delivery, analytics connections, and other external integrations are optional.

Projects, tracked keywords, rank history, and application settings are stored in the PostgreSQL database you operate. Provider credentials saved through the app are encrypted before storage; optional environment fallback credentials remain in your application environment.

To perform a rank check or paid research lookup, your deployment sends the required query, location, device, domain, or URL context directly to the provider account you connected. Optional analytics integrations also exchange data with the corresponding analytics service.

bisibility does not proxy self-hosted provider requests through a bisibility-owned SERP account.

When the product is ready for them. Whatever the date, beta users get at least a month's notice before anything changes.

Undecided. If the votes and the numbers say there should be one, there will be one.

Yes. bisibility exposes a versioned REST API with OpenAPI, TypeScript, Python, and Go SDKs, signed outbound webhooks, a CLI, and an MCP endpoint.

These interfaces are available to test in the current pre-1.0 release and may change before 1.0.

Agents can authenticate with a personal access token or a project-scoped API key. Core workflows include managing projects and keywords, connecting providers, running checks, reading rank history, working with alerts, researching keywords, and exporting data. Exact operations depend on the interface and release.

Agents work with authenticated tools and structured responses rather than controlling or scraping the dashboard.

You can use, inspect, modify, and self-host the released application under AGPL-3.0. If you run a modified version as a network service for other people, the license generally requires you to offer those users the corresponding source code.

Running an unmodified bisibility deployment for your own team or company does not require you to publish anything.

Versions already released under AGPL-3.0 remain available under those terms. The license text governs; this FAQ is a practical summary, not legal advice.