How a trial works

A trial gives you, for 30 days, one Talos cluster of your own with its own SPIFFE trust domain ({tenant}.reti-infra.com), its own secrets store and its own evidence trail. Nothing is shared with another customer. Trials are not yet open to the public; the status column says what runs today.

#	Step	What happens	Status
1	Sign in	At app.zeta-reticuli.ai (Backstage), through Keycloak: password plus a required passkey or security key. Later, your own single sign-on (SAML or OIDC). No self-registration: an administrator creates your user.	In development: realm and portal configuration written; the portal is not reachable from the internet.
2	Choose where and how governed	A form: cloud, region and an assurance profile, starting from a preset (Commercial; FedRAMP High-like; Air-gapped DoD-like). The form is rendered from the assurance profile schema, which rejects impossible combinations.	In development: the form exists; no customer cloud is built yet.
3	Pick agents	Tick occupations and their tasks in the agent catalog. Tasks reserved to licensed professionals produce drafts only; high-risk physical tasks are never offered.	Planned: the catalog data exists (15 occupations); selection is not in the form yet.
4	Your cluster is provisioned by GitOps	The form becomes a Git commit. Kratix turns it into an OpenTofu run (tofu-controller, reconciled by Flux) of the same code that builds our lab clusters, with SPIRE configured from your profile. An operator reviews each plan before it is applied.	In development: the request path is wired in our lab; recreating a cluster from code is Available in the lab only.
5	Your security officer reviews identities	Each agent has exactly one SPIFFE ID, spiffe://{tenant}.reti-infra.com/onet/{soc_code}, issued by SPIRE after node and workload attestation. Your security officer audits them in Tornjak, one instance per customer.	In development: in our lab one agent identity is issued and Tornjak runs; it has no sign-in yet.
6	Signed task records	Every executed task produces an in-toto statement signed with cosign: the outputs’ hashes, the occupation and task, the agent’s SPIFFE ID, the model, every source read and every human approval. You can verify it offline.	Available as a sample record; signing of real agent tasks is Planned.

At day 30 the trial converts to paid or is torn down by the same code that created it (Planned).

Task text in the catalog comes from the O*NET 31.0 Database by USDOL/ETA, used under CC BY 4.0; USDOL/ETA has not reviewed or endorsed this product.