Your SQL database
×
Papercrane
You've written that query a hundred times. Connect your Postgres, MySQL, MariaDB, or SQL Server with a read only login you create, and Papercrane's AI agent writes the SQL, shows you the SQL, and publishes a live dashboard your team opens instead of pinging you.
Connect in about a minute. Free to connect and ask. Paid plans start when you publish a dashboard. See pricing
You don't hand over your application's login. You create a read only one, scoped to what reporting needs, and you can point it at a replica instead of your primary.
Connections run over SSL.
Have a read replica? Point Papercrane there and your primary never sees a reporting query.
More than one schema? Repeat the grants per schema; Papercrane queries across them.
Revoke this login and the connection is dead.
Every dashboard Papercrane builds is code you own, and the queries are part of it. When a number matters, you read the query and rerun it yourself.
A wrong number doesn't throw an error, which is exactly why the queries stay readable. Actual errors route back to the agent automatically, and it repairs the dashboard instead of waiting for you to notice.
Active accounts by plan, weekly, since January.
Orders stuck in a fulfillment state for more than 48 hours.
The list sales asked for: accounts with more than 50 seats and no login in 30 days.
Signups per week next to actual revenue collected in Stripe.
Which marketing channels in GA4 produce users who are still active at day 30.
Rows created per table per day, so you see growth before it pages you.
Each answer becomes a tile on a hosted dashboard. The follow up questions go to the agent, not to you.
1. Create the read only login (copy it from above)
2. Connect over SSL and ask a question
3. The agent writes the SQL and builds a hosted dashboard
4. It stays live, and errors route back to the agent
| The job | You and a SQL client | Metabase you host | Your database + Papercrane |
|---|---|---|---|
| The next quick pull | Costs you the query plus the context switch back into your code | Costs whoever learned the query builder; the hard ones still reach you | Asked in chat, answered as a chart, without you |
| Standing up and keeping it running | Nothing to run | Your server, your upgrades, your backups, your app database migration | Hosted; nothing new on your infrastructure |
| A question that spans Stripe or GA4 too | Two exports and a spreadsheet join | Separate sources on separate cards; the join is on you | The agent joins them in one dashboard |
| When a number looks wrong | You rerun it and eat the time | You debug the question and the instance | The query is code you own; read it, rerun it, fix it in the open |
| When the dashboard breaks | It was never up | Someone notices, eventually, and it's you | Errors route back to the agent automatically, which repairs it |
| What it costs | Your hours | Free software, plus the hours; hosted from about $100/month | Free to connect and ask; paid starts at publishing (see pricing) |
When you don't need us
If what your team needs is a free explorer for one database and you're happy running a server for it, self hosted Metabase is the right answer; it's mature, your less technical teammates can click around it, and free means free. If you're charting infrastructure metrics, Grafana is already built for that. Papercrane is worth paying for when you want the asking, the hosting, and the repairs off your plate, or when the answer spans your database plus Stripe, GA4, or your books.
The best application database questions don't end at the database. Most teams connect Stripe for revenue truth and GA4 for what happened before signup; when you outgrow the app database, the warehouse pages are next.
Create the read only login, connect your database, and answer the next request with a link.
Connect in about a minute. Free to connect and ask. Paid plans start when you publish a dashboard. See pricing
Papercrane
Integrations: