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.
Spreadsheet to SQLite
Turn a CSV, TSV, or JSON file into a real, typed SQLite database in one command — header-aware, type-inferred. Or just run litescope yourfile.csv and it imports itself. Fix it, then export it back out.
Scrape it into Grafana
Render fleet health and schema-drift as Prometheus / OpenMetrics text — one-shot for a textfile collector, or --serve a /metrics endpoint. Drops straight into Grafana and Alertmanager.
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
Diff → runnable SQL with every op classified Safe / Risky / Destructive, plus declarative plan (with a CI drift gate) and versioned authoring (new / status) — Atlas-grade. Apply safely with apply/up: auto-backup, single transaction, FK verification, and rollback.
Catch drift over time
Baseline a known-good schema and check for drift on demand (cron/CI), or 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
Read-only shock diagnosis — fingerprint + health across a Turso org or D1 account — and the full lifecycle: converge drift to canonical, recover corrupt databases, staged canary rollouts. A fleet of any size.
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. Plus a read-only data browser and SQL console — click a table to preview rows, or run any SELECT. 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, see your own drift, and fix the whole fleet — free and open source, on a fleet of any size.
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.
The whole toolchain is free.
Forever.
Litescope is open source under the GNU AGPL-3.0. Every command — diff, migrate, monitor, the entire fleet lifecycle, and the local web dashboard — is unlocked for everyone, on a fleet of any size. No license key, no tiers, nothing to unlock.
One thing we'll host for you
The only paid offering is optional and runs beside the open-source
tool, never gating it. 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 hosted dashboard
that shows your entire fleet, thousands of instances, on one screen, with
time-series drift history and alerts when something breaks.
It runs on a metadata-only edge stack (Cloudflare Workers + D1), so it costs
almost nothing to operate — and there's nothing to host yourself unless you
want to: litescope serve already gives you the same dashboard
locally, free. The hosted version is planned and demand-gated — see the
roadmap. Need enterprise self-host or support? dl_litescope@crode.net.
Run this locally today with litescope serve — free. The hosted version is the multi-user, always-on cloud edition.
Up and running in seconds
One pure-Go binary. No runtime, no dependencies.