Skip to content

FAQ

Reloqui is free to self-host — the complete platform, no feature gates. A fully-managed hosted / enterprise option (dedicated infrastructure, uptime SLA, backups & DR, priority support, white-glove SSO/SCIM setup) is available and scoped with you directly — email contact@reloqui.com. See reloqui.com/pricing.

Do I need to connect a real source to try it?

Section titled “Do I need to connect a real source to try it?”

No. The built-in Synthetic connector generates a realistic evidence chain, and the live demo needs no setup at all.

How is a release’s confidence calculated?

Section titled “How is a release’s confidence calculated?”

From weighted evidence components (tag anchor, linked PRs, artifact, deployment, no orphans, no force-push, green builds) minus deductions. Full detail in the Confidence guide.

What happens if I only connect GitHub (no CI/deploy)?

Section titled “What happens if I only connect GitHub (no CI/deploy)?”

Reloqui flags a coverage gap and does not penalize you for artifact/deployment evidence you have no way to produce. Your score reflects what’s genuinely available.

Yes — manually link or unlink evidence with a reason. Overrides survive recomputes.

No. Incidents are correlated to a release for context but never scored — they describe operations, not release content.

OIDC, with JIT provisioning. SAML is out of scope.

Yes — a versioned REST API with a live OpenAPI explorer. See the REST API reference.

How is my data isolated from other tenants?

Section titled “How is my data isolated from other tenants?”

Every row carries a tenant id and PostgreSQL row-level security enforces isolation as a second layer, failing closed if the tenant context is unset.

Yes — GET /api/v1/export/releases/{id} returns evidence, notes, approvals and the snapshot reference. See Prove what shipped.