Hosted vs self-hosted

The intelligence engine is one codebase. Self-hosted and hosted run the same Python — same parsers, same git analysis, same wiki generation, same MCP tools. Pick whichever fits your team.

Side-by-side

Same agent experience

Whichever you pick, your AI agent gets:

• The same nine MCP tools.
• The same proactive PreToolUse / PostToolUse hooks (if you're using Claude Code).
• The same auto-generated CLAUDE.md (with generate-claude-md on self-hosted, automatic on hosted).

The hosted MCP endpoint adds federated workspace queries — repo="all" against your entire org's repos in one call.

Pick self-hosted if

• Your code can't leave your network.
• You're an individual or small team and don't want a billing relationship.
• You want full control over the LLM provider, model, and embedding pipeline.
• You're comfortable with a Python install and one of the auto-sync options.

Pick hosted if

• You want zero ops — managed indexing, managed webhooks, push-sync.
• You want federated cross-repo intelligence across your whole org without coordinating workspace setup yourself.
• You want the security suite — CVE scanning with reachability triage, secret detection across git history, SBOM/VEX, nightly refresh, compliance reports, audit trail.
• You're running a team: seats and roles, pooled repos and credits, portfolio health and ownership rollups, and the engineering-leader dashboard with drift alerting into Slack.
• You want the Pro analysis pages (semantic search, docs explorer, coverage, federated chat) and the PR review bot.

Self-hosted under the hood

The hosted frontend (Next.js + Supabase Auth) talks to a hosted FastAPI backend over a typed REST client; it imports presentational components from @repowise-dev/ui and types from @repowise-dev/types, the same packages the OSS web UI uses. There's no fork — both modes share the engine.