The support model, by plan
Forge does not run one anonymous support tier. STARTER includes community support — enough for a side project. TEAM includes priority support, built for studios whose client work has deadlines. ENTERPRISE, for regulated institutions, adds dedicated infrastructure and a signed data protection agreement, with support to match.
Why small batches
The waitlist page says it plainly: Forge is onboarding from the waitlist in small batches so early users get real support, not a support ticket queue. Join the list and you hear from them directly — one email when it is your turn, no spam. The batching is the support model: each cohort is small enough that questions get answers from people who know the platform, not from a queue.
What this looks like in practice
Because onboarding is personal, the questions that are usually self-serve elsewhere — export formats, domain records, billing quirks — are handled in conversation. See How to Export Your Data From Forge and Custom Domain Setup on Forge for the two that come up most.
Handover: when a project changes owners
Handover is the common agency case: you built a client's booking form or portal, the project is done, the client takes it over. On the TEAM plan, multiple client projects live under one account, so a handover is a matter of moving the project, transferring the domain, and exporting the data for the new owner — the same export path that serves every other purpose. The project keeps running throughout.
The practical takeaway
If you expect to need help — deadlines, clients, compliance — the plan tiers encode that: community, priority, or enterprise. And if you are deciding whether Forge fits at all, start with Who Should Use Forge (and Who Shouldn't).