Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Sengol

Signed, offline-verifiable evidence for AI agents in regulated institutions.

Sengol evaluates every agent response against a ControlBook (a regulation expressed as configuration), gates deployments in CI, and writes each verdict as an HMAC-signed, hash-chained, Ed25519-countersigned record. An auditor verifies the exported evidence pack months later, on a laptop, without Sengol: the gate verdict and the audit record are the same signed object.

Sengol is self-hosted and single-tenant: one install is one tenant, inside your own network. Nothing leaves it.

Regulations arrive as configuration: OSFI E-23, FINTRAC, PIPEDA, SR 11-7, EU AI Act, GDPR, HIPAA, NIST AI RMF, ISO 42001 and more, 29 cataloged total in sengol/policies/catalog.yaml; a custom internal policy is one more entry.

Fifteen-minute quickstart

make keys          # Ed25519 evidence signing key into .env
make demo          # Postgres + API + Console, seeded with the reference agent
open http://localhost:8000
sengol gate --config sengol.yaml                      # verdict = signed record
sengol export --agent rag-advisor-001 --out pack.zip
# Not on PyPI yet (see docs/evidence/offline-verification.mdx); install it from source:
pip install "git+https://github.com/sengol-io/sengol-verify.git@fbbe46fd91a25b9e5b524df5b7f9b2d0829224f6"
sengol-verify pack.zip --trusted-key "<key_id>=<appliance-key.pem>"   # verify without Sengol
# <key_id> and the Ed25519 public key come from the operator, not from pack.zip. Without
# --trusted-key the countersignature step is UNVERIFIABLE and the exit code is 3
# (see docs/evidence/offline-verification.mdx).

The full walk-through, Entra ID and SCIM setup, and the operator references are in docs/ (quickstart.mdx first). Product scope is in PRODUCT.md; current state in STATUS.md.

Licence

Sengol 2.0 is proprietary software. A signed licence file (SENGOL_LICENSE_FILE) is verified offline at boot against the public keys in sengol/governance/trusted_keys/; the API and sengol worker run refuse to start without one. The sengol CLI is otherwise an API client and needs no local licence. There is no free tier. A lapsed licence never costs access to evidence: export and verification keep working, including with the separate sengol-verify. Fourteen-day trials and licences are issued at https://sengol.io/signup.html.

A build trusts only the anchors it ships. From the first release carrying the 2026-09-prod anchor, production licences verify; releases cut before it have an empty trusted_keys/MANIFEST.json and verify nothing. Check STATUS.md for the release you are installing.

The verifier, sengol-verify, is Apache-2.0 and has no dependency on this package.

Development

uv sync --all-extras, then uv run pytest --timeout=60. Tests marked postgres need a live database (docker compose up postgres). Invariants and review rules are in AGENTS.md; session rules in CLAUDE.md.

Metadata

Release files for sengol 2.0.1a9

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for sengol 2.0.1a9
File Size Uploaded Provenance
sengol-2.0.1a9.tar.gz 12.8 MB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for sengol 2.0.1a9
File Interpreter ABI Platform
sengol-2.0.1a9-py3-none-any.whl Python 3 none any Details

Total release size: 15.6 MB

Release files / sengol-2.0.1a9.tar.gz

Download URL sengol-2.0.1a9.tar.gz
Size 12.8 MB
Tags Source
SHA-256 checksum
How to use checksums
8fb968a3295eb7a7c2204c9e257cfccb9c9823bb8620ca6bdfcd69ddd6d04f05
BLAKE2b-256 checksum
How to use checksums
9ac7e20837d86760916becd9f28d421bcfb00edd4a2801befac768ec625b5096
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / sengol-2.0.1a9-py3-none-any.whl

Download URL sengol-2.0.1a9-py3-none-any.whl
Size 2.8 MB
Tags Python 3
SHA-256 checksum
How to use checksums
3f3c14058d7e01b88fdbdcdb3900a4026738145cb96ebdc2a162342dd9fd84b9
BLAKE2b-256 checksum
How to use checksums
803d73586426628fa3d47f690cf18239f6cc530a3790808fc8d0460e014b90ac
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for sengol 2.0.1a9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page