Dashboard

Enterprise

Infrastructure design, at the scale of your organization

Every team gets a senior architect's review on every repository, with the controls your security team expects: single sign-on, IP allowlists, an audit log and your own AI provider.

For every team

One standard for every repository

Platform teams set the rules once; product teams get a reviewed design in minutes instead of weeks.

Teams and roles

Owner, admin, member and viewer. Invitations bound to a GitHub account, shared projects.

Reviews on every PR

Infrastructure, cost and security impact commented on each pull request, before merge.

Deployment in one click

Through your own GitHub Actions, followed live in Brunel, with credentials we never store.

Your AI provider

Run Brunel's architect on your provider and key, billed by your provider.

Security controls

Access, the way your security team wants it

Set by the team's owner and admins, enforced on every request, and recorded in the audit log.

Secrets sealed with AES-256-GCM, bound to their owner

Brunel Access

Your own sign-in page in front of the workspace: identity provider or GitHub, allow and block policies by group, domain, network or country, every decision audited.

Single sign-on

OIDC with Google Workspace, Microsoft Entra, Okta or any provider, optionally required for every member.

IP allowlist

IPv4 and IPv6 ranges, applied to every request, from the browser and from API keys.

Session length

Force members to sign in again after a set number of hours.

GitHub organization

Only members of your GitHub organization can join or sign in.

Audit log

Invitations, roles, sharing, deployments, security changes: who did what, and when.

Sign everyone out

End every member's sessions and API keys in one click.

Questions

Enterprise FAQ

Can we put our own sign-in in front of Brunel?
Yes, with Brunel Access. Members can use enterprise SSO with directory-provisioned identities or link their existing Brunel account to your company's page: your identity provider (Okta, Microsoft Entra ID, Google Workspace or any OIDC provider) or their GitHub identity, checked against your allow and block policies (email domain, groups, GitHub organization, IP ranges, countries). Every decision goes to your audit log.
Can Brunel use our own AI provider?
Yes. Set your provider, model and key (OpenAI, Claude, Mistral or any OpenAI-compatible endpoint) for the whole team. The key is tested, sealed, and never shown again. Prices and files still never come from the model.
Does Brunel get access to our cloud accounts?
No. Deployment runs in your GitHub Actions, with credentials that stay in your repository: GitHub OIDC to AWS (no stored key) or your own GitHub secrets. One-click deployment only asks GitHub to start the workflow; Brunel never receives cloud credentials.
How is the Enterprise plan billed?
By contract, with invoicing. Tell us about your team and needs with the form; every request is read by the team and answered by email.
Where is data stored?
The production app runs on AWS in the Paris region. Repositories are deleted right after analysis; only the extracted facts and short excerpts are kept. See the security page for details.

Talk to us

Tell us about your team, your repositories and your constraints. Every request is read and answered by email.

Contact the team Compare plans

The Brunel ecosystem

Infrastructure and programs

Works with

  • Works with Claude
  • Works with OpenAI
  • Works with Mistral AI
  • Works with Amazon Bedrock

Hosted on AWS in Paris (eu-west-3). “Works with” badges identify the providers supported by Brunel.

Enterprise: SSO, audit log and IP allowlists · Brunel