What happens to my Draftbit projects if I downgrade?

A downgrade doesn’t delete or archive your work. Projects, apps, web apps published on a draftbit.dev address, and your credit balance all carry over. The change applies at the end of your current billing period, so you have until then to prepare.

Once the lower plan starts, its limits apply to new work rather than existing work. On Free that means 3 projects, 2 apps per project, and one REST integration per project. If you already have more, everything stays open, but Draftbit blocks creating another project or app until you are under the limit or upgrade again.

Features above the new plan lock. Below Standard, the code editor is blurred, code export and ZIP downloads stop, and you cannot set up custom domains, publish to the App Store or Google Play, or remove Draftbit branding. Custom domains you’ve already connected keep working for 30 days after the lower plan starts. After that, we disconnect them, and your web app is served from its draftbit.dev address. Below Pro, GitHub export and iOS and Android simulators are unavailable, and the plan allows one sandbox at a time. Custom MCP servers you’ve added stay in your list, but the agent stops using them. Web publishing to a draftbit.dev address works on every plan.

Seats follow the same pattern. If the organization has more editors than the new plan allows, seats go to the owner first, then to admins, then to editors in the order they joined. Anyone without a seat sees a seat limit notice and can only view apps read-only until you add seats, upgrade, or remove members. Nobody’s role changes, so they get editor access back as soon as a seat opens up. Viewers aren’t counted.

Credits you already received keep their own expiry dates, so credits from the old plan stay usable for a year after they were added.

Before the switch, export the code if you’ll lose export access, and decide where a live custom domain should point. You have 30 days after the lower plan starts before we disconnect it.