BitzStack is self-hosted

BitzStack is deployed on infrastructure you control — your own server or VPS — rather than a hosted service BitzStack runs for you. You're responsible for server, domain, database and any other infrastructure costs, separately from the one-time BitzStack purchase.

What's provided to help you install it

• A written, step-by-step Installation Guide included with your package.
• A full video walkthrough covering the self-hosting process end to end.
• An “AI Setup Prompt” — a ready-made prompt you can hand to any coding AI assistant to help you through your specific install.
• An optional paid Deployment Service if you'd rather have it set up for you on your own server/domain.

General install flow

Exact commands depend on the runtime your build uses, so this page deliberately doesn't guess them — they're kept accurate in the written Installation Guide and AI Setup Prompt bundled with your actual download. In general terms, expect to:

1. Extract the source package on your server.
2. Install dependencies for the included runtime.
3. Configure your environment. Most self-hosted packages ship an example environment file you copy and fill in yourself:

cp .env.example .env

4. Set up and connect your database using your own connection details.
5. Run any included migration/setup step to prepare the schema.
6. Create your first Founder/Admin login.
7. Start the application for development, then build/start it for production.

Keeping secrets safe

Generate your own values for any secrets your build uses (database credentials, an authentication secret, third-party API keys) and never commit them to source control or share them outside your team:

SECRET_KEY=<generate-a-long-random-value-yourself>
DATABASE_URL=<your-own-database-connection-string>
ADMIN_PASSWORD_HASH=<generated-locally-never-shared>

Treat every value shown in an example/template file as a placeholder to replace, never a value to reuse in production.