A fetch handler is all you deploy
Pick a template, edit it in a built-in editor, and hit Deploy. Every deploy is a version you can activate or roll back — Workers-class runtime, not containers.
JS · TS
Runtimes
TypeScript compiled with esbuild
4
Wizard steps
Template → Details → Environment → Review
1-click
Rollback
Activate any earlier version
13
Templates in the catalog
2 live, 11 coming soon
What Edge Functions is
Edge Functions lets you run JavaScript or TypeScript fetch handlers without servers or containers. It is a separate product from Deployments: instead of Docker images, each function is a single file of standard Web API code running on a lightweight isolate runtime.
Functions belong to a project. The create wizard starts from a template — Hello World or JSON API today, with eleven more in the catalog — then asks for a name, the runtime and an environment, and opens the built-in editor with the starter code in place.
The editor auto-saves as you type, and Deploy creates a new version and activates it. Every version is listed on the Deployments tab, so rolling back means activating an earlier one. TypeScript is bundled with esbuild, and project vault variables and secrets are injected as bindings when the version starts.
Each function has Overview with its invoke URL and active version, Editor, Deployments, Logs and Settings for rename, environment references, archive and delete. A Resources view lists every function across projects. This release targets trusted code; KV, cron and multi-file sources are not included yet.
Start from working code
These are the exact starters the create wizard drops into the editor. Standard Web APIs — Request, Response, URL — nothing proprietary.
- Single-file editor with auto-save
- Deploy creates a new version and activates it
- Copyable invoke URL on the Overview when running
export default {
async fetch(
_request: Request,
_env: Record<string, string>,
): Promise<Response> {
return new Response("Hello from Flowbit Edge");
},
};Write, deploy, roll back — all in the browser
Built-in editor
A Monaco editor with a dark code theme and debounced auto-save straight to the control plane.
Versioned deploys
Every Deploy is a version. The Deployments tab lists them all and lets you activate any one.
Function logs
Console output from the active deployment, also available in the unified log viewer.
Vault bindings
Reference project variables and secrets; they are injected as Worker bindings at provision time.
Separate from containers
Edge is its own product: lightweight isolates for request handling, not Docker images.
Org-wide view
See every function across projects, filter by project, and favorite the ones you touch most.
Every Deploy is a version
A function stays draft until its first successful deploy, then active; archive it to keep it without serving. Each version moves through:
queued
Deploy requested from the editor
building
TypeScript bundled with esbuild
deploying
Starting the isolate runtime
running
Serving on the invoke URL
stopped
Not serving; redeploy or activate to resume
failed
Build or runtime error, with an event
What you can start from
| Template | What it does | Status |
|---|---|---|
| Hello World | Return a plain-text greeting from the edge | Live |
| JSON API | Respond with JSON including path and timestamp | Live |
| CORS | Add CORS headers to requests | Coming soon |
| Reverse proxy | Forward requests to an origin | Coming soon |
| Rate limiter | Throttle requests by IP | Coming soon |
| AI gateway | Proxy AI provider calls from the edge | Coming soon |
| Auth middleware · Load balancer · Static · SSR · Image optimizer · Cache worker · Redirect | More starters in the catalog | Coming soon |
Common questions
How is this different from Deployments?
Deployments run Docker containers. Edge Functions run single-file fetch handlers on a lightweight isolate runtime — faster to start and nothing to build.
Can I use multiple files or npm packages?
Not yet. This release is a single-file editor; multi-file source trees are on the roadmap.
Are KV, cron, or Durable Objects available?
No — KV, Durable Objects, cron triggers, queues, and WebSockets are out of scope for this release.
Is it safe for untrusted multi-tenant code?
This release targets trusted code. A hardened sandbox or a managed edge provider is a later milestone before multi-tenant production.
Deploy your first Edge Function
Pick a project, start from Hello World, and ship in seconds.

