Docs/Overview
Docs/Deployments

Deployments & Build Engine

From the instant code is pushed to your Git repository or uploaded via the CLI, Exovon automates compilation, verification, container packaging, and zero-downtime traffic shifts from Google Cloud Mumbai (asia-south1).

4 Dedicated vCPUs

Every build compiles on dedicated e2-standard-4 runner instances with 16 GB RAM and fast NVMe scratch storage.

Monorepo First

Native support for Turborepo, Nx, and pnpm workspaces with configurable root directories and intelligent lockfile dependency pruning.

Instant Rollbacks

Swap production traffic pointers to any historic healthy deployment in under 3 seconds using atomic Anycast routing table updates.

The Deployment Lifecycle

Every deployment transitions through a deterministic four-phase pipeline:

1
Phase 1: AST Inspection & Framework Detection

< 3 seconds

The orchestrator clones your source code, scans package.json, lockfiles, and project configurations to identify whether the project is static (Vite, Astro, React SPA) or dynamic SSR (Next.js, Remix, Node.js API).

2
Phase 2: Dependency Hydration & Compilation

~45–90 seconds

Global package caches restore dependencies. Multi-threaded Rust compilers (SWC / Turbopack) execute your build script. Live stdout and stderr streams directly to your dashboard and terminal session.

3
Phase 3: Containerization & Health Probing

< 15 seconds

Dynamic runtimes are packaged into minimal gVisor container images. Synthetic health checks probe port 8080. If an application crashes or fails to respond within 30 seconds, the build halts safely without disrupting live production traffic.

4
Phase 4: Canary Verification & Edge Promotion

< 1 second

Static assets promote immediately to Anycast CDN edge points of presence. Dynamic apps enter canary traffic validation before completing a full 100% traffic shift with zero dropped connections.

Supported Frameworks & Detection

Presets automatically recognized during project initialization.

FrameworkIndicator FileDefault OutputCompute Class
Next.js (App / Pages)next.config.*.next/standaloneDynamic Serverless
Vite / React / Vuevite.config.*distFast-Path Edge CDN
Astroastro.config.*distStatic / Serverless
Remix / React Routerremix.config.*build/serverDynamic Serverless
Node.js Express / Fastifypackage.json (start).Dynamic Serverless
Custom DockerfileDockerfileEXPOSE 8080Container Microkernel

Monorepos & Workspaces

If your application lives inside a monorepo workspace (apps/web or packages/api), target the package via CLI or dashboard settings:

terminal
# Deploy a specific workspace package from monorepo root:
npx exovon deploy --root-dir apps/web --project my-web-app

# Override build script for Turborepo:
npx exovon deploy --build-command "turbo run build --filter=web"

Static Asset Optimization

By default, Exovon serves static media in its uploaded source fidelity to support specialized asset pipelines. For bandwidth-sensitive production applications, you can enable Static Asset Optimization to automate modern WebP and AVIF generation during compilation.

Next-Generation Encodings

Generates parallel WebP and AVIF variants for static PNG and JPEG assets with configurable visual fidelity, reducing edge transfer weight by up to 65%.

Deterministic Timeout Ceiling

Guaranteed build stability: compression is bounded by an adjustable safety threshold (3s to 60s, default 8s). Builds safely proceed with source assets if exceeded.

Zero Runtime Overhead

Transformations occur ahead of time during build compilation before edge distribution, ensuring 0ms compute latency on live user requests.

Configuring Static Asset Optimization

  1. Navigate to your project dashboard and select Settings.
  2. Locate the Static Asset Optimization section.
  3. Enable the Optimize Static Image Assets toggle.
  4. Adjust your desired Optimization Timeout Cap (seconds) and Encoding Quality Target (%).
  5. Click Save Changes. Subsequent deployments will automatically compile optimized asset variants.

Zero-Downtime Rollbacks

Exovon retains immutable build images and compiled bundles. If an issue occurs in production, reverting traffic takes under 3 seconds:

Dashboard Rollback

  1. Open your project dashboard.
  2. Navigate to the Deployments tab.
  3. Locate any historical healthy release.
  4. Click Instant Rollback to switch active traffic.

CLI / Agent Rollback

npx exovon rollback --deployment dep_01J8ABC

Routing pointers update atomically across all Anycast edge nodes in under 3 seconds.

Frequently Asked Questions

Do you bill for failed builds?

No. If a build fails due to a compiler error or missing dependency before promoting to live traffic, zero compute minutes are billed.

How long are historical deployment artifacts retained?

On the free tier, deployment history is stored for 30 days. Paid plans retain immutable deployment artifacts for 1 year with one-click rollback availability.

Was this documentation page helpful?