Your AI app runs on SQLite.
Who's watching it?
Agents, RAG pipelines, and edge services all ship on SQLite — then drift, bloat, and corrupt in the dark. Litescope is the operations layer: see your schema, catch faults, and fix them — from one local file to a fleet of thousands.
AI shipped on SQLite.
Nobody's watching it.
Every agent, RAG store, and AI app reaches for SQLite — it's the zero-config default. Then the schema drifts, the WAL bloats, a file corrupts, and the backup nobody tested can't be restored.
Postgres has a decade of tooling for this. SQLite — now running real production behind AI apps, Turso, and D1 — has almost none. Litescope is that tooling.
Every operation, one binary
A pure-Go CLI with zero dependencies. Works on local files and remote databases through the same commands.
One command, one verdict
Point it at a database and get a single checkup — integrity, health, index advice, and schema lint — with a shareable, self-contained HTML report.
See what changed
Human-readable schema and data diff between any two databases. JSON, Markdown, and HTML output for CI and PR comments.
Catch schema smells
Flags SQLite design anti-patterns — no primary key, untyped columns, non-STRICT tables, AUTOINCREMENT, non-integer PKs — in CI, before they ship.
Fix slow queries
Catch the performance bugs AI-generated schemas ship: foreign keys with no index, redundant indexes, and full table scans. Get runnable CREATE INDEX fixes.
Inspect & diagram
Inspect tables, columns, and indexes on local, Turso, or D1 — or emit a Mermaid ERD with --erd to paste straight into a GitHub README.
Portable SQL export
Export schema + data to portable SQL with sqlite3 .dump parity — blob/NULL/quote-safe and round-trip verified. Schema-only or per-table too.
Spot faults early
One command flags corruption, WAL bloat from a starved checkpoint, and fragmentation — the faults that silently break production SQLite.
Lock your schema in CI
Snapshot a known-good schema and fail the build when an unplanned change sneaks in. Migration locking for your pipeline.
Browse your data
Visual table explorer with row-level queries and a SQL console. Get oriented fast without leaving the app.
Let your AI drive it
An MCP server so Claude or any agent can call Litescope as read-only tools — and inspect the database it just built. Diagnose freely; a human commits the fix.
See the blast radius first
Free: diff → runnable SQL with every op classified Safe / Risky / Destructive, plus declarative plan and versioned authoring (new / status) — Atlas-grade, no license. Pro: safe apply/up with auto-backup, single transaction, FK verification, and rollback.
Catch drift over time
Free: baseline a known-good schema and check for drift on demand (cron/CI). Pro: watch continuously with webhook alerts to Slack and Discord.
Trust your backups
Batch PRAGMA integrity checks plus schema and row-count comparison against a reference. Catch a bad backup before you need it.
Operate hundreds at once
Free: read-only shock diagnosis — fingerprint + health on up to 10 databases. Pro: the full lifecycle across a Turso org or D1 account — converge drift to canonical, recover corrupt databases, staged canary rollouts.
Your fleet in a browser
One command — litescope serve — opens a local web dashboard: topology map colored by health, worst-first faults, and a schema-drift fingerprint. Runs on your machine or your own server. No cloud, no account, no telemetry.
Three steps to production safety
Baseline
Snapshot your known-good schema. Takes one command and outputs a versioned JSON file you commit to your repo.
Watch
Run drift detection on a schedule or continuously. Get instant alerts when something changes unexpectedly.
Operate
Validate backups, generate safe migrations, and roll them out across your entire fleet with one command.
One database is fine.
A thousand is a different job.
Turso and Cloudflare D1 made one-database-per-tenant the norm — hundreds or thousands of SQLite files, each its own production system. That's exactly where the old tools assume "one database" and fall apart. Three moments turn a quiet fleet into a 3 a.m. page.
"I thought I ran one schema."
A per-tenant migration half-fails and your fleet quietly splits into many shapes — and you don't know it happened. The next migration is the one that breaks. sqlite3 can't tell you this; fleet fingerprint shows exactly how many schemas you really run.
"How do I roll this out safely?"
DDL locks the entire SQLite file. A migration across 500 tenants is 500 downtime rolls of the dice. migrate apply wraps each in backup → transaction → FK verify → auto-rollback; fleet migrate --canary proves it on a few before the rest.
"Which ones broke, and how bad?"
The first command to run when the pager fires. fleet health triages every database worst-first, fleet recover restores from verified backups, and blast-radius flags the at-risk neighbors in the same group.
Run the shock diagnosis on up to 10 databases free and see your own drift. Fixing the whole fleet is Pro.
Diagnose, then treat —
schema and faults.
Per-tenant SQLite is exploding, and they don't drift into one shape — they fracture into many. Litescope runs the fleet the way an SRE runs a service.
-
fingerprint Cluster every database by schema. You think you run one — see how many you actually run, and exactly how each drifted.
-
health Parallel fault triage: corruption, WAL bloat from a starved checkpoint, fragmentation, unreachable. Sorted worst-first.
-
converge Auto-generate and stage the migration that brings every drifted database back to canonical — canary, halt-on-failure, rollback.
-
recover Restore corrupt databases from verified backups; quarantine the unrecoverable so they're excluded from future ops.
Your AI can drive it too.
Litescope ships an MCP server, so Claude, Cursor, or any agent can call it as a tool — and inspect the database it just built.
-
One command
litescope mcp— point Claude Desktop at it and the tools appear. -
Diagnose freely, treat with a human The agent gets read-only tools — health, diff, fingerprint, and migration plans with blast-radius. It can recommend a fix; a person commits it.
Explore free. Operate with Pro.
Scale with Enterprise.
Free is open source. Pro unlocks the full toolchain with a license key; Enterprise adds a web dashboard, SSO and self-host for teams.
- ✓doctor — one-shot checkup + HTML report
- ✓diff, schema & ERD, dump — explore & export
- ✓lint — schema anti-pattern linter (CI)
- ✓health & advise — faults + index tips
- ✓validate — migration locking for CI
- ✓mcp — AI agent integration
- ✓Local web dashboard (litescope serve)
- ✓fleet shock diagnosis — read-only (≤10 DBs)
- ✓Explorer + 1 named connection (GUI)
- ✓Everything in Free
- ✓migrate — blast-radius analysis + safe apply
- ✓check — backup integrity verification
- ✓monitor — continuous drift + webhook alerts
- ✓fleet — fingerprint, converge, health & recover
- ✓policy gates + team RBAC (local)
- ✓Unlimited named connections (GUI)
- ✓Everything in Pro
- ✓Hosted dashboard — multi-user, time-series history
- ✓Up to 25 databases (Scale tier for more)
- ✓Alerting — Slack, PagerDuty, on-call
- ✓SSO + org multi-user + RBAC
- ✓Self-host — on-prem or your own cloud
- ✓Provisioned within ~1 week of purchase
Running SQLite on Turso, Cloudflare D1 and local files? The CLI you already
use becomes the agent — litescope push streams health and schema
metadata (never your data) to a dashboard that shows your entire fleet,
thousands of instances, on one screen. Drift history, fault triage, and
alerts when something breaks. Run it in our cloud, in your cloud, or
fully self-hosted on your own servers.
$49/month covers up to 25 databases. Bigger fleet? Enterprise Scale — $149/month covers up to 250 databases. Larger or air-gapped? The self-host build runs on your own infrastructure. Every plan is a flat, capped monthly price — no surprise bills.
| Feature | Free | Pro — $99/yr | Enterprise |
|---|---|---|---|
| Explore, inspect & validate | |||
| doctor — one-shot checkup + HTML report | ✓ | ✓ | ✓ |
| Explorer — browse tables & query rows | ✓ | ✓ | ✓ |
| diff — schema & data comparison | ✓ | ✓ | ✓ |
| schema — inspect + Mermaid ERD | ✓ | ✓ | ✓ |
| dump — portable SQL export | ✓ | ✓ | ✓ |
| lint — schema anti-pattern linter (CI) | ✓ | ✓ | ✓ |
| advise — index & query recommendations | ✓ | ✓ | ✓ |
| health — single-DB fault check | ✓ | ✓ | ✓ |
| validate — migration locking for CI | ✓ | ✓ | ✓ |
| migrate — diff → SQL + blast-radius report | ✓ | ✓ | ✓ |
| Operate | |||
| migrate apply — safe apply, backup & rollback | — | ✓ | ✓ |
| Versioned migrations (new / status / up) | — | ✓ | ✓ |
| check — backup integrity + 1 reference | ✓ | ✓ | ✓ |
| check — batch (>1 file) + save-report | — | ✓ | ✓ |
| Monitor | |||
| monitor snapshot / check — drift baseline (cron/CI) | ✓ | ✓ | ✓ |
| monitor watch — single local DB | ✓ | ✓ | ✓ |
| monitor watch — remote targets (Turso/D1) | — | ✓ | ✓ |
| Webhook alerts (Slack, Discord) | — | ✓ | ✓ |
| Drift history & audit trail | — | ✓ | ✓ |
| Fleet — Turso & Cloudflare D1 | |||
| fleet check — parallel drift across all DBs | — | ✓ | ✓ |
| fleet fingerprint / health — read-only shock diagnosis (≤10 DBs) | ✓ | ✓ | ✓ |
| fleet fingerprint / health — full fleet (11+ DBs) | — | ✓ | ✓ |
| fleet converge — auto-fix drift to canonical | — | ✓ | ✓ |
| fleet recover — restore & quarantine | — | ✓ | ✓ |
| fleet migrate — staged canary rollouts | — | ✓ | ✓ |
| policy gates + team RBAC (local) | — | ✓ | ✓ |
| Web dashboard | |||
Local dashboard — litescope serve (self-hosted) | ✓ | ✓ | ✓ |
| Hosted dashboard — multi-user, time-series history | — | — | ✓ |
| Enterprise — teams & scale | |||
| Alerting — Slack / PagerDuty / on-call | — | — | ✓ |
| SSO + org multi-user + org RBAC | — | — | ✓ |
| Self-host — on-prem or your own cloud | — | — | ✓ |
| SLA + priority support | — | — | ✓ |
| GUI | |||
| Named connections | 1 | Unlimited | Unlimited |
| All Pro panels (Migrate, Check, Monitor, Fleet) | — | ✓ | ✓ |
Up and running in seconds
One pure-Go binary. No runtime, no dependencies.