At Beamable, we’ve always believed that empowering developers means removing complexity, streamlining workflows, and making live game operations as seamless as possible—whether you’re using Unity, Unreal, or something custom.
With the release of Beamable Unity SDK 3.0.0, we’re delivering on that promise in a major way.
This update isn’t just incremental—it’s a foundational shift in how Unity developers can build, manage, and operate live games with Beamable.
If you’re a Unity dev using Beamable, Unity 3.0.0 gives you:
And if you’re still on the fence about Beamable, there’s never been a better time to try it.
Here’s what we’re most excited about:
We’ve replaced the old Unity-native content tools with a brand new content manager built on our CLI. This means:
This is the future of content ops—and it’s available now.
We’ve rebuilt the Unity editor login flow using the CLI, eliminating the need to store credentials in Unity’s /Library folder. This not only improves security, but also aligns with modern engineering best practices.
The com.beamable.server package? It’s still there—for legacy reasons—but it’s effectively empty. We’ve decoupled core logic from the editor package to streamline usage and reduce clutter.
Under the hood, this release leans entirely on CLI 5.3, meaning nearly all important operations are routed through the CLI rather than HTTP calls directly from the Unity editor. That’s a huge architectural shift with some very cool implications:
We’ve made the Unity runtime smarter and leaner—no more sending heartbeat messages when PubNub isn’t in use.
From an engineering perspective, this release marks a major milestone in Beamable’s evolution. The Unity SDK 3.0:
Explore Unity 3.0.0 and see how Beamable is reshaping live game development—one release at a time.
👉 Check out the Docs