Works with
Backfire works with the runtime you already deploy
There is no SDK and no adapter layer. Anything that can POST JSON over TLS can use the relay, which is why the examples differ only in syntax.
Vercel
A Vercel function is an ephemeral process with an open outbound network. Backfire gives those invocations one authenticated egress path, so a URL that arrived in a request body is never handed straight to fetch().
Cloudflare Workers
Workers run user-triggered code at the edge with the ability to fetch almost anything. Backfire puts a validating relay between the worker and the Internet, and gives you a log that survives past the request.
AWS Lambda
Lambda functions multiply: one per endpoint, each with its own outbound code and its own credentials. Backfire collapses third-party calls into one endpoint you can key, rate-limit and audit in a single place.
GitHub Actions
CI jobs end up holding credentials for every service they touch. A relay key gives a workflow one outbound capability that can be revoked the moment a run misbehaves — and a log of exactly what it called.
Supabase Edge Functions
Edge functions are Deno processes with fetch() and little else. Backfire gives them a target-validated path out plus a record of what each invocation did, without adding a database round trip to the call path.
n8n
Automation workflows are where credentials quietly multiply: every HTTP node holds its own secrets and nothing records what a run actually called. A relay key centralises the outbound path across all of them.
Other sections
Try it with 5,000 free trips.
No card, no subscription, and the balance never expires.

