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.

Run log · jira.create_issue
  1. 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
  2. scope

    Tenant, agent, preset

    tenant
    platform · every query filtered to it
    agent
    jira.create_issue on its allowlist
    preset
    open · interactive chat
  3. risk

    Declared, not inferred

    declared
    Medium · in the tool's manifest
    threshold
    Medium (shipped default)
    verdict
    at or above threshold · ask a person
  4. 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
  5. vault

    Credential at call time

    backend
    hashicorp
    token
    resolved by the runtime, not the model
    prompt
    never contains it
  6. 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.

  1. 01

    Who is acting?

    An agent running on one shared API key can't tell you which person asked for what.

  2. 02

    What can it do without asking?

    If the model decides its own limits, there is no limit for you to audit.

  3. 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.
Medium (default)

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.

Select a component to see what it connects to and where the docs describe it. Two connections leave your perimeter, and both are yours to turn off.

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.

  • 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.
    Docker Compose guide
  • 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.
    Native .NET guide
  • 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.
    Kubernetes + Helm guide

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.

Model providersOffline licensing

05Shared responsibility

Sophon ships the controls. Your deployment certifies them.

Buildersoft holds no attestation of its own. What Sophon provides, and what stays with you, line by line.
InfrastructureSophon shipsRuns entirely in your deployment. Data is stored only there.You ownRegion, cloud or site, host hardening, physical security.
IdentitySophon shipsSSO over OIDC or SAML, RBAC with custom roles.You ownMFA comes from your identity provider; admins can require TOTP two-factor for local accounts. Session and conditional-access policy in your IdP, role assignments and access reviews.
ActionsSophon shipsDeclared risk levels and a gate enforced outside the model.You ownThe threshold, per-tool overrides, and who may answer.
EvidenceSophon shipsAppend-only audit, optional hash chain, compliance reports and export.You ownRetention, your SIEM, and the audit itself.
CertificationSophon shipsThe technical controls SOC 2, ISO 27001, HIPAA, and GDPR require.You ownCertifying your deployment. Buildersoft holds no attestation of its own.

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

Source: the privacy policy, section 2

06Support

Who answers, by tier.

Enterprise response terms are written into your support agreement, so they are a commitment rather than a line on a web page.
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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.

  • MITRE ATLAS threat model

    Trust boundaries, technique coverage, detection coverage, and the residual-risk roadmap.

    Public

  • Security documentation

    Credential vault, sandbox, prompt-injection defense, rate limiting, approvals.

    Public

  • Privacy policy

    What Buildersoft does and does not collect.

    Public

  • Terms of service

    The terms that govern your use of Sophon software and related services.

    Public

  • End user license agreement

    The software license under which Sophon is used.

    Public

  • Compliance and audit reports

    User access review, permission matrix, approval history, credential access, and more, generated by your own Enterprise deployment for your auditors.

    Your deployment

  • Security review material

    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 comparison of the Personal, Pro, and Enterprise tiers
FeaturePersonalProEnterprise
Core
ConversationsUnlimitedUnlimitedUnlimited
ChannelsAll 17All 17All 17
SkillsIncludedIncludedIncluded
MemoryIncludedIncludedIncluded
WorkflowsIncludedIncludedIncluded
Document processingIncludedIncludedIncluded
Code sandboxIncludedIncludedIncluded
Infrastructure
StorageLocal, single-userPostgreSQLPostgreSQL
Built for concurrent usersNot includedIncludedIncluded
Semantic memory searchIncludedIncludedIncluded
Vector storeBuilt-in (SQLite)QdrantQdrant
Collaboration
Users1TeamPer license
Shared memoryNot includedIncludedIncluded
Workflow sharingNot includedIncludedIncluded
Security and compliance
SSO (OIDC or SAML)Not includedNot includedIncluded
RBACNot includedNot includedIncluded
Audit logsNot includedNot includedIncluded
Multi-tenancyNot includedNot includedIncluded
Vault backendsLocalLocalHashiCorp, AWS, Azure
Deployment
Docker ComposeIncludedIncludedIncluded
Native .NETIncludedIncludedIncluded
Kubernetes + HelmNot includedNot includedIncluded
Support
CommunityIncludedIncludedIncluded
Priority emailNot includedIncludedIncluded
Dedicated supportNot includedNot includedIncluded
Custom SLANot includedNot includedIncluded

09Questions

What security and procurement teams ask.

Security and compliance

Product

Buying

10Talk to sales

Tell us what you are deploying.

We reply within one business day.

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

Your use case, timeline, and anything your security review will ask for.

Or email hello@buildersoft.io