Getting started

This is the complete first-run path. If you just want to click around, the live demo needs none of this. If you want your own data, follow along — it takes about ten minutes.

1. Create your workspace

Go to reloqui.com → Create your workspace and register with email + password. On first login Reloqui creates:

• your organization (the tenant — all your data is isolated to it),
• a default project (projects group your catalog, releases and policies),
• your org-admin membership.

You can create more projects any time under the org.

2. Model your catalog

Reloqui attributes evidence to services, so a minimal catalog comes first.

1. Products (optional) — group related services (e.g. “Storefront”). Set an owner team.
2. Services — the unit releases are scoped to. Set:
   • Repository URL — the single most important field; evidence is attributed by matching this.
   • Tier, lifecycle, owner team / email, and optional links (runbook, dashboard, ADR) and custom fields.
   • Kind — service, component (a library) or resource (a database, queue…).
3. Environments — e.g. development, staging, production; mark production requiresApproval if you like.
4. Dependency graph (optional) — declare typed edges between services (calls, depends_on, publishes_to) to unlock lineage and blast-radius views.

See the Catalog guide for details.

3. Connect a source

Under Integrations, add a connector. For a first run you have two easy paths:

• GitHub — paste a personal access token and configure the generated webhook in your repo. Merged PRs, tags and pushes start flowing.
• Synthetic — no credentials; click Generate demo evidence to fabricate a realistic PR/build/artifact/deployment chain for a service.

Reloqui also supports GitLab, Bitbucket, Azure DevOps, Linear, Jira, generic CI/CD, deployments, container registries, Terraform and incident tools — see the Integrations guide.

4. Create and reconcile a release

1. Releases → New release. Choose the service, a version (2.0.0), release type, and a git tag or release branch. Optionally set a baseline (the previous release or a timestamp) to bound the comparison window.
2. Open the release and click Reconcile. The engine:
   • resolves the release window,
   • collects evidence in that window,
   • attributes each item to the service (deterministically first, then heuristically),
   • classifies each item (included, included_heuristic, excluded, uncertain, orphaned),
   • detects backports and force-pushes,
   • computes a confidence score + tier,
   • evaluates policy and writes the result.
3. Read the Release 360: included evidence, confidence, exceptions, dependency changes, and notes.

Full detail in the Releases guide and Confidence guide.

5. Add governance (optional but recommended)

Under Policies, set a release gate: minimum confidence, required approvals, orphan/heuristic limits, and freeze windows. Then use the Approvals inbox to request and grant sign-off before publishing. See the Governance guide.

6. Publish

Click Publish on an approved, policy-passing release. Reloqui freezes a snapshot (release, evidence, gate results, approvals) and emits a release.published event that fans out to your notification channels.

What you get

At this point you have a living, evidence-backed record of what shipped, a confidence score you can defend, audience-specific notes, and a governance trail — all queryable via the UI, the REST API, or scoped service tokens.

Next

• Core concepts — understand the model you just used.
• Use cases — see how teams apply it.