For mobile app debugging

The SQLite database inside your client's app, without leaving adb

Plug in the Android or the iPhone, open any database the app loads, and browse it table by table — live, while the app runs. No copying the .db out, no DB Browser, no adb pull every time a column changes.

Download for free See what's in Pro

Windows · free plan, no signup · zero telemetry

In practice

The time you stop losing

Less back-and-forth to find out what the app recorded, less guessing about where the bug lives.

Fix it without asking for a screenshot

See exactly what got written to the device in the middle of the bug, without waiting for the user to reproduce it again for you.

Tell a local bug from a server bug

Compare what the app stored in SQLite with what the API returned, with no instrumentation — the answer is in the table.

Fix a test value on the spot

Edit the wrong cell and reproduce again, without reinstalling the app or repeating the whole flow on the device.

Cached queries: 170ms vs. 479ms re-copying the database on every click — measured on the test device, not a marketing number.

Features

Built for people who live inside adb logcat

Android and iPhone, live

Connected device or a loose .db file — same screen, same shortcut to rescan when the app writes something new.

Read-only SQL, no risk

Virtualized grid, sticky header, every column's type on display. Free-form queries for when a whole table isn't enough.

Count, filter and chart

Group by column, filter without writing WHERE, and turn a result straight into a chart.

Pro

Cell editing

Fix a test value without reinstalling the app or repeating the whole flow on the device.

Pro

AI with one job

No file access, shell or network — every stock CLI runs boxed in to the database tool only. It refuses the rest, even if asked.

Light and dark

Follows the system theme or locks yours — both measured for the same contrast, not just an inverted color.

Privacy

Your client's database never leaves your machine

Zero telemetry. File paths, table contents, package names — none of it travels. The only four conversations with the network exist for the product, never for the data you're inspecting.

  • License — sends the key and the machine hash, only once you already have a saved license.
  • Update — only downloads the signed installer for a new version.
  • Error report — the text passes through a scrubber that swaps paths, package names and databases for placeholders before it leaves.
  • Installing an AI assistant — downloads the vendor's official CLI, only on click, and checks its hash before running it.

Pricing

Start free, go Pro when you need to write

Free reads. Pro counts, filters, groups, charts and writes — on screen and through the AI.

Free

No cost
  • Database and table tree, on-device or a loose .db file
  • Read-only grid and free-form read queries
  • Chat with the AI — it shows up to 10 rows from a table
  • No count, filter, grouping or charts
  • No writing — not on screen, not through the AI
Download for free

Pro

Monthly subscription
  • Everything in Free, with no row limit
  • Count, filter, group and chart straight from the grid
  • Cell editing and SQL writes
  • The AI writes too, when you let it
Try free for 3 days

Card required at signup · first charge only after 3 days · cancel before then and pay nothing

Download DBScout

Native installer, no app store. The free plan already opens any database your client's app loads.

Download for Windows Install for VS Code

Requires Windows 10 or newer · 64-bit

FAQ

Questions people ask before subscribing

How does the 3-day trial work?

Subscribing to either plan starts a 3-day window before the first charge — enough to try writing, cell editing and the AI assistants. Cancel within that window and you're never charged.

Can I cancel anytime?

Yes, no lock-in. Cancelling stops the next charge, and the license simply reverts to Free the next time it revalidates — no manual step, no support ticket.

Does it still work without internet?

Yes. Pro keeps working offline for up to 72 hours after the last check and warns you before it expires; a hard refusal from the license server drops it to Free immediately instead.

Is it safe to edit a client's production database?

Being honest: the real risk is editing while the app on the phone still has that same database open — returning the file underneath it can corrupt what the app is mid-write on. Outside that case, edits are scoped one cell at a time, by row, with type validation.

Can the AI assistant see my other files?

No. Every assistant runs boxed in to the database on screen only — no file, shell or network access, even the vendor's own tools are disabled. It refuses anything outside that, even if asked.