Case study
Zero-downtime Next.js deployments on Azure DevOps
A CI/CD pipeline on Azure DevOps with a self-hosted agent that builds, tests and deploys Next.js applications to private servers with health checks and instant rollback.
- Deployment duration
- Pending
- Downtime per release
- Pending
- Release frequency
- Pending
The challenge
Next.js applications were deployed by copying build output to servers manually. Releases caused brief outages, steps varied between engineers, and the target servers were on a private network unreachable from Microsoft-hosted agents.
The solution
We installed a self-hosted Azure DevOps agent inside the private network, built multi-stage YAML pipelines (build, test, package, deploy), and switched traffic between release directories with PM2 and Nginx only after health checks passed.
Implementation timeline
1 week
Pipeline design
Stages, environments and approvals agreed.
1 week
Agent and scripts
Agent installed, deploy scripts written.
1 week
Rollout
Applied to remaining applications.
Results
Metric pending
Deployment duration
Metric pending
Downtime per release
Metric pending
Release frequency
Tech stack
How we built it
The pipeline builds with output: 'standalone', runs tests, publishes the artifact, then the self-hosted agent extracts it into a timestamped release folder, starts the new process on a spare port, checks a health route and swaps Nginx upstreams. The previous release stays on disk for rollback.
The full method is in Next.js CI/CD on Azure DevOps.
Draft write-up of INTELLIA engineering work; figures pending measurement.
Related case studies
- Result pending · Self-service provisioning timeResult pending · Operator tickets per tenant
cross-industry · Pakistan
Private cloud console for a hypervisor platform
A self-service web console for a hypervisor-based cloud platform, covering virtual machine provisioning, networking, snapshots and usage metering for tenants.
Draft — awaiting client approval - Result pending · Service level after cutoverResult pending · Change in abandonment rate
telecom-and-contact-centers · Pakistan
Contact center modernization on Asterisk/Issabel
A contact center moved from a legacy PBX to CONVERSA on Asterisk and Issabel, gaining skills-based routing, CRM screen pop-ups, searchable recordings and live wallboards.
Draft — awaiting client approval - Result pending · Status of the engagementResult pending · Vendors onboarded in phase one
retail-and-ecommerce · Oman
Multi-vendor marketplace platform
Scoping and architecture of a multi-vendor marketplace with vendor onboarding, catalogs, bidding, order splitting and payouts, prepared for a client in Oman.
Draft — awaiting client approval
Have a project in mind?
Tell us what you are trying to achieve. A solution architect will reply within one business day with next steps — not a sales script.