Service · Software development

High-availability system development for mission-critical applications.

Custom HA architectures for platforms that simply cannot go offline. From redundant database clusters and multi-region failover to observability and runbook discipline, all built around a concrete uptime target that fits your business case.

Multi-region failoverDatabase HASLO/SLI & error budgetsBlue-green deployment

High availability is not a checkbox, it's a design choice.

A high-availability (HA) system is a platform designed so that the failure of a single component, such as a server, a data centre, a network link or a database replica, does not cause an outage for your end users. That sounds simple, but it touches every layer of your stack: how you write your application, how your database is set up, how your network routes traffic, how your deployments run, and how your team responds when something breaks at half past two in the morning.

We design and build HA systems for organisations where downtime directly costs money or trust: payment providers, banks and insurers, telecoms, e-commerce platforms around peak moments like Black Friday, healthcare providers with an EHR, government bodies delivering critical services, SaaS vendors with SLA obligations, and energy and logistics platforms where operations run 24/7. The starting point is always the same: we begin with the concrete uptime target (99.9%, 99.99% or 99.999%) and work backwards to the architecture that fits it. Never the other way round.

We work closely with your own DevOps or platform engineers, and with our DevOps-as-a-service if that function isn't yet covered in-house. The designs we deliver end up in code (Terraform, Pulumi, Kubernetes manifests) and in runbook discipline, not just in PDF reports that get forgotten in a Confluence folder.

Three typical HA projects we build.

Which one fits depends on where you are now: a greenfield HA design, making an existing application HA-ready, or a complete multi-region or multi-cloud setup. In our first conversation we'll advise which option matches your availability target and budget.

Greenfield project · fixed sprint budget

Designing and building an HA platform from scratch

For a new application or a replacement platform, we design the architecture around a chosen availability target. Multiple availability zones, stateless application services, a database cluster with automatic failover, a load balancer with health checks and circuit breakers, and a deployment pipeline that supports blue-green or canary releases. Everything is captured in infrastructure as code straight away, so the whole environment is reproducible: by us, by you, or by a third party you bring in later.

Architecture blueprintMulti-AZ deploymentIaC (Terraform/Pulumi)CI/CD with blue-green
Brownfield project · fixed sprint budget

Upgrading an existing application to HA

You have a working application that currently runs on a single server, or that only comes back online after manual intervention when it fails. We analyse where the single points of failure are, usually in the database, in stateful application components or in network routing, and tackle them step by step: replication and automatic failover for the database, moving sessions and state out of application services, adding a load balancer, introducing a solid observability layer, and building the release pipeline that makes instant rollback possible.

SPOF auditDB replication + failoverStateless refactorLoad balancing
Enterprise engagement · fixed sprint budget

Multi-region or multi-cloud HA architecture

For platforms that need 99.99% uptime or better, and where losing an entire cloud region is a real risk. We build active-active or active-passive setups across multiple regions, with geo-DNS routing, cross-region replication for data and a chaos engineering practice that regularly simulates regional outages. Often combined with cloud-native platform development and with edge computing for low latency on traffic coming from different parts of the world.

Active-activeGeo-DNSCross-region replicationChaos engineering

What you get at the end of a project.

A working, monitored and documented HA system that meets the uptime target we agreed together — plus the runbooks, training and deployment pipeline your own team needs to run it.

  • Architecture blueprint with uptime targetA documented design with SLO, error budget, RPO and RTO per critical flow, plus the rationale behind each choice between active-active, active-passive and multi-region.
  • Production and staging environments as codeThe full environment in Terraform or Pulumi, running on AWS, GCP or Azure — or hybrid where that makes sense. Reproducible and redeployable in a new region or with a new provider.
  • Database HA and backup strategyLeader-follower or multi-master replication (PostgreSQL with Patroni, MySQL/MariaDB with Galera, CockroachDB or YugabyteDB), point-in-time recovery and a 3-2-1 backup setup that we test regularly.
  • Deployment pipeline with instant rollbackCI/CD with blue-green or canary releases, feature flags for gradual rollout, and a rollback procedure that takes minutes rather than hours.
  • Observability stackPrometheus and Grafana or Datadog for metrics and SLO tracking, OpenTelemetry or Jaeger for distributed tracing, and Pingdom or Checkly for synthetic monitoring from outside your network.
  • Runbook library and on-call setupConcrete runbooks for the most likely incidents, integrated with PagerDuty or Opsgenie. Includes a post-mortem template and the first guided DR drill with your team.
  • Training and knowledge transferWorkshops for your ops and platform engineers, plus documentation that lets a new colleague run the system independently, without you depending on us.
  • Managed service contract (optional)Monitoring, security patching, capacity planning and ongoing development. Fixed monthly price, with several response-time tiers matched to your platform's uptime target.

When an HA system is the right choice.

Four patterns we keep seeing at organisations that come to us for high-availability work. If you recognise one of them, we'd be glad to talk further.

Mission-critical

Downtime costs money or trust directly

You run a payments platform, an order flow on a large e-commerce domain, a telecom service or an EHR that healthcare professionals rely on in real time. Every minute of downtime means declined transactions, lost revenue, complaints or worse. A single-region, single-database setup is then a risk that no longer fits the volume or sensitivity of your business.

SLA pressure

You have contractual uptime obligations

Your business customers — especially larger corporates and government — demand 99.9% or 99.99% in the contract, with penalties for breaches. Your current platform doesn't meet that consistently, or you lack the measurement and evidence layer to show that you comply. SLO-driven monitoring with error budgets closes that gap on both sides.

Peaks

Traffic is erratic or seasonal

Black Friday, ticket sales, year-end closing in HR software, a media campaign: you get extreme peaks on top of a normal pattern, and you cannot afford a capacity problem at precisely that moment. Auto-scaling, graceful degradation and separating critical from non-critical flows prevent the whole application from collapsing under pressure.

Compliance

Regulators demand demonstrable continuity

DNB, AFM, NEN 7510, BIO or a sector-specific standard requires you to be able to demonstrate the continuity of your service, with tested failover procedures and a documented DR plan. A paper plan without a tested implementation no longer counts as valid evidence. We tie the design to periodic DR drills that do produce evidence, often in combination with an ISO 27001 programme.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How an HA project works with us.

1

Introduction and goal setting

A conversation in which we work out which flows in your platform are truly mission-critical, which can go down for a while, and which uptime target fits. Not every flow needs 99.99%; some need even more. We also map out what your current measurement and monitoring layer already shows, which is usually the best starting point for the design.

2

Architecture review and blueprint

A short discovery phase in which we test the current architecture against the uptime target: where are the single points of failure, where is there state we no longer want to tie to a single node, how is database replication set up, what does the network path look like? At the end you have a concrete blueprint, a sprint plan and a prioritisation of the changes with the greatest impact.

3

Building in sprints

We work in two-week sprints and deliver a piece of working improvement, validated in production, every sprint. We often start with the observability layer, because without measuring you can't tell whether a change helps, and then work towards the database layer, the application layer and the deployment pipeline. Our engineers pair with your own platform engineers where you have them; knowledge transfer is built into every sprint rather than left until the end.

4

Drills, post-mortems and ongoing management

After go-live we schedule the first DR drill: we simulate a targeted failure in a production-like environment and check whether failover, observability and runbooks do what they promised. We then join you on a chaos-engineering cadence and on post-mortems of real incidents, so the architecture and runbooks keep improving instead of slowly eroding. For disaster recovery we work, where needed, on a separate disaster recovery platform.

Frequently asked questions about high availability.

The questions platform owners, IT managers and CTOs usually ask us before a project begins.

What exactly is a high-availability system?
An HA system is a platform designed to keep functioning even when one or more underlying components fail: a server, a database replica, a network link or even an entire cloud availability zone. In practice that means redundancy at every critical layer, automatic failover instead of manual intervention, and monitoring that detects faults before your customers report them. HA is usually expressed as an uptime percentage such as 99.9%, 99.99% or 99.999%, and behind every extra nine lies a considerable jump in both architectural complexity and cost.
What is the difference between high availability and disaster recovery?
HA is about preventing downtime: redundancy, failover, load balancing and monitoring ensure that a failure in one component doesn't cascade to your end users. Disaster recovery is about what you do when a larger incident happens despite all that redundancy — a corrupted database, a region-wide outage, a security incident — and how you get back online within an agreed timeframe with your data intact. The two overlap, but they are not the same thing. A good HA system also has a DR plan; a DR plan without HA means you recover faster after a major crisis, not that you prevent minor outages.
What is the cost difference between 99.9% and 99.99% uptime?
Significant, and not linear. 99.9% allows for roughly 8.76 hours of unavailability per year; 99.99% allows only about 52 minutes, and 99.999% just under 5 minutes. Each extra nine means that things which could be fixed manually or as a one-off at the previous level must now be fully automated and redundant — more replicas, more regions, stricter deployment discipline, a dedicated on-call team and chaos engineering. In the first conversation we'll tell you which level is realistic and worthwhile for your business. Not every application deserves 99.99%; many internal tools are perfectly well served by 99.5%.
Do we need multi-region, or is multi-AZ enough?
For most Dutch applications, a multi-AZ setup within a single region is sufficient and considerably cheaper than multi-region. AZs within a region almost never fail at the same time, and the latency between AZs is low enough to support synchronous database replication. We mainly use multi-region when the business needs to rule out the loss of an entire cloud region as a real risk — typically in financial services, telecoms or internationally operating platforms — or when regulatory requirements demand data residency in several countries. We would rather advise multi-AZ with a tested cross-region DR procedure than a half-hearted active-active setup that never gets through its drills in practice.
Can you make our existing application HA-capable without rebuilding it?
In many cases, yes. We start with a SPOF audit: where does state live, where are the singleton processes, how is the database set up, and what happens during a network outage? For many applications it's feasible to work towards HA step by step — database replication and automatic failover, moving sessions out of the application, putting a load balancer in front, a solid observability layer, and only then the harder refactors. Sometimes a fundamental rebuild is unavoidable because the architecture stands in the way of HA; we'll tell you that honestly rather than promise to bolt it on with a few plug-ins.
How do you handle database HA?
It depends on the database and the requirements. For PostgreSQL we often work with Patroni or Stolon for leader-follower replication with automatic failover and point-in-time recovery. For MySQL or MariaDB, we use a Galera cluster or a managed RDS variant. Where latency and write scaling are critical, we look at multi-master solutions such as CockroachDB or YugabyteDB. We don't choose technology based on trends — we choose based on fit with your workload, your team and your operational reality, and we deliver a tested procedure for backup restores and failover drills.
Do you work with our own DevOps or platform engineers?
Almost always. HA work is precisely the kind of work that your own team has to carry after go-live — otherwise the design erodes within a year. We work in pairs with your engineers, transfer knowledge in every sprint, and deliver documentation and runbooks that new colleagues can genuinely use. If you don't have a platform team yet, we can fill the DevOps role temporarily through our DevOps-as-a-service until you have your own people in place.
What determines the cost of an HA project?
Mainly three things: the uptime target you choose, how far your current setup is from it, and how much of the work your own team takes on. A 99.9% multi-AZ project on a reasonably clean application is fundamentally different from a 99.99% multi-region setup for a legacy monolith with a lot of entrenched state. Beyond that, the choice between managed services and self-managed infrastructure weighs heavily, as does whether you hand monitoring and on-call to us or handle them in-house. We outline the range in the first conversation and always work with fixed sprint prices, so there are no surprises.
Do you also build HA for enterprise platforms?
Yes. For larger organisations we deliver HA work as part of broader enterprise software projects: integration with a corporate identity provider, change advisory boards around releases, SLA levels per system component and integration with an existing SOC or MSP. The difference from an SME project lies mainly in governance, not in the technology; the architectural principles are the same.

Talk to us about your high-availability platform.

A no-obligation introductory call of half an hour. We listen to which flows are mission-critical, to your current architecture and to the uptime target that fits your business, and we give you direction you can use straight away, even if we don't end up working together.

Edit content