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)
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.
npx exovon login
# Verify your active tenant identity:
npx exovon whoamiOption B: Environment Variable (CI/CD Pipelines)
- Open Exovon Dashboard → Settings → API Tokens
- Generate a Personal Access Token (PAT) prefixed with
exo_live_... - Export it in your terminal session or CI/CD secret configuration:
export EXOVON_API_KEY="exo_live_..."Link & Deploy
Link your local project directory once to write your project configuration to .exovon/project.json:
# Link local directory to an Exovon project
npx exovon link --project "my-app"
# Trigger deployment
npx exovon deployRunning via npx ensures your environment always invokes the latest audited release of the Exovon CLI without requiring global package installations.
.exovonignore: excluded node_modules, .next (1.8 MB payload)asia-south1) in 420msDeployment Command Flags
| Flag | Description & Use Case |
|---|---|
| (default) | Automatically detects static web apps, SSR frameworks, or custom Dockerfiles. |
| --static | Forces edge CDN deployment for purely static assets (Vite, HTML, Astro SSG). |
| --dynamic | Forces 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:
# .exovonignore
node_modules
.git
.env*.local
.next
dist
build
coverage
*.log
.turboLifecycle of a Build
- Framework Detection — Exovon analyzes your project root:
Dockerfileat repository root → Isolated OCI container compilerpackage.jsonwith a start script → Serverless containerized application- Static output directory → Fast-path edge asset distribution
- Build Execution — Code compiles in an isolated container instance with dedicated vCPU and RAM.
- Image Registry — Built containers are stored in the regional Mumbai (
asia-south1) container pool. - Zero-Downtime Rollout — New revisions are health-checked prior to shifting traffic, ensuring zero user-facing disruptions.
- Live Edge URL — Immediate distribution under an assigned
.exovon.co.indomain.
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
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
# Writes to .env.local:
npx exovon env pull --project "my-app"
# Writes to specified file:
npx exovon env pull .env.staging --project "my-app"Secrets are never baked into container layers or build logs. They are mounted ephemerally in memory at container instantiation.
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)
| Type | Host / Name | Target / Value | Purpose |
|---|---|---|---|
| CNAME | app (or www) | router.exovon.co.in | Routes traffic to Anycast edge network |
| TXT | _exovon-challenge.app | [token-from-dashboard] | Domain ownership verification for SSL |
Apex / Root Domains (e.g. domain.com)
| Type | Host / Name | Target / Value | Registrar Compatibility |
|---|---|---|---|
| A (Primary) | @ | 172.67.182.1 | Universal DNS support across all registrars |
| A (Secondary) | @ | 104.21.70.1 | Anycast failover redundancy IP |
| TXT | _exovon-challenge | [token-from-dashboard] | Domain ownership verification |
Common Diagnostics
| Symptom | Root Cause | Resolution |
|---|---|---|
| API_KEY_NOT_FOUND | Missing API token in environment or local auth file | Execute npx exovon login or set EXOVON_API_KEY. |
| PORT_BIND_ERROR | Container failed to bind to assigned port | Verify your server listens on process.env.PORT || 8080. |
| GATEWAY_TIMEOUT | Request execution exceeded maximum duration | Optimize server response time or offload long-running tasks to background workers. |