Resonate Cloud — the Resonate server, hosted
A server URL. We run the rest. Point your workers at it and the Async Await code you already write keeps working exactly as it does today — we run the binary and the database.
We're opening to 25 teams first. There's no form yet — on September 9, 2026 this page turns into one.
Hosted, same server
Resonate Cloud runs the same Resonate server that's on GitHub, Apache 2.0. You can read every line of what we operate for you.
Workers find the server through one URL. Moving between self-hosted and Resonate Cloud — in either direction — is a configuration change, and the same Async Await code runs on both sides of it.
We run the binary, the storage, and the upgrades. The preview has no SLA yet — it has a staffed Discord and a cohort small enough that we notice when something breaks for you.
That's the date the first cohort gets its server URLs. The list is open before then, and it's the list we work down.
No card, no invoice. Long enough to put a real workload on it and find out where it bends.
One call during the preview. What you built, what broke, what you'd need before you'd trust it with production traffic.
It's the same open-source server you can run yourself. Point your workers back at a binary whenever you want to.
When paid plans start, the preview cohort keeps a standing discount.
If you're already running Resonate, or you know the workload you'd point at us first, come tell us in Discord. We'd rather hear it now than after we've built the wrong thing.
Talk to us in DiscordWe value your privacy
We use strictly necessary cookies to run this site. With your consent we also use Google Analytics to understand traffic. We do not load analytics until you choose to allow it. Privacy Policy.