The 14-day pilot, in plain language.
This page explains what you're agreeing to when you request a Sengol pilot. It is not a substitute for the licence agreement that comes with your licence, which governs if the two ever disagree.
Two paths, one pilot
A Sengol pilot is 14 days of full capability — nothing is held back, gated, or watermarked. You choose how you run it, and we arrange it with you after your request:
- Hosted demo. We provision a private Sengol instance on our AWS account for you, pre-loaded with a reference agent and sample evidence.
- Self-hosted licence. You install Sengol inside your own network — Docker Compose, Helm, Terraform, or
pip install sengol— under a 14-day licence file. No licence check or telemetry leaves your network under this path.
Both paths start from the same request. Picking one is not a commitment to the other, and you can ask us to switch you before day 14.
Who can request one
- Work email only. Pilots are offered against a work email address at the company evaluating Sengol. Personal addresses (Gmail, Outlook, Yahoo, Hotmail, iCloud, Proton and similar) are refused by the request form.
- One pilot per domain. A given company email domain gets one pilot, regardless of which path is chosen or who on the team requests it. If your organization needs another, email trial@sengol.io.
What data a hosted pilot holds
Hosted pilot instances are for evaluation, not production traffic. They are provisioned with a reference agent and synthetic or non-production data only — do not point a hosted pilot at real customer data, real accounts, or anything you would need to retain past the pilot. A hosted instance is destroyed at day 14, along with everything on it. If there is evidence you want to keep — an exported pack, a report, a screenshot — export it before day 14.
Self-hosted pilots are different: the instance runs on your infrastructure from the first request, and nothing about the 14-day licence changes where your data lives or who can see it.
What expiry does — and does not — do
When a trial licence (or, later, an annual licence) reaches its expiry date, nothing changes for a process that is already running. The next start comes up in evidence-only mode — after a 14-day grace period for an annual licence, immediately for a trial licence — which refuses new evidence ingest, new evaluation and governance writes. That's it.
Expiry does not take away access to evidence you already have:
- Reads keep working through the API and CLI — you can still list and fetch records already written. The Console is not served in this mode.
- Export keeps working — you can still pull an evidence pack for a period that already ran.
sengol-verifykeeps verifying — it's a separate open-source tool with no dependency on Sengol and no licence check of its own, so a lapsed Sengol licence has no effect on whether your evidence still verifies.
A lapsed licence is a reason to renew, not a reason evidence you've already signed becomes unreadable.
Licences verify offline
A Sengol licence file is checked locally, against a public key, once when the process starts; the licence status the Console and CLI show is re-read at most every 60 seconds and never stops a running process. There is no phone-home: Sengol does not call home to validate a licence, and a fully air-gapped self-hosted install works the same way a networked one does.
After the pilot
Sengol is proprietary software from version 2.0 onward — there is no free tier. To keep using Sengol past day 14, you convert to an annual licence. Talk to us before or after your pilot ends:
Questions
Anything on this page unclear, or a situation it doesn't cover — email hello@sengol.io and a person will answer.