Databases
Managed PostgreSQL — tuned, monitored, backed up.
We run Postgres the way it deserves: HA replicas, point-in-time recovery validated weekly, connection pooling, query-plan monitoring and migration safety. On RDS, Cloud SQL, Azure Database or self-hosted with Patroni.
What we manage
High availability
Multi-AZ Postgres on RDS / Cloud SQL / Azure Database, or self-hosted with Patroni + etcd. Failover tested quarterly with documented RTO/RPO.
Backup & recovery
Daily logical + WAL-based PITR, weekly restore validation in a sandboxed environment, encrypted off-region copies, 7-year retention for regulated workloads.
Connection pooling
PgBouncer / RDS Proxy / Cloud SQL Auth Proxy in front of every Postgres — short-lived sessions, prepared-statement reuse, IAM-authenticated connections.
Security
TLS in transit, encryption at rest (KMS / CMEK), row-level security where the schema warrants it, secret rotation via Vault / Secrets Manager, audit logging via pgaudit.
Query & cost optimisation
pg_stat_statements review, index lifecycle (unused index detection, bloat monitoring), autovacuum tuning, storage tier optimisation.
Observability
Per-query latency, connection-pool utilisation, replication lag, locking events, slow query alerts routed to PagerDuty.
Compatible across every cloud we manage
Same playbook on AWS, Google Cloud, Microsoft Azure and DigitalOcean — pick the cloud, we'll run the stack.
How we engage
1. Assess
Two-week audit of your current cloud setup against the provider's Well-Architected / Architecture Framework. Concrete findings, no fluff.
2. Stabilise
We close the top security, reliability and cost gaps before going into steady-state operations.
3. Operate
24/7 monitoring, on-call, change management, monthly reviews and a roadmap for the next quarter.
DIY guides & field notes
Build it yourself — or have us do it for you
Short articles, runbooks and field notes from our engineers. Each one starts here as a snippet and continues on Medium.
May 30, 20261 min read
MySQL to Postgres migration — when it's worth it, the gotchas, and the pgloader workflow
We've migrated databases both ways. Here's the honest decision framework, the data-type traps that bite every team, and the migration runbook we've refined across customer engagements.
Read snippetMay 27, 20261 min read
Postgres replication patterns in 2026 — Patroni, managed services, and the failover story
When to roll your own Patroni cluster, when to use managed Postgres, and the failover semantics nobody explains until production breaks.
Read snippetMay 23, 20261 min read
Postgres autovacuum, demystified — the tuning that prevents 3am wraparound panic
Autovacuum failures are silent until they aren't. Here's how it actually works, the metrics that matter, and the per-table tuning we apply on customer databases.
Read snippetMay 21, 20261 min read
Postgres connection pooling with PgBouncer — the patterns we run in production
Transaction mode, session mode, prepared statements, and the cluster topology decisions that determine whether PgBouncer helps or hurts.
Read snippetMay 10, 20261 min read
Run a PostgreSQL PITR restore drill every week (here's our runbook)
Backups you've never restored are not backups. Our weekly point-in-time recovery drill — what it tests, what we automate, and what we still do by hand.
Read snippet
Ready to take the operational load off your team?
Book a 30-minute discovery call. We will audit your current cloud setup and show you exactly where we add value.