Skip to content
Cloud & Platform

No-Outage Release Setup

Moving your product from single-server deploys to blue-green releases, with health checks and automatic rollback whenever a new version starts behaving badly.

14 working days₹32,999 incl. GST7 deliverables
Overview

What this service covers

If you still schedule releases for 2am on a quiet Sunday, this project ends that routine. A new version starts up and must pass health checks before any traffic reaches it, while the previous version stays running so you can switch back instantly. Database changes follow an expand-and-contract pattern, so old and new code can run side by side during a release. We rehearse the full process in staging, including a release that is broken on purpose.

Deliverables

What you receive

  • Blue-green or rolling deploys set up for your virtual machines or managed container platform
  • Health check endpoints built and tuned to your application's real startup behaviour
  • Load balancer target groups and connection draining configured
  • Expand-and-contract database change pattern written up and applied to one live release
  • Automatic rollback if health checks fail within a defined window
  • Release runbook, including the manual override steps
  • Failure drill rehearsed with your engineers observing
How it runs

The work in 4 stages

  1. Stage 1: Current-state mapping

    We trace today's deploy steps, the causes of downtime and how tightly the database is coupled.

  2. Stage 2: Groundwork

    We build health checks, the schema change pattern and the needed infrastructure updates.

  3. Stage 3: Staging rehearsal

    We release in staging, then force a failure to show rollback works.

  4. Stage 4: First live release

    The first production release is carried out together with your team.

Fit and inputs

Who it suits, and what we need from you

Ideal for

  • Products with users across several time zones
  • Teams paying a regular price for late-night releases
  • Businesses with uptime obligations written into customer contracts

What we need from you

  • Access to the application code and the environment it deploys to
  • Part-time input from a developer who understands the database schema
  • A staging setup that is reasonably close to production

You share these through the brief on your order page after checkout.

Why it helps

What changes for your team

  • Releases happen during working hours with the team available
  • A faulty release is reversed in minutes without restoring the database
  • Deployments become everyday work, not a planned event
Questions

Questions about this service

Yes. Expand-and-contract changes are precisely how systems with a single database avoid downtime while the schema changes.

That is manageable. Health checks and startup grace time are adjusted to suit, and we flag the slow start as a separate improvement to consider.

Yes, where your traffic levels and load balancer make canaries meaningful. We advise on this during the assessment.

This is a remote service: nothing is shipped physically, and the work is delivered into systems you control. See delivery and handover and refunds and cancellation for the full terms.

Related services

Often considered alongside this one

All Cloud & Platform