Customer hosting
Sign up, choose a test plan and create your first managed app.
Create your workspaceLink to this section: Create your workspace
Sign in with Zitadel and open /signup. Accept the terms, privacy notice and acceptable-use policy. Your customer organisation is separate from the operator and other customers. Customer organisations currently support one member; invitations do not grant Zitadel access.
Choose a planLink to this section: Choose a plan
Open Billing and choose Stripe or Razorpay and a plan. Approve the exact checkout request under Approvals, then open its billing session and confirm the simulated payment. No payment details or money are involved. Hosting becomes ready after the worker prepares your workspace.
Create an appLink to this section: Create an app
Open Customer panel and choose WordPress, Static site, Content site, SaaS app, Directory or Local business. Give it a name and short name. Approve each hosting, database and DNS request under Approvals. Repositories are prepared automatically in simulation. Setup continues after each approval; database-backed templates receive a separate Postgres database and simulated required secret references. A repeated request with the same template and name resumes the same draft.
Templates use the existing versioned monorepo catalogue. WordPress uses the existing WordPress with MariaDB service and has no Git repository. The reserved example.test address is a simulator address.
Review and deployLink to this section: Review and deploy
Open the app workspace from Customer panel. Use Releases to review a release and Deployments to deploy it. The first public launch always waits for launch approval. WordPress starts through its approved service operation; edit its pages in WordPress when live hosting is separately enabled.
Limits and isolationLink to this section: Limits and isolation
Plan limits are enforced on the server and include pending resource requests. An expired or suspended workspace cannot create resources. Site and resource links belong to your workspace, including when someone changes an ID in a URL or API request.