Quick start

Pick the scenario that matches where you are. Each one is self-contained and takes just a few minutes.

Scenario 1 · See it working in 2 minutes (no login)

The fastest way to understand Reloqui is to explore a workspace that’s already full of data.

1. Go to reloqui.com/demo. You’re dropped straight into the read-only Nimbus Commerce workspace — no sign-up.

2. You land on the Feature Tour — a guided catalog of every capability. Each card links to that feature running on real data.

3. Open Releases. You’ll see releases in every state: published, ready_with_exceptions, approval_suspended, rolled_back, superseded, draft.

4. Click a published release to open its Release 360: the evidence graph, the confidence score and tier, notable changes, and correlated incidents.

5. Open the Dependency graph and Operations to see the catalog, connector health, and the dead-letter queue.

Tip

Everything in the demo is read-only — write actions return a friendly “demo is read-only” message. Nothing you click can break anything.

---

Scenario 2 · Your first release truth

Create your own workspace, connect a source, and reconcile a real release end to end.

1. Create a workspace. Go to reloqui.com, choose Create your workspace, and register. Your org and a default project are created automatically, and you become the org admin.

2. Add a service. In Catalog → Services & Products, create a service and set its repository URL (e.g. https://github.com/acme/checkout-api). The repo URL is how Reloqui attributes evidence to this service.

3. Connect a source. In Integrations, add a GitHub connector (personal access token + the generated webhook). Or, to try the pipeline with zero credentials, add the built-in Synthetic connector and click Generate demo evidence.

4. Create a release. In Releases → New release, pick the service, set a version (e.g. 2.0.0) and git tag, and save.

5. Reconcile. Open the release and click Reconcile. The engine collects evidence in the release window, attributes it, classifies each item, and computes a confidence score.

6. Read the truth. You now have a Release 360: included PRs/issues/artifacts/deployments, the confidence score + tier, any exceptions, and generated notes for five audiences.

Note

No connector credentials handy? The Synthetic connector produces a realistic PR/build/artifact/deployment chain so you can see the whole engine work before wiring up real sources.

---

Scenario 3 · Put a release gate in place

Require a confidence threshold and a human approval before anything can publish.

1. Define a policy. In Delivery → Policies, set a release policy for your project: a minimum confidence (e.g. 0.7), require approval, and how many approvals (N-of-M).

2. Reconcile a release. With evidence attached, a release lands in ready or ready_with_exceptions. If confidence is below the floor or a gate fails, it becomes blocked_by_policy.

3. Request approval. On the release, click Request approval. It appears in the Approvals inbox for your reviewers. (You can’t approve your own request — self-approval is blocked.)

4. Approve & publish. A reviewer approves; you Publish. Reloqui writes a frozen snapshot of the release, its evidence, gate results and approval chain.

5. Watch the guardrails. If new evidence later collapses the confidence of an approved release (e.g. a force-push), Reloqui auto-moves it to approval_suspended so it can’t ship silently.

Where to go next

• Getting started — the full first-run walkthrough with more detail.
• Core concepts — the vocabulary behind evidence, reconciliation and confidence.
• Guides — how to use each feature, step by step.