Symbol Docs
Features

Sentinel Self-hosted

Run Sentinel's AI review of protected changes on your own infrastructure, with keys, rules and AI provider account that stay with your organization.

Sentinel Self-hosted is a version of Sentinel that your organization runs itself, as its external approval service. It reviews every change held in your organization's Protected Types with the same two checks, a safety check and a check against your own rules, then approves or rejects it through Symbol's public Approvals API. A change it cannot decide safely waits for a person in your organization's own review queue.

It is one container with a small volume for its journal. It listens on no port: it only makes outgoing requests, to your Symbol server and to your AI provider.

When to choose it

Sentinel, run by SymbolSentinel Self-hosted
Who holds the keys that approveSymbolYour organization
If an owner's account is taken overThe attacker can approve a held change, and can change Sentinel after the 24 hour waitThe attacker cannot release a change: they cannot sign as your service
Where your rules are keptIn SymbolOnly on your side. Symbol never sees them
Who pays for the checksThe change author's AI credits in the organizationYour own Anthropic account. No Symbol AI credits
End-to-end encrypted changesAlways go to a personCan be reviewed, if you choose to mount your organization key
What you runNothingOne container, its keys and a volume

Choose Sentinel Self-hosted when your policy requires that the keys able to approve a change, your review rules or your AI traffic stay under your organization's control, or when you want encrypted changes reviewed automatically. It is more work: you run and update the container, keep its keys safe, and pay your AI provider directly. Choose Sentinel when you would rather run nothing.

Its protection against a compromised owner account starts after enrollment. Enrollment itself relies on the owner being trustworthy at the moment they do it, as for any external approval service.

What stays where

ItemWhere it livesWhat Symbol receives
Management keyYour operator's machine, used only for setup and changesIts public key
Recovery keyOffline, after enrollmentIts public key
Worker keyMounted into the running containerIts public key
Review rulesA file you mountAn opaque random id and a number for each version you activate, never the rules or a digest of them
AI provider keyMounted into the container, sent only to AnthropicNothing
Organization decryption key (optional)Mounted into the containerNothing
The review journal and queueThe container's volumeEach decision and its reference

Every request the service makes is signed with one of its private keys, which never leave your side. A Symbol account, however privileged, cannot produce a signature, so it cannot approve on your service's behalf.

Deploying it

Sentinel Self-hosted's source code, its operator guide and its container image are published openly, under the Apache License 2.0, when it is released. Once they are, you can build the image from the source or pull the published image, then follow the guide that ships with it. The guide covers the configuration file, the key files and how to run every command below with the image.

You need:

  • a machine that can reach your Symbol server and api.anthropic.com over HTTPS, with Docker or another container runtime;
  • an Anthropic API key for your organization's own account;
  • the organization's owner, for the one-time enrollment;
  • your review rules.

Enrolling

  1. On the operator's machine, generate the management and recovery keys with sentinel-selfhosted keygen. Each command writes a private key file that only its owner can read, and prints the public key.
  2. The organization's owner opens Settings, Governance, Approval service, chooses Signed keys, pastes the two public keys and chooses Start enrollment. Paste only the public key each command printed. A secret made for the Secret hashes option has the same 43-character shape but is not a public key, and a key file's contents are private: never paste either.
  3. The panel shows the enrollment id, the origin this deployment checks signatures against (set it as symbol_origin in your configuration) and, for each key, a credential id, a one-time challenge and the exact sentinel-selfhosted enroll possession command to run. If the deployment has no such origin configured, the Signed keys option is not offered. Run both where the keys are kept. Keep both credential ids: the configuration names them.
  4. When both keys have proved possession, the owner chooses Turn on the approval service.

From then on, nobody with a Symbol account can approve or reject a protected change in your organization, including the owner. Enrollment cannot be undone from a Symbol account. See External approvals for everything that changes.

Keep the recovery key offline once enrollment is on. It is only needed to replace a lost or compromised management key.

The worker and its key

The container that reviews changes never holds the management or recovery key. Instead:

  1. The management key registers an installation, the identity of this reviewer and its rules: sentinel-selfhosted installation create.
  2. The management key issues the worker its own key with sentinel-selfhosted child issue. The worker's private key is generated on your machine and only its public key is sent. It can only review and decide, it is bound to this installation, it expires after 30 days unless you choose otherwise, and it can be limited to some Types.
  3. Reissue the worker key before it expires, then revoke the old one.

Run management commands from the operator's machine, mounting the management key only for that run. The long-running worker gets only the worker key, the provider key and, if you enable decryption, the organization key.

Importing your rules

Sentinel Self-hosted reads the file that Export rules downloads from Sentinel's settings (see Exporting your rules) unchanged, with its line breaks and any characters kept as written. You can also write the file yourself in the same shape:

{"schemaVersion":1,"rules":"Reject anything naming a client without approval.\n\nNo prices in published copy."}

Anything else, such as another schemaVersion, extra keys or rules longer than 8000 characters, is refused before any review runs.

sentinel-selfhosted rules validate checks the file. sentinel-selfhosted rules activate keeps an exact copy of it in the journal and moves the installation to a new rules version. Only the version's number and its random id reach Symbol. Symbol refuses a decision that names any other version, so a verdict reached under old rules cannot land after new rules took effect. The worker pauses while the mounted file differs from the activated version: to change rules, edit the file and activate it again.

Provider billing

Each reviewed change costs two Anthropic Messages calls, one per check, with the model claude-haiku-4-5-20251001. They are billed to the Anthropic account whose key you mount. Symbol charges no AI credits for these reviews and never sees the provider key. Set spending limits in your Anthropic console. When the provider refuses or your limit is reached, changes wait for a person.

What the provider sees

Each call carries the review instructions and the whole change, every item before and after, as data marked as untrusted. Only the rules check receives your rules. The AI is offered no tools. Text in a change that tells a reviewer what to do is treated as a safety problem, never followed.

End-to-end encrypted changes are not readable by default, so they wait for a person. If you turn on local decryption by mounting your organization's encryption key, the container decrypts encrypted changes itself and sends their plaintext to your AI provider for both checks. Turn it on only if that is acceptable to your organization. The key never leaves the container. A missing or wrong key, or an item that fails to decrypt, leaves the change pending, and nothing about it is sent to the provider.

Failures leave changes pending

Sentinel Self-hosted never approves when it cannot decide. A provider error or timeout, an unclear or malformed answer, a change too large for its limits, a file attachment, a page or item it could not read, or an encrypted item it could not decrypt all leave the change pending. Only two clear passes approve. Two completed checks with a definite problem reject, with a fixed reason the author can see that never quotes your rules or the content.

Every decision is written to the journal before it is sent, so a container that stops at any point picks up where it left off and decides a change once. If the change, its authority or your rules moved in the meantime, the old verdict is discarded and the change is checked again.

If the service is not running, changes wait. Symbol never falls back to member approval.

The human review queue

Anything the reviewer could not settle is kept in its journal with a reason. On the machine that holds the journal:

  • sentinel-selfhosted review list lists what is waiting.
  • sentinel-selfhosted review inspect shows a whole change, decrypted locally if you enabled decryption.
  • sentinel-selfhosted review approve and review reject decide the exact revision you inspected. The change is read again first, so one that moved since is refused rather than decided. While the worker is reviewing the same change, or the change already has a decision waiting to be resent, your decision is refused rather than raced: try again in a moment, or settle the waiting one first.
  • sentinel-selfhosted review requeue lets the worker try again, for example after a provider outage.
  • sentinel-selfhosted review retry resends your decision exactly as you made it, if its answer was lost. Until then the change stays with you and is never reviewed automatically.

A change whose author no longer qualifies under your organization's security policies is listed apart, since no content decision can release it.

Anyone who can run these commands with a key that can decide can decide changes, so protect the machine and the volume with your own access controls.

Disabling and recovery

  • Replacing a key. The management key can replace itself. If it is lost or compromised, the recovery key replaces it. Every replacement proves possession of the new key, and when it completes the old key and every worker key stop working at once.
  • Disabling. sentinel-selfhosted authority disable, signed by the management key, turns external approvals off. Changes waiting at that moment are cancelled, not published, and owners and Admins decide new ones. This cannot be undone: the organization cannot enroll a service again.
  • Losing both root keys. If both the management and recovery keys are lost, Symbol cannot give you control back. See Recovery and custody.
  • Restoring a backup. Back up the journal volume. Restoring an older copy is safe: the reviewer compares it with Symbol and pauses rather than act on rules it did not activate.

The open source code

The reviewer's source code, its container image and its operator guide are published openly, under the Apache License 2.0, when Sentinel Self-hosted is released, so you can read exactly what runs, build it yourself, and change it. The source includes the conformance vectors for the signing format, as test/fixtures/approval-signature-v1.vectors.json. The signing format it uses is in the preview API reference, so you can also write your own service against the same API.

On this page