Enterprise
Agents your teams can use, on infrastructure your security team controls.
Sophon runs in your deployment, signs people in through your identity provider, stops for a person before a risky action, and writes both the request and the decision to an append-only audit log. Only the model providers you choose see what you send them.
request
Slack thread · a.kim
- ask
- File a Jira ticket for the checkout bug in this thread
- identity
- a.kim · signed in through your IdP (OIDC)
- tool
- jira.create_issue
scope
Tenant, agent, preset
- tenant
- platform · every query filtered to it
- agent
- jira.create_issue on its allowlist
- preset
- open · interactive chat
risk
Declared, not inferred
- declared
- Medium · in the tool's manifest
- threshold
- Medium (shipped default)
- verdict
- at or above threshold · ask a person
approval
Waiting for a person
- sent to
- the Slack thread it came from
- timeout
- 5 min · a timeout is a rejection
- decided
- approved in the thread · j.ortiz
vault
Credential at call time
- backend
- hashicorp
- token
- resolved by the runtime, not the model
- prompt
- never contains it
audit
Written, then streamed
- entries
- approval.approved · tool call, Medium
- params
- SHA-256 hashed in the entry
- chain
- linked to the previous entry's hash
- sink
- Splunk HEC
06/06 Both decisions land in the audit log and stream to your SIEM.
Recreation of one run. People and tenant names are illustrative.
01The problem
Your teams want agents. Your review has three questions first.
- 01
Who is acting?
An agent running on one shared API key can't tell you which person asked for what.
- 02
What can it do without asking?
If the model decides its own limits, there is no limit for you to audit.
- 03
Where does the data go?
Every hosted assistant is one more vendor holding your prompts, documents, and credentials.
Sophon answers each one with a control outside the model: your identity provider, a declared risk gate, and a deployment you run.
02Governance
The controls sit outside the model, where a prompt can't reach them.
- Identity
- Single sign-on through your identity provider over OIDC or SAML: Entra ID, Okta, Google Workspace, Auth0, or any OIDC provider. MFA comes from your IdP, and its session policy wins over Sophon's. For local accounts, admins can require TOTP two-factor per tenant or for the whole Gateway.
- Roles
- Three fixed roles (Admin, Operator, Viewer) and as many custom roles as you need, built from a fine-grained permission catalog: who can manage agents, install skills, add connections, approve actions, or read the audit log.
- Approvals
- Every tool declares one of five risk levels in its manifest. A call at or above your threshold (Medium unless you change it) waits for a person, and Critical always does. A timeout is a rejection, never an approval. In a multi-tenant deployment any user in the tenant can answer a pending request; scope an agent to one user when only that user should.
- Audit
- Append-only: there is no update or delete path for an entry, and retention pruning is itself an audited action. Turn on the SHA-256 hash chain to detect tampering at the database level. Stream events to Splunk, Datadog, Elastic, syslog, or a signed webhook. Tool parameters are hashed in the entry, so the log shows what ran without copying its content.
- Tenants
- One Gateway hosts isolated tenants. Users, agents, memory, documents, connections, and the audit trail are separated at the data layer by query filters. The Gateway binary, installed skill code, and the license are shared.
- Secrets
- Credentials live in HashiCorp Vault, AWS Secrets Manager (with KMS encryption), or Azure Key Vault. The runtime resolves one at call time, so it never enters the model's prompt. A sandboxed skill that declares a credential does receive it, so grant connections narrowly.
Critical always asks, whatever the threshold says.
Runs2
- jira.searchNone
- web.searchLow
Asks you4
- jira.create_issueMedium
- message.sendMedium
- email.sendHigh
- os.executeCritical
Threshold Medium. 2 of 6 calls run, 4 ask you.
Recreation of Settings › Security › Approvals. Move the threshold: calls at or above it ask a person.
03Architecture
What runs where, and what crosses your perimeter.
Use the arrow keys to move between components. The details below the map update as you move.
Your perimeter
Outside, only if you configure it
Overview
Your perimeter
Everything inside the dashed line runs on infrastructure you control. Two connections leave it: prompts to the cloud model providers you configure, and the marketplace check, which you can turn off. Select a component for its connections and docs.
Leaves the perimeter
04Deployment
Three ways to run it. The same product in each.
| Option | Tiers | What you run | Scale | Docs |
|---|---|---|---|---|
| Docker Compose | Every tier | Gateway and Dashboard containers. Pro adds PostgreSQL and Qdrant; Enterprise adds Redis and RabbitMQ on a dedicated bridge network. | One host. Enterprise asks for 8 GB of RAM and 4 cores or more. | Guide : Docker Compose |
| Native .NET | Every tier | The .NET 10 SDK and `sophon start`, or the packaged Gateway binary under systemd. Without Docker, code runs in the process sandbox. | One process you manage yourself. | Guide : Native .NET |
| Kubernetes + Helm | Enterprise | The sophon-enterprise Helm chart on Kubernetes 1.28 or later, with your values file and secrets. | Gateway and Dashboard scale horizontally; RabbitMQ coordinates work. Use managed PostgreSQL, Redis, Qdrant, and RabbitMQ for high availability. | Guide : Kubernetes + Helm |
Docker Compose
- Tiers
- Every tier
- What you run
- Gateway and Dashboard containers. Pro adds PostgreSQL and Qdrant; Enterprise adds Redis and RabbitMQ on a dedicated bridge network.
- Scale
- One host. Enterprise asks for 8 GB of RAM and 4 cores or more.
Native .NET
- Tiers
- Every tier
- What you run
- The .NET 10 SDK and `sophon start`, or the packaged Gateway binary under systemd. Without Docker, code runs in the process sandbox.
- Scale
- One process you manage yourself.
Kubernetes + Helm
- Tiers
- Enterprise
- What you run
- The sophon-enterprise Helm chart on Kubernetes 1.28 or later, with your values file and secrets.
- Scale
- Gateway and Dashboard scale horizontally; RabbitMQ coordinates work. Use managed PostgreSQL, Redis, Qdrant, and RabbitMQ for high availability.
Models, in any of them
Point Sophon at cloud providers, at local models through Ollama, LM Studio or any OpenAI-compatible server, or at both. With local models and the marketplace disabled, a deployment runs without internet access: license validation never leaves the Gateway.
05Shared responsibility
Sophon ships the controls. Your deployment certifies them.
The full matrix is on the security page
Outbound connections, stated plainly.
Everything Sophon sends on its own. No usage analytics, no behavioral tracking, and license validation is offline. No conversation, memory, document, or credential data is included in any marketplace request.
Model providers you configure
Your prompts, to the providers you set up and no others. The Gateway ships with none.
Turn off: use local models only
Marketplace update check
Every 24 hours by default: which versions exist for the packages you have installed.
Turn off: Sophon:Marketplace:Enabled = false
Anonymous install counts
An instance identifier, the package name and version, and whether it was an install or an uninstall.
Turn off: Sophon:Marketplace:ReportInstalls = false
Automatic updates
Off by default. Only when an admin turns them on does the daily sweep download new package versions, checksum-verified.
Turn off: already off unless an admin turns it on
06Support
Who answers, by tier.
- Community
- Every tier. Discord and GitHub Discussions, best-effort, with no SLA.
- Pro
- Priority email support, opened through the support form with your license ID.
- Enterprise
- A dedicated support agreement: a named point of contact, onboarding help, deployment and migration support, and an SLA set to how critical Sophon is to your operations. The terms are written into your agreement, not this page.
- Security reports
- Email security@buildersoft.io. We acknowledge within 48 hours and coordinate disclosure.
07How buying works
From the first install to a signed license.
01
Read it first
The self-hosting, security and enterprise guides are public, and so is the threat model. Most security questions are answered there before a call.02
Try it on one machine
One person can install the free Personal tier with Docker and see the whole product. It is licensed for individual, non-commercial use, so a team evaluation runs under a pilot license instead.03
Pilot on your infrastructure
Tell us what you are deploying. We reply within one business day and issue a license that enables the features your pilot needs, on your own Docker, .NET, or Kubernetes setup.04
Review and sign
Your security team works from the documents below. Pro and Enterprise are licensed per organization. The key is verified offline, with no license server to reach, and a renewal is a new key installed with no downtime.
The trust package.
What exists, and where it is. Anything else your review needs, ask in the form below, and we will tell you plainly whether it exists.
Trust boundaries, technique coverage, detection coverage, and the residual-risk roadmap.
Public
Credential vault, sandbox, prompt-injection defense, rate limiting, approvals.
Public
What Buildersoft does and does not collect.
Public
The terms that govern your use of Sophon software and related services.
Public
The software license under which Sophon is used.
Public
User access review, permission matrix, approval history, credential access, and more, generated by your own Enterprise deployment for your auditors.
Your deployment
Anything else your review needs. Ask, and we will tell you plainly whether it exists.
On request
Third-party attestation
Buildersoft holds no SOC 2 report, ISO certificate, or other attestation of its own.
Not held
08Compare tiers
Personal, Pro, and Enterprise, side by side.
| Feature | Personal | Pro | Enterprise |
|---|---|---|---|
| Core | |||
| Conversations | Unlimited | Unlimited | Unlimited |
| Channels | All 17 | All 17 | All 17 |
| Skills | Included | Included | Included |
| Memory | Included | Included | Included |
| Workflows | Included | Included | Included |
| Document processing | Included | Included | Included |
| Code sandbox | Included | Included | Included |
| Infrastructure | |||
| Storage | Local, single-user | PostgreSQL | PostgreSQL |
| Built for concurrent users | Not included | Included | Included |
| Semantic memory search | Included | Included | Included |
| Vector store | Built-in (SQLite) | Qdrant | Qdrant |
| Collaboration | |||
| Users | 1 | Team | Per license |
| Shared memory | Not included | Included | Included |
| Workflow sharing | Not included | Included | Included |
| Security and compliance | |||
| SSO (OIDC or SAML) | Not included | Not included | Included |
| RBAC | Not included | Not included | Included |
| Audit logs | Not included | Not included | Included |
| Multi-tenancy | Not included | Not included | Included |
| Vault backends | Local | Local | HashiCorp, AWS, Azure |
| Deployment | |||
| Docker Compose | Included | Included | Included |
| Native .NET | Included | Included | Included |
| Kubernetes + Helm | Not included | Not included | Included |
| Support | |||
| Community | Included | Included | Included |
| Priority email | Not included | Included | Included |
| Dedicated support | Not included | Not included | Included |
| Custom SLA | Not included | Not included | Included |
09Questions
What security and procurement teams ask.
Security and compliance
Product
Buying
10Talk to sales
Tell us what you are deploying.
What the conversation covers
- Pricing and licensing for your organization
- Deployment and migration support
- Security review and compliance documents
- A pilot license for your evaluation