The Five-Day
Database Audit
We audit your production PostgreSQL or SQL Server for a fixed 3,900 USD, in five business days. No access needed.
You run our read-only script, review what it collected and send it to us. We send back a report ranked by risk, with the fixes ready to apply.
What you get
- A report ranked by risk. A PDF of 15 to 25 pages. Each finding states what it is, why it matters, the fix and the expected gain.
- Scripts ready to apply. SQL for new or dropped indexes, configuration changes and rewritten queries.
- A 90-day plan. The fixes from the report, laid out over the next three months.
- A 10-minute walkthrough video. A screen recording that takes you through the report.
- Two weeks of email Q&A. Ask us anything about the report for two weeks after delivery.
How it works
- Pay. You pay through a Stripe link. We send you the collection script.
- Run the read-only script and review the bundle. Use
collect-postgres.shfor PostgreSQL orcollect-mssql.sqlfor SQL Server. You run it with your own read-only role. It does not collect row data or credentials. You can open and read the archive before you send it, and you send it to us encrypted. - We work five business days. The clock starts on the day your bundle reaches us.
- You get the report. Report, scripts, 90-day plan and video arrive together. The two weeks of email Q&A start that day.
This is what the bundle holds. Pick your engine.
collect-postgres.sh writes one CSV per topic into alpiflow-bundle/:
- version.csvserver version, uptime, recovery state
- settings.csvmemory, WAL, checkpoints, autovacuum, planner
- databases.csvsize, transaction ID age
- tables.csvsize, rows, scans, dead tuples, last vacuum
- indexes.csvsize, scans, definition
- indexes-unused.csvzero scans, not backing a constraint
- indexes-duplicate.csvexact duplicates
- constraints-no-pk.csvtables without a primary key
- statements-by-total-time.csvtop 100 from pg_stat_statements
- bloat-tables.csvestimated table bloat
- locks-blocking.csvsessions waiting on a lock
- activity.csvsessions, waits, current query
- extensions.csvinstalled and latest versions
collect-mssql.sql reads the matching DMVs, one CSV per section:
- version.csvversion, edition, update level, start time
- configuration.csvall instance configuration options
- wait-stats.csvtop 100 wait types since restart
- file-io.csvreads, writes and stall times per file
- query-stats.csvtop statements by CPU, duration, reads
- tables.csvrows, size, scans and seeks
- indexes.csvsize, seeks, scans, lookups vs updates
- indexes-unused.csvno seeks, scans or lookups
- missing-indexes.csvsuggestions from the optimizer
- heaps.csvtables without a clustered index
- index-fragmentation.csvindexes over 1,000 pages
- backups.csvlast full, differential, log backup
- requests.csvrunning requests, waits, blocking
A live query as captured: WHERE email = 'jane@example.com'WHERE email = ?
- table rows
- passwords and connection strings
- credential-bearing settings (redacted)
On PostgreSQL every query runs in a read-only transaction, with a 60-second statement timeout and a 3-second lock timeout.
Who it's for
For
B2B SaaS and e-commerce teams of 10 to 200 people with PostgreSQL or SQL Server in production and no DBA. Usually bought by the CTO, the Head of Engineering or a founding engineer.
Not for
Teams that want a managed DBA service, or a migration done as part of the audit. We do neither.
Guarantee
If the report contains fewer than five fixes you can apply, we refund the full price.
Price
3,900 USD, or 3,400 EUR for clients in the EU.
Payment is due at the start. The invoice comes from the studio in Italy, with our VAT number on it. The full terms are on the terms page.
Sample report
A seven-page public extract of the sample report, on a synthetic pgbench workload. The full sample is sent on request.
Sample report on a synthetic pgbench workload (PDF)
About
Alpiflow is an independent engineering studio from Italy. We audit production databases and .NET backends at a fixed price, without needing access to your systems.
We build our own database tooling. Our desktop client, written in Rust, connects to 24 engines plus any ODBC driver and reads execution plans. It writes the CREATE INDEX it recommends.
Our own multi-tenant .NET 10 platform sits on PostgreSQL and pgvector, with its schema kept in EF Core migrations and end-to-end tests against real Postgres containers.
FAQ
Do you audit SQL Server?
Yes. The SQL Server script, collect-mssql.sql, reads the DMVs that match what we collect on PostgreSQL. The deliverables and the price are the same.
Does it work on managed databases like Amazon RDS or Azure SQL?
Yes. The script only reads system views and statistics through a read-only role. If a provider hides a setting from that role, the report says what we could not see.
What about sensitive data?
The script collects no row data and no credentials. You read the archive before it leaves your hands, and you send it to us encrypted. We never connect to your systems. Part of the analysis runs through a language model API (Anthropic, US) under commercial terms that exclude training on customer data; nothing else leaves the studio.
What happens if you find nothing?
If the report has fewer than five fixes you can apply, you get a full refund.
Who does the work?
The studio does, from the first read of your bundle to the walkthrough video. Every report is reviewed before it is sent to you.
Do we need a call?
No. The whole audit runs by email. If you want one, we hold an optional 20-minute call at your request.
Questions before you start: contact us.