Since PartyKit joined Cloudflare, all of our energy has gone into PartyServer. Itâs the same model you know from PartyKit (rooms, connections, broadcasting, hibernation), but it runs as a regular Worker with Durable Objects on your own Cloudflare account. Every new feature lands there, itâs what the Cloudflare Agents SDK is built on, and it doesnât need us in the middle.
So weâre shutting down the hosted PartyKit platform: projects on *.partykit.dev, and deploying with npx partykit deploy.
Timeline
| Date | What happens |
|---|---|
| Fri 9 Oct | No new projects or preview environments. You can still redeploy existing projects. |
| Mon 12 Oct | Projects with no activity in the last 3 months are removed. |
| Fri 16 Oct | Deploys are turned off. This is the deadline to export your data, or to ask us for help. |
| Fri 23 Oct | The hosted platform shuts down. Remaining projects and their room data are deleted. |
| Fri 23 Oct | npx partykit deploy to your own Cloudflare account stops working too. Workers already in your account keep running; use wrangler deploy. |
What you need to do
Starting something new? Use PartyServer. Install it, write a server class, and deploy it with wrangler:
npm install partyserver partysocket
npx wrangler deploy
The PartyServer README has a full example, and it works on the Workers free plan.
Have an existing project? Follow the migration guide. For most projects itâs a small diff: your server class extends Server from partyserver, partykit.json becomes wrangler.jsonc, and your partysocket clients keep working once you point them at the new host.
Need your room data? Data stored with this.room.storage lives in PartyKitâs Cloudflare account, and we canât move it into yours for you. Export it before Friday 16 October, while you can still redeploy. The guide has an export endpoint and a copy script that move rooms straight into your new PartyServer project.
Already deploying to your own Cloudflare account (with cloudflare in partykit.json)? Your Workers keep running, but npx partykit deploy goes through our API, so it stops working on 23 October. The guide covers switching to wrangler.
Running something people depend on?
If your project has real users, lots of room data, or you just canât make these dates, tell us before Friday 16 October on Discord. Weâll keep your project running past the deadlines and help you move it, including your data. Some of you will hear from me directly.
What isnât going away
- PartyServer, partysocket and y-partyserver are actively maintained at cloudflare/partykit.
- Workers youâve already deployed to your own Cloudflare account keep running.
- The PartyKit Discord stays open, and itâs still the best place to ask for help.
Thank you
Thank you to everyone who built with PartyKit. Seeing what you made, from games and whiteboards to cursors on every website, has been the best part of this whole thing đ
Letâs keep partying on PartyServer đ