Today, we are thrilled to announce that the Fastly C++ SDK is officially Generally Available on Compute. Ideally, we’d love for this to help you bring C++ code for your gaming engines, complex glue code, and financial systems to the edge.
And because Compute compiles code directly down to wasm bytecode, your C++ programs execute with ultra-low latency within a completely memory-safe sandbox. You get native, idiomatic C++ performance without compromising security.
We designed this SDK to unlock critical functionality across three core technical patterns:
1. Legacy Modernization & Code Unlocking: Move battle-tested legacy systems directly to the edge. If you are migrating off legacy architectures like Apache Traffic Server (ATS) or old cgi-bin scripts, you can port that logic straight to the edge with Compute.
2. Real-Time Gaming Logic: C++ fundamentally powers the gaming world. With this SDK, game developers can execute latency-sensitive features right next to players—enabling things like real-time multiplayer matchmaking, low-ping server selection, and anti-cheat validation.
3. Agentic Access to the C++ Ecosystem: Modern AI agents need access to specific, highly performant toolsets. By bringing the massive array of existing C++ libraries to the edge, your agentic workflows gain a raw speed profile that origin servers simply can’t match.
The C++ SDK also hooks directly into our broader feature matrix:
-
Object Storage Integration: Deliver game patches, install data, and assets efficiently with zero egress fees.
-
Image Optimizer (IO): Power media ecosystems, user stores, and companion apps by dynamically transforming image assets on the fly from a single source of truth.
-
Polyglot Collaboration: C++ plays nice with all the other languages Compute supports, meaning your teams can collaborate even across language boundaries.
Ready to get started?
Check out our documentation and code examples for inspiration.
We want to hear from you
What existing C++ libraries are you most excited to drop into a Compute service? Are you unlocking a legacy module or optimizing a real-time system? Let us know what you’re building below! ![]()