Autopliance — getting started
EdSSA Autopliance is the hosted compliance product: a subscription that turns a live evidence chain into audit-ready reports. This page takes you from nothing to a generated report, and then to a paid plan, without a sales call. Budget fifteen minutes.
If you want the self-hosted protocol instead, start at the Quickstart — Autopliance is the product for teams who want the evidence without running the infrastructure.
1. Create an account
Go to app.edssa.io/login and enter your work email. The same form creates the account — there is nothing separate to sign up for, and no password exists to choose or lose: sign-in links are single-use and expire in fifteen minutes.
Every new account starts on a 14-day trial. No card is asked for at any point during it.
2. Get your trial fleet
The app’s first step, Test Fleet, provisions a hosted fleet for you: a real verification boundary with its own evidence chain, not a simulation. Two things to know:
- The seed is shown once. It is the fleet’s credential. The reveal page will not show it again, so store it like a password. (We keep the copy the verifier needs; the one on your screen is yours.)
- The fleet is yours for the trial plus a grace period — converting on the last day does not cost you the chain you accumulated.
3. Drive it
A chain with nothing on it proves nothing, so send some traffic:
- Have us drive it. The Run it step has a “drive it for me” button that sends realistic traffic from our side. This is the fastest route to a chain worth reporting on.
- Drive it yourself. Anything that can set an HTTP header can
participate. The SDK reference covers Go,
Node.js and Python; the credential travels as one header
(
X-EdSSA-Token) with no callback and no round trip to us.
Either way, verified traffic accumulates into anchors on your chain. Ten anchors is enough for a report worth showing to someone.
4. Generate a report
The Generate step renders a report against your own chain. Pick a framework — the catalog spans 34, including NIS2, SOC 2, ISO 27001, GDPR Art. 28, DORA, the EU AI Act, FedRAMP and the Finnish Katakri/PiTuKri/Julkri set — and a format: HTML, PDF, Markdown, JSON, or OSCAL for the GRC pipelines that ingest machine-readable assessment results.
Report provenance is stated on the document and never inflated: a report generated from your live chain says anchored because its verdict was computed by walking that chain. Example reports for every framework are downloadable without any account on edssa.io/why/compliance — they say so on every page.
5. Upgrade when it earns it
The in-app pricing page lists the tiers; the entry tier is Autopliance at €149/month, and upgrading is one Stripe checkout — VAT is computed there, and an EU business enters its VAT ID for reverse charge. Invoices, card changes, plan changes and cancellation all live in the billing portal, reachable from your account page.
Two commitments worth knowing before you pay:
- Evidence is never held hostage. If you stop paying, every report you generated stays downloadable and your chain is not deleted. The account goes read-only for new work; nothing you already have is withdrawn.
- Prices are list prices. What the pricing page shows is what checkout charges. If the two ever disagree, checkout refuses rather than charging the difference.
6. When something breaks — or should exist
The in-app Support page (account menu → Support) files bugs, ideas
and help asks; you get an acknowledgement by mail and a person replies
from support@edssa.io. Emailing that address directly works too.
What Autopliance is, and is not
It is cryptographic evidence: proof that specific parties were genuinely themselves, present at recorded moments, in order, with nothing replayed or quietly inserted. It is not an attestation, an audit opinion or a certification, and we are not an accredited certification body — what a report says is what a verifier computed. Where a framework needs an auditor’s opinion, an Autopliance report is the evidence you hand the auditor, not the opinion itself.