Application types
FastEdge supports two application types: HTTP and CDN. The application type determines how the application integrates with FastEdge and which setup guide to follow. Modern HTTP applications receive and respond to HTTP requests directly. They implement the WASI P2wasi:http/proxy interface — the current recommended standard for WebAssembly HTTP applications. Supported in Rust (via the wstd crate) and JavaScript. Use this type for new edge services: APIs, redirects, and authentication proxies.
Legacy HTTP applications also handle HTTP requests directly, but use Gcore’s own fastedge crate rather than the WASI standard. They target WASI P1, the original WebAssembly system interface. Use it when maintaining existing applications built on the fastedge crate.
CDN applications run inside a CDN resource’s request pipeline. They implement the Proxy-Wasm specification — an open standard for WebAssembly-based proxy extensions — and can intercept traffic at four stages: on request headers, on request body, on response headers, and on response body. Supported in Rust and AssemblyScript. Use this type when extending an existing CDN-served site with edge logic.
To get started, choose the setup guide that matches the application type and language:
Both application types share the same deployment workflow:
- Compile the application to WebAssembly and upload the binary to FastEdge.
- Gcore deploys it across edge nodes worldwide. Traffic is automatically routed and load-balanced.
- When a request arrives, the runtime executes the application and returns the result to the client.
Key benefits
FastEdge addresses three operational constraints common to edge workloads: latency, server management, and isolation.- Run code close to users. FastEdge executes on the edge node closest to each request, reducing round-trip latency without relocating the origin.
- Deploy without managing servers. Gcore handles deployment, scaling, and routing across the global network. The application binary is the only artifact to maintain.
- Isolated execution per application. Each application runs in a WebAssembly sandbox, isolated from other applications on the same node.
- Write in Rust or JavaScript. Both languages have first-class SDK support. Rust covers both HTTP and CDN application types; JavaScript supports HTTP applications.
Request call limits
Each plan includes a monthly call allowance tracked at the account level across all applications; per-plan values are on the FastEdge pricing page. When the allowance is exceeded, Gcore charges for overage or suspends the account depending on the plan, rather than disabling individual applications.Current usage
Current consumption across all applications is available viaGET /fastedge/v1/me, documented in the API reference, which returns three fields alongside the active plan name and total app count.