Architecture & data · Service
Database Management
We design, tune and look after relational databases, mostly PostgreSQL: schemas that match the domain, queries that stay fast as data grows, and backups you have actually restored.
-- the query your dashboard runs EXPLAIN ANALYZE SELECT … FROM leads WHERE email = $1; before Seq Scan on leads reads every row after Index Scan using leads_email_idx reads only the matching rows
IllustrationTuning starts from real query plans, and a backup only counts once it has been restored.
Who is Database Management for?
For teams whose database is slow, fragile, or one bad migration away from an outage.
Delayed decisions
Every decision waits for a number someone has to assemble by hand, so meetings end with “let's check”.
What do you get?
- A schema review and migration plan, with rollback steps
- Index and query tuning based on real query plans
- Backups, point-in-time recovery and a tested restore runbook
- Least-privilege roles, encryption and audit settings
How do you know it's done?
- A restore has been performed and timed, not just scheduled
- The slowest queries are known, measured and addressed
- Every application connects with only the access it needs
How does an engagement run?
- 01
Brief. A few minutes with our intake. Your context arrives before the call does.
- 02
Intro call. Thirty minutes. We ask the hard questions and tell you honestly whether we're the right fit.
- 03
Written scope. Scope, exclusions, milestones and a fixed price per phase, in writing, before any invoice.
- 04
Architecture. Diagrams and decision records you review and approve before the build starts.
- 05
Build. Working software on staging, demoed on a fixed cadence. You see progress, not status reports.
- 06
Handover. Code, infrastructure, docs and runbooks in your accounts. Ongoing support only if you want it.
How is it priced?
By scope. After the call you get a written scope with exclusions, milestones and a fixed price per phase. Payment follows accepted milestones. The budget range you pick in the brief isn't a quote; it helps us suggest a first phase that fits.
Which technologies do you use?
Our usual stack for Database Management. We work with yours when you have one.
- PostgreSQL
- Prisma
- Redis
- AWS
Database Management: questions and answers
Which databases do you work with?
Mostly PostgreSQL, alongside Prisma and Redis.
How do you make a slow database faster?
From real query plans. We find the slowest queries, measure them, tune indexes and queries, and check that the schema still matches the domain.
How do we know our backups work?
Only by restoring them. We set up backups and point-in-time recovery, then perform and time a restore, and leave you a tested restore runbook.
Start a brief for Database Management.
A few questions, about three minutes. Nothing is sent until you review it and press Send, and the first call is thirty minutes to check fit, both ways.