Our Stack · Fly Docs
fly.io · 292 words · saved by 1 readers
Documentation and guides from the team at Fly.io.
*)]:mx-auto [body_:where(&>*)]:max-w-2xl [body:not(.toc)_:where(&>*)]:lg:mx-[calc(50%-min(50%,35rem))] [body_:where(&>*)]:lg:max-w-3xl min-w-0 relative"> Our Stack Our platform, the stuff that actually runs apps for our customers, is built on Rust and Go. Developers on all of our platform teams switch-hit between those two languages. We love them both, and that's an attribute we're looking for in platform devs. When a user aims their browser at an app hosted on Fly.io, they're talking to fly-proxy , a Rust / Tokio / Hyper proxy that powers our Anycast network. fly-proxy uses attache , our Go S
related reading
- Fly.io makes infrastructure easy for developers | by Pekka Enberg | Turso blog | Mediummedium.com
- Carving The Scheduler Out Of Our Orchestrator · The Fly Blogfly.io
- The Design & Implementation of Sprites · The Fly Blogfly.io
- IPv6 WireGuard Peering · The Fly Blogfly.io
- Oxide Computer Companyoxide.computer
- Architecture · OrbStack Docsdocs.orbstack.dev
- Tailscale: How it workstailscale.com
- Rethinking Serverless with FLAME · The Fly Blogfly.io
- firecracker/docs/design.md at main · firecracker-microvm/firecrackergithub.com
- Protocollie Claude Code Vibe Coding setupgist.github.com
- Gigalixir - Deploying The Full Power of PaaS Production Applicationsgigalixir.com
- Istio / FAQistio.io