Enterprise
Verification, stood up by the person who built it
The software is free to download and run. Consulting starts at $10,000 a month: hands-on installation, your agents and CI connected, release gates defined with you, custom checks built, your team trained, and a monthly report on how reliable your agents actually are.
What $10,000 a month buys
An engagement is hands-on work on your repositories, with you, by the person who builds the product. Section 1 of the agreement you sign covers every line below.
Months one and two
- Excellent installed and configured in your environment.
- Your AI agent, model provider, repositories and CI connected.
- Two to four release gates defined with you, and agreed in writing.
- One or two custom verification integrations or evidence sources built for your workflow.
- One or two training sessions for the people who will operate it.
Every month after
- A monthly report on agent reliability: attempt pass rates, and what was verified versus returned.
- A weekly working session, with async support in between.
- Direct access to the person who builds the product — not a ticket queue.
- Release-rule review as your gates change, and new evidence sources as you need them.
What an engagement does not promise is an improvement. It promises a valid measurement and a serious attempt to find one, month over month — and it says plainly when no safe improvement was found.
The commercial terms
Quoted from the Verification Services Agreement you would sign, version 2.0, dated 23 September 2026.
- Price
- Starts at $10,000 per month, billed monthly in advance through Stripe. Stated and charged in U.S. dollars, exclusive of taxes. A larger scope is a higher monthly fee, agreed in writing before the work is done (§2).
- Time commitment
- The base fee buys approximately eight hours a week of hands-on time, averaged across the month, on the priorities you set. Work beyond it is $275 an hour, billed only for hours agreed in writing in advance and invoiced separately (§3).
- First payment
- The first month's fee is due at signing. There is no separate deposit, and recurring billing starts one month later.
- Term
- Month to month, with no minimum term — the agreement says so in terms (§4). Cancel any time from the client portal or in writing; billing stops at the end of the month already paid for, with no termination fee.
- Documents
- Three, signed electronically in the client portal: the Verification Services Agreement, a mutual NDA, and a liability limitation acknowledgment.
- Work product
- Deliverables, configurations and code built for you in your workspace are works made for hire and are yours on creation (§6).
- Governing law
- The laws of the State of California, United States of America, with exclusive jurisdiction in the state and federal courts located in California (§12).
- Software licence
- Nothing to buy, and the agreement says so (§7). The software you run yourself is free, for one developer or a whole team, with no seats and no metering, under the licence published with it; it is licensed, not assigned, and cancelling the engagement does not end your right to keep running it. Consulting is the only thing we charge for.
Where it runs
Four shapes, with their real status. Excellent is local-first: the only deployment we operate is none of them.
Local — one developer
AvailableThe CLI on the developer's machine. Everything stays there.
- Tasks, attempts, the evidence collected, results and receipts live in a data directory on that machine (~/.excellent by default).
- No Excellent account is needed to run it, and we do not operate a cloud that holds a copy.
- You bring your own model key; agents bill to your account, never to ours.
CI
ExperimentalExcellent watches the CI you already run and takes its result as evidence.
- It reads the CI you operate (GitHub Actions or GitLab) through a checked-in config file. There is no Excellent-hosted runner and no build of ours in your pipeline.
- Treat it as early software — it is the least exercised path on this page, and worth scoping on the call before you plan around it.
Self-hosted team sync
BetaA small server you run — Docker, DigitalOcean or any VPS. Excellent never hosts or sees it.
- Typical hosting cost is $4–12 per month, billed to you by your provider; the provisioning default is a $6 DigitalOcean droplet. We charge nothing for it and there are no seats.
- Each device authenticates by signing a challenge with an Ed25519 key, checked against an allowlist on your server. You add and remove devices in that file yourself, and the relay re-reads it whenever it changes — so both joining and revoking take effect without a restart.
- It is off unless you turn it on, and an unset or mistyped value behaves as solo.
- Not zero-touch: a teammate joins from the command line, not from the app — the in-app switch takes a relay address but no workspace id, so it cannot join an existing workspace — and adding them still means editing the server's device allowlist by hand. There is no roster API.
- The server speaks plain HTTP. TLS comes from a reverse proxy the provisioning recipe sets up when you give it a domain; without one, plain HTTP is safe only on a trusted LAN, a VPN or a tunnel.
- Verification runs never leave the machine that produced them, and gate receipts are excluded from team exchange — so a teammate cannot yet open the proof behind your result.
- Machines doing the editing must be Apple Silicon Macs. The server itself can be Linux.
Hosted or managed by Excellent
Not availableWe do not run any part of your installation.
- There is no Excellent-hosted tier, no managed primary and no hosted runner. Whether to build one is an open decision, not a roadmap commitment — so there is nothing here to join, and we would rather say that than take your email for it.
- During a consulting engagement we work inside your environment, on infrastructure you own and can switch off.
Identity, access and audit
The short answer is that there is no SSO. Here is the whole list, so nobody has to email to find out.
- Single sign-on (SAML or OIDC)Not available
- There is no SAML or OIDC integration in the product, and no date we could honestly give you for one. If your policy requires every tool to sit behind your identity provider, Excellent does not meet it today.
- SCIM or directory provisioningNot available
- No directory sync. A teammate is added by hand: they run `sync pair`, send you their device line, and you add it to the allowlist on your own server. Joining is command-line only — the in-app team switch takes a relay address but no workspace id, so it cannot join an existing workspace.
- Roles and permissionsAvailable, with a caveat
- There are two layers. A workspace member is an owner or a member, and owner-only actions — changing someone's role, removing a member, revoking a device — are refused for anyone else. Above that sits a capability graph with built-in Owner, Member and Viewer roles, attached to actors rather than to people, so an agent can be scoped the same way a human is. The caveat: a workspace where no role has been assigned to anyone permits everything. Assigning the first role is what switches enforcement on.
- Tamper-evident event logAvailable
- Changes are appended to a hash-chained log with signed checkpoints, each signature chained to the one before it, so removing or rewriting an entry is detectable rather than silent. Role and grant changes are written to it. You can verify the chain from inside the app; it stays on the machine and is never synced.
- Audit-log exportNot available
- Verifying the chain is something you do in the app. There is no export of that log as a product feature, and nothing streams to a SIEM.
- Device identityAvailable
- Devices authenticate by signing a challenge with an Ed25519 key, checked against an allowlist on the server you operate. There is no invite link for team sync and no token-rotation path: you edit the allowlist yourself, by hand.
- Device revocationAvailable
- You remove the device from the allowlist on your own server — revocation is something you do, not something you ask us to do, and there is no console for it. The relay re-reads the roster when that file changes, so it takes effect on the device's next request without a restart, dropping its key, its live session and its bearer tokens together.
Status as of 23 September 2026. If a control you need is not named here, ask security@excellent.so rather than assuming it exists.
For your security review
The questions a procurement pack asks, answered here or pointed at the page that answers them.
- Where the data lives
- On the machine Excellent runs on. The security page lists what it keeps, what can leave, what is encrypted and what changes when you turn team sync on — each statement checked against the product source. Read the security page →
- Privacy policy and subprocessors
- The privacy policy covers the CLI, this site, accounts and consulting, and names the services we rely on. Read the privacy policy →
- Data processing agreement
- No DPA is drafted yet, and we would rather say so than imply one is sitting in a drawer. Tell us which entity is contracting and which jurisdiction it has to satisfy and we will have one drawn up to those requirements; it is queued with the rest of our legal review. If your process needs a signed DPA before work can start, say so early, so that the drafting is not the thing that delays you. security@excellent.so
- SOC 2 and penetration testing
- Neither report exists today. A SOC 2 Type 2 audit is in progress: the budget is approved and the work has started, but nothing has been audited, no auditor has issued an opinion, and there is no report to send you. We are targeting the report by September 2027 — a target for a report, not a date on which we become certified. There is no third-party penetration test and no target date for one. If you need a compliance artefact to buy today, we are not there yet, and we would rather you know now.
- Status page
- None. There is nothing of ours in your critical path to report on, and we would rather say that than link a page nobody updates.
- Install integrity
- CLI releases publish a SHA256SUMS file, and the install script served from excellent.so refuses to install bytes it could not verify: a missing checksum file, a missing entry, no hashing tool on the machine, or a mismatch all exit non-zero, with one documented environment variable as the deliberate opt-out. The checksum file itself is not signed, so it protects against a corrupted download rather than against someone who controls the bucket. There is no signed or notarized download to verify independently yet. See the install page →
- Security contact and disclosure
- Send reports, and vendor security questionnaires, to security@excellent.so. Every security report is answered and we aim to acknowledge within three business days. There is no paid bounty program. security@excellent.so
- What a consultant can reach
- Only the access you grant, on infrastructure you own and can switch off — there is no Excellent-hosted system for your code to land in. Confidentiality is covered by the mutual NDA signed alongside the agreement, and anything built for you is yours on creation.
- Who you contract with
- Excellent Software, LLC — the registered entity behind excellent.so, which the agreement refers to as Excellent. The agreement names both parties, assigns the work product to you, and is governed by the laws of the State of California, United States, with exclusive jurisdiction there. The registered address is not published on this page; email hello@excellent.so for the address line a vendor-onboarding form asks for. hello@excellent.so
Brief for your CTO
Most of this decision gets made in a room you are not in. The verification walkthrough is a ten-slide brief built for that room: why an agent’s completion claim is not enough, how attempts, checks, evidence and receipts fit together, how a result gets decided, what the engagement looks like month to month, and the price. You can tailor it to your team’s role, size, stack and priorities, share the link, or print it to PDF.
Questions we get asked twice
No. There is no SAML, OIDC or SCIM support, and no published date for it. What does exist is owner and member roles, a capability graph with Owner, Member and Viewer, and device keys checked against an allowlist on a server you control. If SSO is a hard requirement, say so on the call — it is a real gap, not an oversight.
Yes. Roles attach to actors rather than to people, so an agent gets scoped the same way a human does — read everything, mutate only its own work, or a narrower grant you define. One caveat worth knowing before you rely on it: a workspace with no roles assigned to anyone permits everything, and assigning the first role is what switches enforcement on.
Yes, and today that is the only way it runs. The CLI works entirely on the developer's machine, and team sync goes to a server you provision and operate. We do not host it, hold its credentials or have a way to read it.
No. Whether to build one is an open decision rather than a roadmap commitment, so there is nothing to sign up for yet. During an engagement we work inside your environment instead.
Not yet. Verification records do not cross the team-sync boundary, so receipts and gate evidence stay on the machine that produced them. Plan around that, or bring it up as a priority for the engagement.
Yes, explicitly — §7 of the agreement says the licence is included at no additional charge. The software is free to download and run anyway, for one developer or a whole team, with no seats and nothing metered, and cancelling the engagement does not end your right to keep running it. Consulting is the only thing we charge for.
An agent already used for real work, a repository with repeatable tests, a reasonable history of tasks to measure against, a person who owns the agent setup, and a way to observe whether a change worked. Without those, we would be measuring nothing.
The person who builds Excellent. That is the offer, and it is also the limit: there are only so many engagements one person can run well, so availability is finite and we will tell you if it is not there.
Any time, from the client portal or in writing. Billing stops at the end of the month already paid for. There is no termination fee, and the agreement states in terms that there is no minimum term.
Start with a call, not a contract
Tell us which AI agent your team uses, how many tasks it handles, and how you decide whether its work is good enough to merge. The intro call is free and there is nothing to sign to have it.