What We’re Working On Next
Building the future of resilient API infrastructure
Next
Regional Failover
Shipping in 2 weeks
The Problem:
- • AWS us-east-1 goes down (happens regularly)
- • API deployments introduce bugs
- • Regional outages return 500 errors
- • Your requests fail, users see errors
Our Solution:
# Automatic regional failover
ezthrottle.call(
"https://api.example.com/...",
failover_regions=["us-east", "us-west", "eu-west"]
)
# Tries us-east first
# 500 error? → Tries us-west automatically
# Still failing? → Tries eu-west
# Succeeds in milliseconds instead of failing
🌍 How It Works:
When APIs return 500 errors, we automatically route your request to healthy regions via Fly.io’s global edge network. Zero downtime. Zero configuration.
…
What We’re Working On Next
Building the future of resilient API infrastructure
Next
Regional Failover
Shipping in 2 weeks
The Problem:
- • AWS us-east-1 goes down (happens regularly)
- • API deployments introduce bugs
- • Regional outages return 500 errors
- • Your requests fail, users see errors
Our Solution:
# Automatic regional failover
ezthrottle.call(
"https://api.example.com/...",
failover_regions=["us-east", "us-west", "eu-west"]
)
# Tries us-east first
# 500 error? → Tries us-west automatically
# Still failing? → Tries eu-west
# Succeeds in milliseconds instead of failing
🌍 How It Works:
When APIs return 500 errors, we automatically route your request to healthy regions via Fly.io’s global edge network. Zero downtime. Zero configuration.
Soon
Static Workflows
After regional failover
The Problem:
- • Multi-step API calls fail mid-workflow
- • Manual retry logic everywhere
- • No coordination between steps
- • Lost state on failures
Our Solution:
# Define multi-step workflow
workflow = ezthrottle.create_workflow({
"steps": [
{"name": "charge", "api": "stripe", "critical": True},
{"name": "fulfill", "api": "shipstation", "retry": "1h"},
{"name": "email", "api": "sendgrid", "non_blocking": True}
]
})
# Execute - all steps guaranteed
result = workflow.execute(order_data)
🔄 Key Features:
Automatic retries, checkpointing, idempotency guarantees, and dependency management. Your workflows complete even when individual steps fail.
The Vision
Every API call should succeed. Every workflow should complete. We’re building the infrastructure layer that makes this possible.
✅
Today
Distributed rate limiting across global edge network
🚀
Next Month
Regional failover + static workflows for guaranteed completion
🌟
This Year
Intelligent routing, latency optimization, dynamic workflows
Early customers get grandfathered pricing when we raise rates
COMING SOON
Eventually Consistent Workflows
Not every task needs to be instant. Some should run overnight. Reliably. Autonomously.
Workflows You Can Trust to Eventually Finish
Research that runs while you sleep. Content that generates during meetings. Data collection that completes in the background. The aqueduct coordinates everything.
{
"workflow": "competitor_research",
"steps": [
{"search": "Find top 5 API infrastructure companies"},
{"scrape": "Extract pricing from each site"},
{"analyze": "Compare features and positioning"},
{"generate": "Create comparison spreadsheet"}
],
"webhook": "https://yourapp.com/results"
}
// Submit once. Go to sleep.
// Wake up to completed research.
The workflow runner orchestrates all rate limiting, retries, and coordination. You define the goal. We handle the execution.
🔬
Research Agents
Collect data from dozens of sources. Takes hours. You’re not waiting around.
📝
Content Pipelines
Generate, optimize, translate, publish. Multi-step workflows that just work.
📊
Data Enrichment
Process 1,000 leads overnight. Structured data. Reliable results. Done.
Want early access to workflow runners?
Start with reliable rate limiting today. We’ll invite early adopters to test workflows as we build them.
Zero Data Storage
✓ Requests processed in-memory only
✓ No database storage of request/response data
✓ Webhooks deliver results directly to you
✓ Automatic deletion if temporary storage ever needed
Built on open-source Gleam + BEAM. Code transparency for security-conscious teams. Your data flows through, never stays.
Open & Transparent
Our landing page, FAQ, and trial process are all open source on GitHub.
🔍 See Exactly How Trial Requests Work
We use email templates for trial requests. No hidden questions, no surprises. You can see the exact template before you apply.
"We’re gambling on you. We want to know who we’re betting on."
Read the README • See trial email template • Fork if you want
Join Early Adopters Building the Future
Start with reliable requests. Grow into workflows. Shape the roadmap.
Roman aqueducts: 2,000 years. BEAM: 40 years. EZThrottle: Built to last.
Start Free - 1 Million Requests →
No credit card required. Integrate in 30 minutes.