Menu ▾
Sign inBook a demo Become a design partner

RigelEnterprise & self-host

Enterprise & self-host

Your cloud today. Ours soon.

Run Rigel Enterprise Beta inside your own infrastructure now, on your own model account. Hosted Rigel Cloud Coming soon keeps your model key yours, with no fallback to ours.

Get early accessTalk to us about self-hosting

Rigel centralizes cross-repo application knowledge, workflows and architecture patterns so agents build consistently across tens to hundreds of repos → How it works

01 · Two ways to run it

Self-host now, or join the waitlist.

Rigel EnterpriseBeta

Self-hosted, in Beta now.

The full platform in your cloud, on your Postgres, with model traffic through your own Anthropic key or Claude through your AWS account.

  • Docker Compose, Kubernetes or the AWS reference stack
  • Your single sign-on, your GitHub token, your keys
  • We work directly with every install during the Beta
Talk to us about self-hosting
Rigel CloudComing soon

Hosted, multi-tenant.

Install the GitHub App, sign in with your SSO, bring your own Anthropic key. We run the rest.

  • Each organisation's data isolated
  • Your key, encrypted at rest, never a platform key
  • A hosted, authenticated MCP endpoint
Join the waitlist
Shipped today, self-hostedMapImpactAutopilotPlanMCPSame build in both. Full maturity detail on each product page.

02 · Topology

Same build. Different address.

Toggle to see which boxes live where. Your model key stays yours in both.

Auto-playing · click to choose
Deployment topology Rigel Enterprise: web tier, worker tier, durable workflow engine, code-graph service, MCP server and Postgres with pgvector all run in your cloud, calling GitHub, your model provider and Voyage AI. Rigel Cloud, coming soon: the same boxes run in Rigel's cloud, and you keep your GitHub org, single sign-on, coding agents and Anthropic key. GitHuba token you issue · repo scope Your model accountAnthropic key or Claude via AWS Voyage AIembeddings · your own key Your GitHub orgGitHub App · granted per repo Your Anthropic keyencrypted · no platform fallback Embeddings providerdetails at launch YOUR CLOUD · RIGEL ENTERPRISE YOUR ORG RIGEL CLOUD · COMING SOON RIGEL CLOUD · COMING SOON · MULTI-TENANT NOTHING TO RUN install the app, sign in, bring your key NOTHING HERE in Enterprise, Rigel runs entirely in your cloud Web tierAPI + UI · autoscaled Worker tierscaled on queue depth Durable workflowsInngest · retries, no lost runs Code-graph serviceAST-based · no LLM Postgrespgvector · chart · audit MCP server20 read-only tools Your identity providerOpenID Connect sign-in Your SSOper-org · members, roles YOURS Your coding agents MCP inside your network hosted, authenticated MCP YOURS

Everything runs in your infrastructure. Model and embeddings calls go out under your own accounts.

Diagram simplified.

03 · Rigel Enterprise · Beta

The same build, in your cloud.

Not a cut-down edition. The whole platform: Map, Impact, Autopilot and Plan.

Web and worker tiers, from one image.

  • Web tier autoscaling (2 to 6 replicas) with a pod disruption budget
  • Worker tier scaled on queue depth with KEDA
  • Secrets from External Secrets Operator
  • Scheduled jobs for playbook ticks, nightly database maintenance and liveness pruning
  • Prometheus metrics endpoint and service monitor
  • GitOps-ready manifests: Kustomize and Argo CD
  • MCP server reachable inside the cluster only

Your model, your account.

Every model call goes through the Anthropic key or the AWS account you configure. Through your AWS account, model traffic stays in it.

Embeddings use Voyage AI, so code-derived text and search queries go to Voyage under your own key. Both providers bill you directly.

Rigel Enterprise is in Beta. We work directly with every self-host install.

04 · Side by side

Enterprise and Cloud, row by row.

Rigel Enterprise BetaRigel Cloud Coming soon
Where it runsYour cloud: Kubernetes or Docker hostsHosted by us, multi-tenant, each org's data isolated
DatabaseYour Postgres 17 with pgvectorRun by us
Model providerYour Anthropic key, or Claude through your AWS accountYour Anthropic key, encrypted at rest. No fallback to a platform key.
EmbeddingsVoyage AI, under your own keyDecided at SaaS launch
GitHub accessA token you issue, with repo scopeGitHub App, granted per repo
Sign-inYour OpenID Connect provider. Required for shared installs.Per-org SSO, with members and roles
MCP for your agentsRun it inside your network. No built-in auth on HTTP yet.Hosted, authenticated endpoint
Spend controlUSD caps per run, chat query and drafting sessionPlus organisation-level spend caps and billing
Merge policyBuilt-in supervisor gates. Per-org policies Coming soonPer-org configurable merge policies
Code hostGitHubGitHub

Everything in the Rigel Cloud column is in development.

05 · Requirements

What you'll need.

An install-readiness checklist for your platform team.

  • Kubernetes, or Docker hosts
  • PostgreSQL 17 with pgvector and pg_trgm
  • A self-hosted durable workflow engine (Inngest, included in the templates)
  • GitHub. GitLab and Bitbucket aren't supported today.
  • A GitHub token with repo scope for the repos you'll chart. The Dependency Upgrade Advisor also needs Dependabot alerts read and packages read.
  • An Anthropic API key, or Claude through your AWS account
  • A Voyage AI API key for embeddings and reranking
  • Outbound HTTPS to GitHub, your model provider and Voyage AI
  • Your OpenID Connect identity provider. Required for any shared deployment. Without it, the API and UI are unauthenticated.
  • GitHub Copilot code review, if you want supervised auto-merge on code-change PRs. Without it, those PRs wait for a human.
  • A writable volume for repository clones
  • Node.js or TypeScript services, for the full chart today
  • Optional: Prometheus and KEDA for metrics and worker autoscaling, a Slack MCP server for the Flight Log, Jira Cloud for bug triage
Full install guide: Docs (soon)

Coming to Enterprise

  • Helm chartComing soon
  • Licence keysComing soon
  • Air-gapped installComing soon
  • Versioned database migrationsComing soon
  • Per-org merge policiesComing soon
  • Hermetic agent sandboxComing soon

See Security & Trust for what each of these closes.

06 · Pilot

Your first week with Rigel.

A typical pilot, in the order we recommend. We walk your team through each step during the Beta.

  1. Rigel MapChart your repos.

    Run Deep Survey on a handful of related services. Each repo gets a docs PR.

  2. Rigel MapGroup a constellation.

    Assembly writes the integration graph and data-flow narratives.

  3. Rigel MCPConnect your agents.

    One config entry. Start with find_consumers on a shared package.

  4. Rigel ImpactTurn on Impact per repo.

    Risk scores and persona review start landing on pull requests.

  5. Rigel AutopilotSwitch on upgrades.

    Set the advisor's schedule. Watch the supervisor merge what passes its gates and hold what doesn't.

07 · Rollout

Rolling out Rigel.

Who does what, from install to your whole estate. One constellation at a time.

01Before you start

Your team does

Provide Kubernetes or Docker hosts, PostgreSQL 17 with pgvector, a self-hosted durable-workflow engine (bundled in our templates), an OIDC identity provider, a GitHub token, a model key or your AWS account for Claude, a Voyage AI key, and a writable volume for clones. Plan on one platform engineer for the install.

We do

Walk your team through install, the first Deep Survey and the first governed PR during the Beta.

02Week 1: one constellation

Your team does

Register the repos of one application (UI or API). Turn Impact on per repo.

We do

Review the first docs PR from Deep Survey with you.

03Expand by team

Your team does

Add teams one constellation at a time. Install Repo Guard from our template; a rollout script covers many repos at once (GitHub App install Coming soon).

We do

Help tune policies and gates as you add repos.

04Upgrades and roll back

Your team does

To roll back a repo, turn off Impact and knowledge refresh for it and remove its Repo Guard workflow. Generated docs stay in your repos, and all data stays in your Postgres.

We do

Ship upgrades. The schema is created idempotently at startup today, and versioned migrations and a Helm chart are Coming soon.

08 · Design partner program

Help shape the roadmap.

For a small number of engineering organisations running 20+ services across many repos.

What you get
  • Early access to Rigel Enterprise, and to Rigel Cloud when it opens
  • Install support from the team that builds Rigel
  • Direct input on the roadmap, including language support and merge policies
  • Design-partner commercial terms, agreed on a call
What we ask
  • Regular feedback sessions
  • A named champion and an executive sponsor
  • Willingness to act as a reference or case study, on terms we agree together
Become a design partner

Next step

Plan your install.

Talk to us about self-hostingReview Security & Trust →