
The Fly-Replay Header: Your Remote Control
Need to send a request somewhere specific? Simply set the
fly-replay
header in your response! We'll pick up that request and replay it to whatever region, Machine, or app you specify. It's like a forwarding address for HTTP requests, except it actually works.
- Route to specific regions (us, eu, apac)
- Target individual Machine instances
- Forward to other apps in your org
- Handles requests up to 1MB
- Tracks replay metadata automatically
- Supports JSON for complex routing
You Don't Have To Be A Cloud Guru to Build Multi-Region Apps
Deploy your app globally, but keep your database in one place. When a write request hits Tokyo, replay it to Virginia where your primary database lives. Reads stay local, writes go where they need to. No eventually-consistent hand-waving, no "just use CRDTs bro." Just working software.

Cross-App Routing: The Platform Builder's Secret Weapon
Want to build a routing layer? A function-as-a-service platform? A custom API gateway? Route requests between apps in your organization like they're all part of one big application. Build platforms on platforms. It's turtles all the way down.
Read the Docs
Dynamic Request Routing
The complete guide to routing requests with Fly-Replay
fly-replay Header Reference
Technical documentation for the Fly-Replay header
Multi-Region with Fly-Replay
Build globally distributed apps with regional routing
Machine-Specific Routing
Route requests to specific Machine instances