From sign-up to your first export

Veritio Cloud is the managed way to run the evidence layer — hosted ingest, storage in your region, a hosted MCP, and signed export bundles. This walkthrough takes you from an empty account to a verifiable export.

The open-source SDK runs fully offline with no account — see Examples. Veritio produces compliance evidence; it does not make you compliant and is not legal advice.

Open the console →

Step 01

Sign up

Register at console.getveritio.com/register with your email. Veritio Cloud sends a verification link — confirm it, then sign in to reach the console.

Step 02

Create your organization & region

On first sign-in you name your organization and choose its data region — EU, US, or APAC. This choice sets where your evidence lives.

What the region means, honestly. Your database and evidence objects are stored in the region you pick, and the EU object store carries a hard EU-jurisdiction guarantee. Application compute is currently EU-located regardless of the storage region. The region is locked at creation — choose deliberately, because you cannot move an organization later.

Step 03

Create a project

Inside your organization, create a project. Each project is an isolated tenant boundary: its project id becomes the scope.tenantId on every event and edge you record, and evidence never crosses between projects.

Step 04

Mint scoped API keys

Veritio keys are scoped to a single authority, so a key can do exactly one job and nothing more. Mint the keys your integration needs:

ingest: Write events and edges to the hosted ingest. Server-side only.
read: Read your evidence back — graph, changes, and timelines.
export: Request signed export bundles.
admin: Manage the project and its keys.
mcp: Let a hosted MCP client query your evidence.

Treat keys like passwords. Keep them in server environment variables or a secret manager, never in browser code or version control, and revoke any key you no longer need.

Step 05

Send your first events

Build canonical audit events and evidence edges with the open-source @veritio/core SDK — the same code shown on the Examples page — then hand them to a server-side dispatcher that drains a batch to the hosted ingest. Point the dispatcher at your project with three environment variables:

server environmentbash

# Set on your server only — never ship an ingest key to the browser.
export VERITIO_CLOUD_BASE_URL=https://console.getveritio.com
export VERITIO_CLOUD_PROJECT_ID=<your project id>   # becomes scope.tenantId
export VERITIO_CLOUD_INGEST_TOKEN=vrt_...            # an "ingest" scoped key

The dispatcher POSTs each batch as one { events, edges } payload to /api/ingest with the ingest key as a bearer token. Delivery is server-to-server — the hosted ingest sets no CORS headers, so the key stays on your backend:

terminalbash

curl -X POST https://console.getveritio.com/api/ingest \
  -H "authorization: Bearer $VERITIO_CLOUD_INGEST_TOKEN" \
  -H "content-type: application/json" \
  -d '{ "events": [ /* canonical audit records */ ], "edges": [] }'

For a complete, runnable delivery harness — building the records, draining an outbox, and posting to a deployed project — see the cloud-full-governance-poc example in the OSS repo.

Step 06

Invite your team

Owners and admins invite teammates by email. Each invite carries a role — admin (manage the org, projects, and keys), member (do the work), or viewer (read-only). Invite links expire after 7 days; re-send if one lapses.

Step 07

Request an export

When you need portable proof, open Evidence → Exports and request a bundle. Veritio assembles a signed vevb-1 export bundle, stores it in your region, and makes it downloadable once ready.

The bundle verifies offline with the open-source verifier — no account, no network, no trust in the host required. Monthly export volume depends on your plan.