Apex runs application code close to your customers with automatic routing, isolated runtimes, built-in TLS, observability, and progressive delivery.
Designed to fit the tools your team already runs
A single delivery workflow for code execution, routing, caching, certificates, logs, and controlled releases.
Apex places compute and cached assets at the network edge, then chooses a healthy region for each request. Use one deployment artifact across development, preview, and production.
TLS 1.3, managed certificates, signed deployments, runtime isolation, and project-level access policies are designed into the platform.
Read how it works →Apex provisions runtime capacity as traffic changes, with per-project limits, concurrency controls, and usage visibility available from the console.
Read how it works →Every pull request can create an isolated preview URL with its own environment variables and build logs, so review happens before production.
Read how it works →Define routing once. Apex continuously checks regional health and sends requests to the best available execution location. Keep stateful data in your chosen primary region while reads, cache, and compute stay distributed.
| Region | Location | Role |
|---|---|---|
| fra1 | Frankfurt | EU primary |
| iad1 | Virginia | US East |
| gru1 | São Paulo | South America |
| sin1 | Singapore | APAC hub |
| hnd1 | Tokyo | North Asia |
| syd1 | Sydney | Australia |
Select a route to inspect the corresponding region and routing role.
Use the CLI for local development and automation. Deploy the same artifact to preview or production without maintaining a separate edge configuration file for every environment.
For personal projects, prototypes, and low-traffic production sites.
$0/ month
Get started for freeFor product teams shipping multiple services and preview environments.
$29/ month
Upgrade to ProFor regulated or high-traffic workloads that need contractual commitments.
Custompricing
Talk to salesStart at $0. Upgrade when your traffic, environments, or support requirements grow. Annual billing reduces the platform subscription by 20%; compute and bandwidth usage are shown separately.
FAQ
Apex runs request-time application code and serves static assets from a distributed edge layer. You can deploy JavaScript or TypeScript workloads and expose them as web routes or APIs.
Each request is evaluated against project routing rules and current region health. Apex prefers a healthy nearby region and can fail over when a region is unavailable.
No. You manage source code, environment configuration, routing rules, and release policy. Apex manages the runtime fleet, certificates, scaling, and infrastructure updates.
Yes. Choose a primary data region for persistent storage or connect an external database. Edge execution can remain distributed while writes use a single source of truth.
A preview can be created from a branch or pull request. It gets a unique URL and its own environment configuration, then can be promoted without rebuilding the application from scratch.
Health checks and release gates can prevent promotion. Production can be rolled back to a previous deployment, while logs and request traces show the failure path.
Create a project, connect a repository, and use a preview deployment before you send traffic to production.