A runtime built around request execution
The Apex Edge Runtime is designed for short-lived request processing: APIs, authenticated web routes, personalization, validation, lightweight transformations, and other workloads that benefit from being near the user.
What Apex manages
- Process placement across supported edge regions.
- Runtime isolation and resource limits.
- Deployment packaging and immutable versioning.
- TLS termination and request routing.
- Logs and metrics associated with the active deployment.
What your team controls
- Application code and dependencies.
- Environment variables and secret scopes.
- Route rules, cache policy, and release gates.
- External databases, queues, and third-party services.
When edge execution is a good fit
Use the edge runtime when request latency or geographic reach matters and the workload can remain stateless or use an external state system. Keep long-lived background workers, specialized network services, and storage engines in systems designed for those roles.
18edge regions
1deployment artifact
TLS 1.3managed transport
JS/TSprimary runtimes
Start with a first deployment
Create a project and validate the runtime with the smallest useful endpoint before moving production traffic.