Store rank history in your own PostgreSQL database, then load it through SQL or REST API v1.

Rank data often stays in a vendor dashboard while revenue data lives in your warehouse. That split makes joined reporting manual and hard to reproduce.
Keep rank history in your own PostgreSQL database. Existing ETL or ELT jobs can read it as another source table.
Pull projects, keywords, and rankings through a documented API when direct SQL is not suitable.
Run daily, weekly, manual, or custom checks to keep the warehouse time series current.
Store country and device on each keyword. Warehouse models can join rankings at a stable level of detail.
Create keywords with the country and device used by each market.
Schedule checks so each warehouse load receives new ranking rows.
Query PostgreSQL directly or use REST API v1 from your ingestion job.
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.
Store rank history in your own PostgreSQL database, then load it through SQL or REST API v1.
Bisibility ships an AGPL-3.0 self-hosted app, BYO DataForSEO or SerpAPI support, scheduled Google rank checks, multi-location and multi-device tracking, owned Postgres history, CSV-oriented exports, REST API v1, OpenAPI, MCP, and agent-discovery endpoints.
Owner, Admin, Editor, and Viewer team roles are shipped. Audit log is shipped. Finer resource-level permissions remain planned. Full-history export is shipped. Native BI warehouse connectors remain planned. Native warehouse connectors for BigQuery, Snowflake, or Redshift are not shipped yet. Opt-in Google Search Console and GA4 connections are shipped (self-hosted). GA4 and GSC conversion attribution is planned.
