Docs/Overview
Docs/Architecture & Security

How Exovon Works

Exovon is a managed developer platform built on high-performance cloud infrastructure. We automate compilation, container microkernel sandboxing, zero-downtime rolling deploys, and global Anycast edge routing.

The Life of a Deployment

From Git commit push to global edge availability, Exovon automates every phase of the delivery pipeline.

1

Push to Git Repository

When code is committed and pushed to your GitHub or GitLab repository, an authenticated webhook dispatches a deployment event to the Exovon orchestrator with cryptographic HMAC SHA-256 signature validation.

2

Containerized Compilation

Exovon provisions an isolated compilation container with dedicated compute allocation and persistent cache acceleration:

  • Clones your repository securely via short-lived scoped OAuth credentials
  • Executes parallel package resolution with global cache re-use
  • Compiles production assets using multi-threaded SWC and Turbopack compiler engines
  • Packages dynamic application images inside unprivileged, sandboxed container builders
3

Container Verification & Canary Rollout

Following successful compilation:

  • Static assets are uploaded to edge object storage for Anycast caching.
  • Application containers are registered in regional container registries.
  • Containers are probed via automated startup and health checks before accepting live traffic.
  • Traffic shifts automatically: 0% → 10% canary traffic → 100% full cutover after passing error monitoring checks.
  • Automatic rollbacks trigger immediately if an error rate exceeding thresholds is detected during rollout.
4

Edge Request Routing

When an end-user sends a request:

  • DNS resolves through the global Anycast network across 300+ edge locations worldwide.
  • Edge nodes serve cached static assets, images, and pre-rendered pages directly.
  • Dynamic requests (Server Actions, API route handlers) route via optimized private transit directly to the nearest regional compute replica in your project's region mesh (e.g. Mumbai, Singapore, US, Europe) with zero hairpinning.
  • The container processes the compute workload and streams the response back with chunked HTTP transfer encoding.
Global Compute Mesh
Multi-Region Active Origin Replicas
Global Edge Layer
300+ Anycast PoPsZero Hairpinning
🇮🇳 Mumbai
asia-south1
Primary Origin
🇮🇳 Delhi
asia-south2
North India
🇸🇬 Singapore
asia-southeast1
APAC Hub
🇺🇸 Iowa, US
us-central1
Americas
🇪🇺 Belgium, EU
europe-west1
Europe Hub

Platform Stack Specifications

A breakdown of technologies powering Exovon's compute, storage, edge, and database tiers.

LayerEngine / ProviderArchitectural Role
Compute InfrastructureServerless Container MeshMulti-region serverless execution with automated regional routing across APAC, Americas, and EMEA
Microkernel SandboxGoogle gVisorUser-space syscall virtualization preventing host kernel escapes
Global Edge & DNSCloudflare Anycast NetworkStatic asset caching, TLS 1.3 termination, and volumetric DDoS mitigation
Serverless DatabaseExoStore (PostgreSQL)Serverless Postgres with built-in connection pooling, copy-on-write branching, and JIT credential leasing
Identity & Auth EngineExovon Auth SubsystemDedicated multi-tenant auth with Argon2id password hashing and tenant-owned database tables
Object StorageCloud Storage LayerDurable build artifact storage and multi-region backup replication
SSL CertificatesAutomated TLS 1.3Zero-configuration certificate provisioning and automated renewal

Container Sandboxing & Security

Defense-in-depth isolation protecting your code, secrets, and end users through microkernel virtualization.

gVisor Syscall Interception

Unlike traditional Docker hosts where containers share the host Linux kernel directly, Exovon runs every container inside a dedicated gVisor user-space kernel sandbox. System calls are intercepted in user space, neutralizing container escape vectors.

Zero-Trust Compute Boundary

Application containers execute under strictly unprivileged service accounts without access to cloud provider APIs, internal metadata endpoints, or adjacent tenant environments.

SSRF & Metadata Shielding

The internal virtual network layer isolates user containers from internal VPC endpoints and cloud metadata services (169.254.169.254), preventing Server-Side Request Forgery vulnerabilities.

Envelope-Encrypted Secrets

Environment variables and API keys are protected using authenticated AES-256-GCM envelope encryption. Secrets are never saved to disk or baked into container images; they are mounted ephemerally in RAM at runtime.

Security DomainStandard Shared VPSExovon Serverless Sandbox
Kernel IsolationShared host kernelgVisor user-space kernel
Escape VulnerabilityVulnerable to kernel exploitsSyscall virtualization barrier
Runtime IAM PrivilegesBroad server permissionsZero-trust unprivileged account
Secret StoragePlaintext environment filesAuthenticated AES-256-GCM in RAM