Why WASM instead of V8 isolates?+
WASM supports multiple languages (Rust, Go, TypeScript, Python), is memory-safe by design, and strictly sandboxed. V8 isolates enforce JS/TS only, with a broader attack surface (prototype pollution, etc.). Our cold-starts match or beat isolates thanks to AOT compilation.
How does the AI Gateway work?+
A single unified endpoint that proxies OpenAI, Anthropic, Google Gemini. Semantic caching (prompt embeddings), per-project/tenant budget caps, cross-provider timeout fallbacks. Observability included: tokens, cost, latency per invocation.
What about secrets management?+
Encrypted via AES-256-GCM, injected into the execution environment at runtime and never persisted on edge worker nodes.
What is the maximum execution duration?+
HTTP handlers: 60s (Pro plan), 10 min (Enterprise). Jobs: no strict duration limit, retry-safe. Streaming responses: as long as the client stays connected. Idempotency via Idempotency-Key header.
Can we deploy existing code (Deno, Bun, Express)?+
Standard fetch(request) handlers run as-is. Express middlewares can be adapted via a lightweight shim. Full legacy Node applications are recommended for aura-compute (dedicated VMs) rather than edge functions.
What is the exact billing structure?+
Free plan: 100,000 invocations + 100,000 CPU-seconds/month. Pro plan: €0.20 per million invocations + €0.00001 per CPU-ms. Zero charge for idle time (WASM sleeps). AI Gateway billed at pass-through cost + 3% margin.