Docs/Overview
Docs/Quickstart

Deploy Your First Application

Get your code live in under 60 seconds. Zero YAML files, automated SSL certificate provisioning, and containerized sandboxing across regional edge networks.

Prerequisites

  • Node.js 18 or newer installed in your environment
  • A Git repository containing your application code
  • An active Exovon account (the Hobby tier is free and requires no credit card)
1

Authenticate

Exovon supports both interactive credential login for local development and headless environment variable authentication for continuous deployment pipelines:

Option A: Interactive CLI Login (Local Development)

Run npx exovon login. The CLI prompts for your API key and securely saves it to ~/.exovon/auth.json with restrictive 0600 file permissions.

terminal
npx exovon login

# Verify your active tenant identity:
npx exovon whoami

Option B: Environment Variable (CI/CD Pipelines)

  1. Open Exovon Dashboard → Settings → API Tokens
  2. Generate a Personal Access Token (PAT) prefixed with exo_live_...
  3. Export it in your terminal session or CI/CD secret configuration:
env
export EXOVON_API_KEY="exo_live_..."
2

Link & Deploy

Link your local project directory once to write your project configuration to .exovon/project.json:

terminal
# Link local directory to an Exovon project
npx exovon link --project "my-app"

# Trigger deployment
npx exovon deploy

Running via npx ensures your environment always invokes the latest audited release of the Exovon CLI without requiring global package installations.

Visual Deployment Reference
user@laptop:~/projects/my-app$npx exovon deploy
Linked to project my-app (id: prj_8e4b10fa)
Detected Framework: Next.js 15 (App Router)
Applying .exovonignore: excluded node_modules, .next (1.8 MB payload)
Archive uploaded to Mumbai region (asia-south1) in 420ms
[builder] Compiling production build with Turbopack...
[builder] Generating static pages (14/14) in 8.4s
[builder] Optimized container image registered in Mumbai cluster
Canary Health Probes: 10/10 healthy (18ms avg latency)
Global Anycast Edge Router updated: 100% traffic shifted
Deployed in 16.2 seconds

Deployment Command Flags

FlagDescription & Use Case
(default)Automatically detects static web apps, SSR frameworks, or custom Dockerfiles.
--staticForces edge CDN deployment for purely static assets (Vite, HTML, Astro SSG).
--dynamicForces containerized execution pipeline with dedicated serverless instances.
--root-dir <path>Targets a specific workspace package inside a Turborepo, Nx, or pnpm monorepo.
--framework <fw>Explicitly defines runtime preset: nextjs, vite, astro, remix, or docker.

Monorepo Workspaces (Turborepo, Nx, pnpm)

When deploying from a monorepo, pass the --root-dir flag or specify the Root Directory in Project Settings. Exovon inspects workspace lockfiles (pnpm-lock.yaml, package-lock.json) at the repository root and packages only required dependency subgraphs into your deployment artifact.

Excluding Files with .exovonignore

The Exovon CLI reads .exovonignore (falling back to .gitignore) prior to packaging. Excluding local node_modules, build caches, and test artifacts ensures sub-second upload speeds:

terminal
# .exovonignore
node_modules
.git
.env*.local
.next
dist
build
coverage
*.log
.turbo

Lifecycle of a Build

  1. Framework Detection — Exovon analyzes your project root:
    • Dockerfile at repository root → Isolated OCI container compiler
    • package.json with a start script → Serverless containerized application
    • Static output directory → Fast-path edge asset distribution
  2. Build Execution — Code compiles in an isolated container instance with dedicated vCPU and RAM.
  3. Image Registry — Built containers are stored in the regional Mumbai (asia-south1) container pool.
  4. Zero-Downtime Rollout — New revisions are health-checked prior to shifting traffic, ensuring zero user-facing disruptions.
  5. Live Edge URL — Immediate distribution under an assigned .exovon.co.in domain.
3

Manage Environment Variables & Secrets

Never commit sensitive credentials to source control. Exovon encrypts environment variables at rest using AES-256 GCM and mounts them directly into memory at runtime.

Add or Update Variables via CLI

terminal
npx exovon env add DATABASE_URL "postgresql://..." --project "my-app"
npx exovon env add STRIPE_KEY "sk_live_..." --project "my-app"

Sync Variables to Local Development

terminal
# Writes to .env.local:
npx exovon env pull --project "my-app"

# Writes to specified file:
npx exovon env pull .env.staging --project "my-app"
Architecture Guarantee:

Secrets are never baked into container layers or build logs. They are mounted ephemerally in memory at container instantiation.

4

Configure a Custom Domain

Every deployment receives an automatic *.exovon.co.in domain. To connect your production domain with automated TLS 1.3 certificates, add the following DNS records at your registrar:

Subdomains (e.g. app.domain.com or www.domain.com)

TypeHost / NameTarget / ValuePurpose
CNAMEapp (or www)router.exovon.co.inRoutes traffic to Anycast edge network
TXT_exovon-challenge.app[token-from-dashboard]Domain ownership verification for SSL

Apex / Root Domains (e.g. domain.com)

TypeHost / NameTarget / ValueRegistrar Compatibility
A (Primary)@172.67.182.1Universal DNS support across all registrars
A (Secondary)@104.21.70.1Anycast failover redundancy IP
TXT_exovon-challenge[token-from-dashboard]Domain ownership verification

Common Diagnostics

SymptomRoot CauseResolution
API_KEY_NOT_FOUNDMissing API token in environment or local auth fileExecute npx exovon login or set EXOVON_API_KEY.
PORT_BIND_ERRORContainer failed to bind to assigned portVerify your server listens on process.env.PORT || 8080.
GATEWAY_TIMEOUTRequest execution exceeded maximum durationOptimize server response time or offload long-running tasks to background workers.