Skip to main content
Flow runs dynamic server-side functions in a Deno-compatible JavaScript/TypeScript runtime. Base path: /v1/flow/functions Flow is a good fit for HTTP APIs, webhooks, lightweight backends, scheduled integrations, and request-driven automation.

Deploy

Package source files into a new function revision.

Invoke

Forward application traffic through an authenticated endpoint.

Observe

Inspect logs, revisions, progress, and rollback state.

​
Function lifecycle

  1. Create a function by sending its name, entrypoint, and assets.
  2. Wait for the returned revision to finish provisioning.
  3. Invoke the function through its ECS route.
  4. Redeploy when source files change.
  5. Roll back to a known revision when a release needs to be reverted.
New and redeployed functions can remain in provisioning while the revision is prepared. Use the status endpoint instead of assuming that a successful create response means the function is already ready.

​
Permissions

All Flow routes require an ECS API key: Keep deployment permissions separate from runtime invocation permissions when different systems own those jobs.

​
Function contract

Your entrypoint must start an HTTP server and return valid HTTP responses. Your function owns its application-level authentication and authorization. The ECS authorization header is removed before traffic is forwarded to function code.

​
Status values

Resource statuses: Revision statuses include queued, building, succeeded, failed, and skipped.