Self-hosting quickstart

When you want customer work in one place, give Claude Code or Codex this repository and ask it to set up the fictional demo first. You can review the existing workflows before connecting accounts, which saves provisioning a full installation just to decide what your team needs.

The agent runs setup and verification using this guide. You choose the business identity, provide authorized account access and review the working result. A connected installation adds your own workspace, sign-in and provider configuration on top of the same interface.

Read docs/NORTHSTAR.md and then AGENTS.md. Preserve existing unfinished work. Set up the fictional demo and show me a complete workflow. When I provide authorized access to my own project, follow the installation guide to configure it, inspect the setup plan and verify sign-in, saved records and workspace isolation. Show the exact checked source and remaining setup steps; hand off deployment separately.

Explore locally

The agent needs Git, Node.js 22.16 or later and npm. These are its local setup commands:

git clone https://github.com/JohnConnorCode/accelerate-site.git
cd accelerate-site
npm ci
npm run dev

Open the local URL printed in the terminal, then visit /demo/command-center. Choose a fictional business and follow your first workflow. This path does not need email or AI provider keys.

Start with your own business identity

The full repository defaults to a neutral Command Center homepage. You receive the complete application, with Accelerate agency content disabled. Set NEXT_PUBLIC_BUSINESS_NAME and NEXT_PUBLIC_SITE_URL for your installation. This is one codebase: every installation, including ours, can enable bundled agency presentation with NEXT_PUBLIC_DISTRIBUTION_PROFILE=branded or disable it with neutral. Keep build and runtime values aligned, then rebuild and deploy. Both profiles retain the editor, AI/MCP, plugins and workspace; hosting authorization is a separate concern.

Before a database is connected, Open your workspace shows a setup screen with links to the installation guide and fictional demo. Visiting /admin/login directly shows the same next steps. First-party analytics stays inactive on an unconfigured fork, so exploring the site does not require a database connection.

After connecting your workspace, open Site Studio and choose Edit installation website. Update identity, theme, pages and navigation, connect published forms, then preview, save and publish. Website tools includes the setup sequence. Form responses use the existing review workflow, and private previews cannot submit. ChatGPT editing requires the owner-approved connection described in the Site Studio guide.

An optional reduced export is available with node scripts/export-neutral-starter.mjs --output /absolute/new/workspace. It physically omits protected media and replaces business-owned content. It is not required to fork the complete product. Follow docs/self-hosting/NEUTRAL-DISTRIBUTION.md for both profiles, asset rights, hosting configuration and verification steps. Provider connections remain yours to configure.

Connect a real workspace

Use a Supabase project and provider accounts you control. Have the agent follow Connect your installation for private configuration, the setup plan and verification steps. For version-specific details, it uses docs/self-hosting/SELF-HOSTING.md in the checkout.

Do not use an existing production database as an installation experiment. The owner identity and migration order matter; skipping a step can leave an account without workspace access.

Add providers incrementally

Start with one workflow. Connect its providers, then inspect Setup. An OpenRouter key enables configured AI workloads; a verified mail connection enables real sending. Neither is required merely to explore the demo.

Before importing real contacts, confirm that you can sign in to the intended workspace and complete a controlled test workflow. Check the action result as well as the screen's success message.

Keep your installation maintainable

Use the installation and upgrade instructions shipped with your version. Before importing customer records or upgrading, make recovery copies of the database, actual uploaded files and encryption configuration, then test a separate restoration. The recovery guide explains the file-copy commands and receipt review before reconnecting providers. Keep server credentials in local or hosting-provider secret configuration, not in source control.

Before planning an update, use Check stable releases in Setup or npm run release:check in your checkout. Connect your installation explains how an unversioned fork adopts its first published core release and how to read a supported upgrade path.

For extending the application, start with Build on it. For connecting an external assistant, see MCP client setup.