Serverless & edge
One outbound HTTP path for every serverless runtime
Serverless functions make outbound calls in a dozen places, each with its own timeout, its own error handling and no shared record. Backfire collapses that into one endpoint you can reason about — and one place where third-party credentials and safety checks live.
Where it goes wrong
Ephemeral runtimes mean retries you never see, cold-start timeouts that look like upstream failures, and no obvious way to answer "what did we call last Tuesday?" after an incident. Copy-pasted fetch calls multiply the problem.
What Backfire handles
- Works from any runtime that can make an HTTPS POST — Node, Python, Go, Deno, edge workers.
- One key per environment, revocable in a click without redeploying every function.
- Timeouts are clamped and enforced, so a slow upstream cannot hold your invocation open.
- A single activity log answers what was called, by which key, and what came back.
The request
example
import os, json, urllib.request
req = urllib.request.Request(
"https://backfireapi.base44.app/functions/forward",
data=json.dumps({
"url": "https://api.example.com/v1/status",
"method": "GET",
"timeout_ms": 8000,
}).encode(),
headers={
"Authorization": f"Bearer {os.environ['BACKFIRE_KEY']}",
"Content-Type": "application/json",
},
)
with urllib.request.urlopen(req, timeout=30) as response:
envelope = json.load(response)
print(envelope["upstream"]["status"], envelope["quota"]["remaining"])All use cases
Questions about this
Keep reading
Try it with 5,000 free trips.
No card, no subscription, and the balance never expires.