Skip to main content

open source

Keep customer work connected. Own the system behind it.

Give Claude Code or Codex the repository and describe what your business needs. Your agent can set it up and build custom screens, reports and workflows on the customer records, permissions and business services already here. Your team spends less time copying context between tools, and your agent has less foundation to rebuild. You own the MIT-licensed source and your installation.

Today · Paper theme

Explore this screen

two ways to run it

Choose who operates your installation.

Your coding agent can build on infrastructure you control. Our team can also configure, operate and improve an agreed workflow with you.

Path one

Run it yourself.

Free, MIT licensed

Start with the fictional demo, then connect a Supabase project you control. The same application runs our agency workspace. You own your deployment, data and AI provider account, and can change the source around your business.

  • 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
  • An MCP server for supported external assistants, using the workspace's permissions and action 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
Read the self-hosting quickstart

Path two

We build and run it for you.

Scoped on a strategy session

We start with the customer workflow your team needs, configure the shared workspace around it, and operate the agreed solution with you. The build, connections, support and costs are scoped before work begins.

  • Your own isolated workspace, configured around your existing tools
  • Migrations, updates, security patches, and monitoring handled for you
  • The integrations required by the agreed workflow, connected and verified
  • Direct support from the engineers who built it, not a support queue
  • Training for your team and ongoing improvement as the business changes
Book a free strategy session

your first assignment

Ask your agent to get it running.

Start with the fictional demo, then describe one workflow to build. The agent handles setup and checks; you review the working result. For your own team, provide authorized access to the accounts needed for a connected installation.

Read the self-hosting docsDescribe the workflow you want built
Give Claude Code or Codex this assignment
Set up https://github.com/JohnConnorCode/accelerate-site.
Read docs/NORTHSTAR.md, then AGENTS.md.
Preserve existing unfinished work.
Run the fictional demo and show me what works.
Then build the workflow I describe, reusing existing services.
Verify the result and show the exact source changes.
Hand off deployment separately.

Local setup commands for your agent
Run from the cloned repository
git clone https://github.com/JohnConnorCode/accelerate-site.git
cd accelerate-site
npm ci
npm run dev

Next.js 16React 19TypeScriptTailwind CSS 4SupabaseTanStack QueryOpenRouterModel Context ProtocolResendPlaywright

why it's open

Build on context your team can trust.

A new screen is useful when it can see the right records and leave a reliable result. Accelerate gives your own workflows and AI tools the same identity, permissions and action history as the workspace.

  • AI earns more responsibility

    Supported actions begin with review. After a record of successful approvals, an owner can grant eligible actions standing permission. Restricted actions keep their required human decision.

  • 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.

  • Have an agent build your next workflow

    Describe the business rules and review a working screen. The agent implements and registers the extension, reusing shared services for customer identity, access and governed actions.

inside the workspace

Follow the work across records, decisions and results.

These are real workspace screens with fictional records. Open one full size to see the context behind a task, then try the corresponding workflow in the demo.

Conversations · Paper theme
Revenue · Night theme
Feature Board · Signal theme

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.

Free30 minYou keep the written planYou talk to John