Next platform deadline: Amazon EKS Nov 26, 2026  

All 14 deadlines

Data practice

Data & database engineering for every engine you run.

We upgrade, migrate, tune and run the databases your products depend on, from PostgreSQL, MySQL, SQL Server and Oracle to MongoDB, Cassandra, Aerospike, Redis and Valkey, DynamoDB and Cosmos DB. Every engagement is fixed fee with a written plan.

Services
7
Engagements
Fixed scope, fixed fee
Who does the work
Senior engineers
SOURCEEnd of supportTARGETSupported, tunedREPLICATIONCDC · checksumsRollback path kept warmAssessRehearseReplicateCut overVerifyLag, row counts and checksums watched until cutover

Relational, NoSQL and in-memory. On premises, AWS, Azure, Google Cloud and OCI.

All platforms
  • PostgreSQL
  • MySQL
  • SQL Server
  • Oracle
  • MariaDB
  • MongoDB
  • Cassandra
  • ScyllaDB
  • Aerospike
  • Redis
  • Valkey
  • Aurora
  • Azure SQL
  • Spanner
  • DynamoDB
  • Cosmos DB
  • Debezium

Point of view

The database is the slowest thing in your stack to change and the most expensive to get wrong. We treat every upgrade and migration as a rehearsed, reversible change, with the rollback path built before the cutover.

7 services, each with a fixed-fee entry point.

Relational, NoSQL and in-memory. On premises, AWS, Azure, Google Cloud and OCI. Each is scoped after a free 30-minute review, and the assessment fee is credited to the project.

01 / 07

Database Upgrades & End-of-Support Programs

Every engine has a clock. RDS and Cloud SQL now bill for extended support on old PostgreSQL and MySQL versions, SQL Server 2017 support ends in October 2027 and MongoDB 7.0 in August 2027. We plan, rehearse and run the upgrades on a fixed fee.

Sound familiar?

  • Your AWS bill now carries RDS Extended Support charges for MySQL 8.0 or PostgreSQL 13, and PostgreSQL 14 joins them on February 28, 2027.
  • You still run SQL Server 2016, which left extended support in July 2026, or SQL Server 2017, which follows on October 13, 2027.
  • MongoDB 6.0 is already past end of life, 7.0 ends on August 31, 2027, and nobody has tested the drivers against 8.0.

You receive

  • Inventory of versions, support dates and extended-support cost
  • Upgrade path and runbook per database
  • Compatibility test results

Database Upgrades & End-of-Support Starts with: Upgrade readiness review

02 / 07

Database Migration & Modernization

Licence renewals, data centre exits and consolidation programs all end in the same place: moving data without breaking the business. We assess every database honestly, move only what pays back and validate every row before cut-over.

Sound familiar?

  • An Oracle or SQL Server renewal is coming and finance wants to know what a move to PostgreSQL would really cost.
  • You are leaving a data centre or VMware and dozens of databases need a home on AWS, Azure or Google Cloud.
  • Years of growth left you with too many small instances, engines and versions to secure and patch.

You receive

  • Assessment with a target and effort per database
  • Licence and run-cost comparison
  • Wave plan with dependencies

Database Migration & Modernization Starts with: Migration assessment

03 / 07

NoSQL Engineering: MongoDB, Cassandra, Aerospike, DynamoDB & Cosmos DB

NoSQL clusters run quietly until a version leaves support, a partition gets hot or the bill doubles. We upgrade, re-model, migrate and tune MongoDB, Cassandra, Aerospike, DynamoDB and Cosmos DB with the same discipline we bring to relational systems.

Sound familiar?

  • MongoDB 6.0 is already out of support and 7.0 ends on August 31, 2027; you want to land on 8.0 without surprises.
  • Your Cassandra 3.11 ring has been unsupported since September 2024 and the upgrade must go one major version at a time.
  • Aerospike 7.x releases reached end of life during 2025 and 2026, and the team that built the cluster has moved on.

You receive

  • Health check report with prioritized findings
  • Version path and rolling-upgrade runbook
  • Data model recommendations

NoSQL Engineering Starts with: NoSQL health check & upgrade plan

04 / 07

Redis, Valkey & Caching Engineering

Redis changed its licence in 2024, Valkey forked under the Linux Foundation, and Microsoft is retiring Azure Cache for Redis. We help you choose between Redis and Valkey, move caches without dropped sessions and design caching that holds up under load.

Sound familiar?

  • Legal flagged the Redis licence change and wants to know whether Valkey removes the question.
  • You run Azure Cache for Redis Enterprise, which retires on March 31, 2027, or Basic, Standard or Premium, which retire on September 30, 2028.
  • ElastiCache for Valkey costs less than Redis OSS and you want the saving without a risky cut-over.

You receive

  • Inventory and licence position
  • Target recommendation with cost comparison
  • Migration runbook with rollback

Redis, Valkey & Caching Starts with: Caching review & migration plan

05 / 07

Database Performance & Reliability Engineering

Slow queries, failovers that have never been tested and backups nobody has restored are the quiet risks in most estates. We find the real bottlenecks, prove recovery works and leave your team with numbers instead of hunches.

Sound familiar?

  • Peak traffic makes the database the bottleneck and the answer so far has been a bigger instance.
  • Your recovery time and recovery point objectives are written down but have never been tested.
  • A failover happened once and took far longer than anyone expected.

You receive

  • Prioritized findings with expected impact
  • Tuned queries, indexes and configuration
  • HA/DR design and failover test results

Performance & Reliability Starts with: Performance & resilience review

06 / 07

Managed Data Reliability Engineering

Not a ticket queue. A named senior engineer runs your data platforms the way an SRE team would: service level objectives, automation, patching, tested restores and a monthly report, across every engine you run.

Sound familiar?

  • You have no full-time database engineer, or one person holds everything in their head.
  • Patching happens when someone remembers, and nobody has tested a restore this year.
  • Monitoring alerts on everything, so the team ignores it.

You receive

  • Agreed SLOs and alerting
  • Runbooks for every database
  • Quarterly restore test reports

Managed Data Reliability Starts with: Reliability onboarding

07 / 07

Oracle Database & Middleware Modernization

Oracle estates face two hard dates: Fusion Middleware 12c Premier Support ends in December 2026 and Amazon RDS Custom for Oracle retires on March 31, 2027. We handle both, plus database upgrades to 19c and 26ai and Forms modernization, on a fixed fee.

Sound familiar?

  • WebLogic, SOA, OSB or Forms runs on 12.2.1.4 and Premier Support ends in December 2026.
  • 14.1.2 needs JDK 17 or 21 and drops the classic Administration Console.
  • You run Oracle on Amazon RDS Custom, which AWS retires on March 31, 2027.

You receive

  • Inventory and support-date map
  • Upgrade or exit path per domain and database
  • Scripted builds and Terraform you own

Oracle & Middleware Modernization Starts with: WebLogic readiness review

Data & Databases dates to plan around

Live day counts to published vendor dates. Full calendar Check your stack

  1.   days Oracle Fusion Middleware 12c (WebLogic, SOA, Forms) Premier Support endsOracle & Middleware Modernization
  2.   days Google Cloud SQL Cloud SQL for MySQL 8.0 moves to paid extended supportDatabase Upgrades & End-of-Support
  3.   days Amazon RDS RDS for PostgreSQL 14 ends standard support; Extended Support charges beginDatabase Upgrades & End-of-Support
  4.   days AWS & Oracle Amazon RDS Custom for Oracle retiresOracle & Middleware Modernization
  5.   days Azure Azure Cache for Redis Enterprise and Enterprise Flash tiers retireRedis, Valkey & Caching
  6.   days Oracle Oracle Database 21c Premier Support ends (no Extended Support)Oracle & Middleware Modernization

What is driving demand right now

Backed by public sources.

  1. Licence change

    Redis to Valkey

    Redis moved to source-available licences in 2024, then added AGPLv3 in Redis 8. Valkey, the Linux Foundation fork, stays BSD and costs less on ElastiCache.

    Redis, Valkey & Caching Source: Redis

  2. Extended-support fees

    Paying to stay on old versions

    Amazon RDS and Cloud SQL charge extended support on PostgreSQL and MySQL versions past their standard support date, and the charge rises over time.

    Database Upgrades & End-of-Support Source: AWS

How we deliver Data & Databases work

The same five phases on every engagement in this practice, so you always know what happens next and what you hold at the end of each phase.

  1. 01

    Discover

    Inventory engines, versions, sizes, dependencies and support dates from read-only access or exports.

  2. 02

    Assess

    Compatibility, performance baselines, backup and restore proof, and a risk register.

  3. 03

    Plan

    Waves, windows, rollback and a fixed quote, in a written plan you keep.

  4. 04

    Rehearse

    Every change runs end to end in a production-like environment, with measured timings.

  5. 05

    Cut over and hand over

    Executed in your window, verified against agreed checks, documented in your repository.

Outcomes we measure

How we frame the business case. We agree the baseline and the measure in the statement of work and report against them. We never quote invented benchmarks or other clients' results. Building the business case

  1. Support exposure removed

    Instances moved off end-of-support versions, and the extended-support fees avoided, calculated from the vendor's published rates and your own inventory.

  2. Downtime per change

    Planned downtime measured in rehearsal, then reported against the actual window after each cut-over.

  3. Recovery proven

    Restore time and data-loss window (RTO and RPO) tested, not assumed, and written into the runbook.

  4. Performance against baseline

    p95 latency, throughput and resource use for your critical queries, before and after.

  5. Licence and run cost

    Licence and infrastructure cost after a migration, taken from your actual contracts and bills.

Proof by depth

Judge the depth before the first call.

No invented statistics or borrowed logos. Instead, the documents themselves: the same structure we deliver, filled in for fictional systems so you can judge the depth before you talk to us.

All samples and checklists Engagement examples

Platforms we work with

Independent and vendor-neutral. Names are trademarks of their owners; listing does not imply partnership. All platforms

Relational databases

  • PostgreSQL
  • MySQL
  • SQL Server
  • Oracle
  • Aurora
  • Azure SQL
  • Cloud SQL
  • AlloyDB
  • Spanner

NoSQL, caching & search

  • MongoDB / Atlas
  • Cassandra / Astra DB
  • Aerospike
  • Redis
  • Valkey
  • DynamoDB
  • Cosmos DB

Questions about Data & Databases

Straight answers on scope, fees and how we work. Anything else, ask us.

Ask a question

Which database engines do you work with?

PostgreSQL, MySQL, SQL Server and Oracle, their managed versions (Aurora, RDS, Azure SQL, Cloud SQL, AlloyDB, Spanner), and MongoDB, Cassandra, Aerospike, Redis, Valkey, DynamoDB and Cosmos DB.

Are you a DBA agency?

No. We are an engineering firm. We upgrade, migrate, design and automate data platforms, and run them SRE-style when you want that, with a named senior engineer rather than a ticket queue.

Do you need production access?

Not for assessments. Read-only access or exports are usually enough, and we sign your NDA first.

Do you offer 24x7 support?

No. Managed services are business hours by default, with extended hours agreed in writing for specific windows.

Start with a free 30-minute review.

Databases, cloud or AI: talk to a senior engineer about what you run and what is coming. We reply within one business day and sign your NDA on request.