EdgeSpark combines a managed deployment platform with a runtime SDK for your app. You write a Hono server, declare your app schema and buckets in the repo, and deploy to Cloudflare’s edge.Documentation Index
Fetch the complete documentation index at: https://docs.edgespark.dev/llms.txt
Use this file to discover all available pages before exploring further.
The platform
EdgeSpark has two main layers:- A deployment layer that creates projects, stores metadata, applies configuration, and manages deploys
- An edge runtime layer that executes your app globally on Cloudflare Workers
What happens on a request
Session validation
The platform validates the session and determines whether the request is authenticated.
Path-based auth enforcement
Route prefixes such as
/api/*, /api/public/*, and /api/webhooks/* determine whether login is required before your code runs.Runtime SDK binding
EdgeSpark binds the request-scoped SDK values you import from
edgespark and edgespark/http.Your code runs
Hono dispatches to your matching handler, where you can use
db, auth, storage, secret, vars, and ctx.No local EdgeSpark server
EdgeSpark does not run a separate local platform emulator for your server. For publicly created projects today,edgespark deploy updates the current default project environment directly.
Use edgespark deploy --dry-run aggressively when you want build validation without changing the live environment. Public staging support is coming soon.
Related concepts
The client object
How the runtime SDK is exposed in your server code.
Platform security
How the platform validates queries and enforces security at runtime.