Databases & data platforms

Databases that stay fast, available and recoverable.

Talk to an engineer
Problems we solve
“Queries got slow as the data grew.”
“One database server, no failover.”
“Reports run against production and slow everyone down.”

What we do

Advise

Databases & data platforms consultancy

An assessment of your Databases & data platforms setup, with findings ranked by risk and effort.

Build

Databases & data platforms delivery

We design and build it with your team, in your accounts, documented as we go.

Run

Databases & data platforms support

Monitoring, patching and upgrades, with incident response agreed per contract.

Teach

Databases & data platforms training

Workshops and pairing on Databases & data platforms, built around your own systems.

Tools we work with

Engines

  • PostgreSQL
  • MySQL
  • MariaDB
  • SQL Server
  • MongoDB
  • Redis
  • Valkey

Managed services

  • Amazon RDS
  • Aurora
  • DynamoDB
  • Azure SQL
  • Azure Database for PostgreSQL
  • Cloud SQL
  • AlloyDB
  • Neon

High availability & scaling

  • Patroni
  • PgBouncer
  • read replicas
  • Citus

Backup & recovery

  • pgBackRest
  • Barman
  • point-in-time recovery

Data pipelines

  • Debezium
  • Kafka
  • Airbyte
  • dbt
  • BigQuery
  • Snowflake

Monitoring & tuning

  • pg_stat_statements
  • Performance Insights
  • PMM

How an engagement runs

  1. 1 A call. 30 minutes with an engineer to understand the problem.
  2. 2 A look. Read-only access or a walkthrough, so we scope from facts.
  3. 3 A proposal. Scope, deliverables and a price model: fixed scope, day rate or retainer.
  4. 4 The work. In your accounts and repositories, alongside your team.
  5. 5 A handover. Documentation and a session with your team, so you’re not dependent on us.

Proof

A recent Databases & data platforms engagement. We keep client names private, but the problem, the work and the outcome are exactly as they happened.

See our work
Case study · anonymised
UK e-commerce scale-up
Challenge
Queries got slow as the data grew. That was how the client put it on the first call.
Approach
We tuned the slowest queries, added a replica with tested failover, and moved reporting off the production database.
Stack
PostgreSQL · RDS · read replicas
Result
Pages stayed fast as data grew, and a database failure is no longer an outage.

Questions

Do you work in our accounts or yours?

Yours. Everything we build lives in your cloud accounts and repositories from day one, so there is nothing to migrate when we finish.

Can you work alongside our own team?

Yes, and we prefer it. We can run a project ourselves, embed engineers in your team, or pair with your people so they pick it up as we go.

How is this priced?

Depending on the work: a fixed-scope price, a day rate or a monthly retainer. We agree it in a written proposal before anything starts.

Tell us what’s broken, slow or expensive.