Deployments & Build Engine
From the instant code is pushed to your Git repository or uploaded via the CLI, Exovon's orchestration engine takes over. Builds run in parallel inside isolated, high-performance runners located physically in Mumbai (asia-south1), promoting to the global edge network with zero downtime.
4 Dedicated vCPUs
Every build runs on dedicated e2-standard-4 instances with 16 GB RAM and 100 GB NVMe storage in Mumbai.
Monorepo First
Out-of-the-box support for Turborepo, Nx, and pnpm workspaces with configurable root directories and dependency caching.
Instant Rollbacks
Switch traffic pointers to any historic healthy deployment in under 3 seconds with atomic edge routing table swaps.
1. The Deployment Lifecycle
Every deployment moves through a deterministic four-phase pipeline:
Phase 1: AST Inspection & Framework Detection
< 3 secondsThe orchestrator clones your source code, scans package.json, lockfiles, and configuration files to identify whether the project is static (Vite, Astro, CRA) or dynamic (Next.js, Remix, Node API).
Phase 2: Dependency Hydration & Compilation
~45–90 secondsGlobal package caches restore dependencies. Multi-threaded Rust compilers (SWC / Turbopack) execute your build script. Live stdout/stderr streams directly to your dashboard and CLI.
Phase 3: Containerization & Health Probing
< 15 secondsDynamic runtimes are packaged into optimized, minimal gVisor container images. The platform executes synthetic health probes on port 8080. If the container crashes or fails to respond within 30s, the build fails safely without impacting live traffic.
Phase 4: Canary Shifting & Edge Promotion
< 1 secondStatic assets promote immediately to Anycast CDN edge nodes. Dynamic applications enter canary verification (10% traffic bleed → 100% cutover) with zero dropped user connections.
2. Supported Frameworks & Auto-Detection
| Framework | Detected File | Default Output Directory | Compute Type |
|---|---|---|---|
| Next.js (App / Pages) | next.config.* | .next/standalone | Dynamic Serverless |
| Vite / React / Vue | vite.config.* | dist | Fast-Path Static Edge |
| Astro | astro.config.* | dist | Static or Serverless |
| Remix / React Router | remix.config.* | build/server | Dynamic Serverless |
| Node.js Express / Fastify | package.json (start) | . | Dynamic Serverless |
| Custom Dockerfile | Dockerfile | EXPOSE 8080 | Containerized Microkernel |
3. Monorepo & Workspace Configuration
If your application lives inside a monorepo (e.g. apps/web or packages/api), configure the Root Directory in Project Settings or via CLI:
4. Zero-Downtime Rollbacks
Exovon stores compiled build artifacts and historical containers permanently. If a breaking change ships to production, rolling back requires zero compilation:
Dashboard Rollback
- Open your project dashboard.
- Click on the Deployments tab.
- Locate any previous stable build.
- Click "Instant Rollback".
CLI / SDK Rollback
The Edge Router atomically updates routing pointers across all global nodes within 3 seconds.
Frequently Asked Questions
Do you charge for failed builds?
No. If a build fails due to a compiler error or syntax exception before promoting to live traffic, zero compute minutes are billed to your account.
How long are historical deployment artifacts retained?
On the Hobby tier, deployment history is stored for 30 days. Pro and Enterprise tiers retain immutable deployment artifacts for 1 year with instant one-click rollback availability.