open source
The Command Center is open source.
Contacts, pipeline, inbox, proposals, and an AI layer that actually knows the business: most service businesses build all of it from scratch. This is that backend, already built and running a real agency, published under the MIT license. Run it yourself and own every part of it, or have us build and run a custom version for your business.
Today · Paper theme
Explore this screen100
Ordered migrations
Every schema change, in sequence
245
Automated checks
Test and verification scripts
178K
Lines of TypeScript
Across 924 source files
MIT
Fully open license
No seat limits, no usage tiers
two ways to run it
Read the code, or start with a conversation.
Neither path is the default. Self-hosting and a managed build solve different problems, and you can move between them as the business changes.
Path one
Run it yourself.
Free, MIT licensed
Clone the repository, connect your own Supabase project, and run the same Command Center codebase behind our own agency. You own the code, the database, and any AI provider key you connect. Nothing phones home to us.
- The complete source, MIT licensed, no seat limits or usage tiers
- CRM, pipeline, inbox, campaigns, proposals, and analytics in one application
- AI operations with approval gates and an audit trail, using your own OpenRouter key
- A Model Context Protocol server, so Claude Desktop, Claude Code, ChatGPT, Cursor, and Antigravity reach the same tools under the same approval rules
- Pluggable modules a workspace turns on and off, extendable from a manifest without forking
- An ordered database migration catalog and full documentation for tenancy and security
- A public roadmap, with acceptance criteria written out for every planned change
Path two
We build and run it for you.
Scoped on a strategy session
The same system, configured for how your team already works, deployed on infrastructure we manage, and kept running by the people who wrote it. This is managed execution, the same offer behind every Accelerate engagement, applied to this product.
- Your own isolated workspace, configured around your existing tools
- Migrations, updates, security patches, and monitoring handled for you
- Integrations connected: Google Workspace, Resend, Calendly, and the rest of your stack
- Direct support from the engineers who built it, not a support queue
- Training for your team and ongoing improvement as the business changes
running in minutes
Four commands to a running workspace.
The public site and fictional demo run with zero external services. Connecting a real workspace with your own Supabase project is a second step. Follow the installation walkthrough in our docs.
Read the self-hosting docsgit clone https://github.com/JohnConnorCode/accelerate-site.git
cd accelerate-site
npm ci
npm run devwhy it's open
Owning the code is the easy part. Trusting what runs in it is the work.
An agent can scaffold a CRM in an afternoon now. What decides whether you can hand it real customers is what happens the moment it acts on their behalf.
The AI proposes, a person approves
Every write an agent attempts becomes a staged proposal in an approval queue. The tool registry refuses at runtime if a tool marked read stages a write, or if a tool marked write does not.
Answers have to cite what they read
A grounded answer is rejected before you see it unless it cites receipts from tools that actually ran in that request.
Every external effect leaves a receipt
Sends, syncs, and webhooks carry idempotency keys and end in a terminal receipt, so a retry cannot fire twice and a silent failure cannot read as success.
Outside assistants get no looser path
Claude Desktop, Claude Code, ChatGPT, Cursor, and Antigravity reach the workspace over MCP through the same registry, the same impact tiers, and the same approval queue as the interface.
Records and AI spend stay yours
Your data lives in a Supabase project you own and can move. Connect your own OpenRouter key and model usage bills to you at provider cost.
Extend it without forking it
A module registers from a manifest: navigation, routes, and AI tools, inheriting the approval queue and audit ledger without touching core.
every screen
Seven screens, seven appearances.
The slider above is a preview, not the whole product. Open any screen full size, and arrow through the rest from there.
frequently asked
Questions, answered.
Everything you need to know about self-hosting and the managed build.
Don't see your question? john@acceleratewith.us
start
Book the session. Keep the plan.
A free strategy session with the engineers who would build it. We'll scope exactly what a managed build looks like for your business. You leave with a written plan. Yours to keep either way.