Everything works on the free plan. What you outgrow is volume and history — which is also what makes the evidence worth anything.
No card to start. The trial is fourteen days and asks for nothing up front, because you cannot know whether we can see your traffic until you have run some through us.
| Free | Team | Self-hosted | |
|---|---|---|---|
| Price | Nothing | $499 a month | Talk to us |
| Governed actions | 1,000 a month | Unmetered | Unmetered |
| History | 7 days | 90 days | However long you keep it |
| Detection, both tiers | Yes | Yes | Yes |
| Signed receipts, verifiable offline | Yes | Yes | Yes |
| Compliance pack, ISO 42001 and NIST mapping | Yes | Yes | Yes |
| Team, roles, single sign-on | Yes | Yes | Yes |
| Where your data sits | Our cloud | Our cloud | Yours |
| Who holds the signing key | We do | We do | You do |
Nothing is switched off on the free plan. You can generate a compliance pack, add your team, and verify a receipt on day one — because a plan that hides the thing being sold cannot demonstrate it.
Seven days is enough to see the product work. It is not enough to answer a question about last quarter, and that question is the one that costs money to be unable to answer.
A receipt you exported is yours for good — we hold its digest, so a receipt you kept can always be checked. What the plan governs is how long we keep the summary you did not export.
Not a fallback. Your cloud, your signing key, and nothing reaching us at all — which removes every data-transfer question from an assessment before it is asked.
It also changes what a receipt proves. On our cloud we derive your signing key, so a receipt shows that nobody has altered the record; self-hosted, we could not produce one even if asked. If your evidence has to survive somebody doubting us, this is the answer.
The governing service is a static binary with no shell and no libc, and its root module has no third-party dependencies at all. The analyzer ships its models inside the image and makes no outbound calls, so the whole thing runs in an air-gapped network.
Stated here rather than discovered during an assessment:
One request or one response that passed through and was inspected. A chat exchange routed through the gateway is two. Traffic another system reported to us counts the same as traffic we watched.
Actions are refused rather than passed through unchecked. Letting them past would mean traffic left ungoverned while a dashboard still said everything was fine, which is worse than an error.
No, and they need no account. lyntway-verify checks a receipt
offline forever, and lyntway-mcp governs your agent's tools on
your own machine. Both are Apache-2.0 —
read the source.
Ask us. Both are ordinary requests and neither is a problem.
Start on the free plan. Point one base URL at us, run the readiness check, and see a receipt you can verify without an account. Create an account or read how it works first.
Documentation · Terms · Privacy · Data processing · Verify a receipt