Access your managed tenant
The optional `relixq` CLI extends managed tenant workflows with source scanning and CI gates. It connects to your tenant when you invoke a platform command. See Enterprise CLI.
What Enterprise adds
Every scan surface speaks the same finding contract, and everything above it — scoring, exposure assessment, governance, egress — is built for an estate rather than a single repository.
Widen the lens
Cloud KMS and certificate posture, runtime telemetry correlation, full SBOM ingest, and fleet-scale TLS probing with ownership attribution.
Make it measurable
The banded RelixQ Score at four scope levels, with ranked drivers, coverage context, and role-specific dashboards.
Make it defensible
Quantum exposure assessment, the crypto asset inventory and CycloneDX CBOM, TTL-bounded exceptions, and a verifiable audit chain.
Make it operational
Organizations and SSO, release gates with policy decisions, and SIEM, ticketing and alerting egress.
Sign in
Open your tenant and go to /login. The root URL redirects there when you are signed out, and to your organization home once you are signed in.
How you sign in depends on how your organization is configured — local email and password, OIDC redirect, or SAML for organizations that enforce single sign-on. If your organization enforces SSO, password sign-in is refused and you are routed to your identity provider. Full details, including MFA and SCIM provisioning, are in Accounts and organizations.
If you sign in and belong to no organization yet, you are routed to onboarding, where you can create one or paste an invitation link.
Create a project and connect a source
A project is the unit RelixQ scans. Create one at /orgs/<slug>/projects/new and pick a source:
- GitHub repository
- A repository URL, an optional branch, and for private repositories an access token. Public repositories need no credentials.
- Empty
- Start with no source and attach one later, or populate the project from CLI submissions and CI.
Projects carry a name, a slug unique within the organization, and an optional description. Beneath a project you can model an application and service hierarchy, which is what turns a findings list into work routed to the owning team.
Run your first scan
- 01
Trigger the run
Press Run scan on the project Scans page. The run appears immediately at the top of the list as running.
- 02
Watch it live
Open the run to see the status panel stream progress over Server-Sent Events — a progress bar, a four-stage pipeline, and completion updating in place without a refresh.
- 03
Read the findings
When the run succeeds, the Findings page, the dashboards, and the RelixQ Score all recompute from the new results.
Three other ways to produce a scan: the CLI (relixq scan locally then relixq submit, or relixq remote-scan to run it server-side), a per-project cron schedule, and CI. Each run records its trigger source — manual, pr, scheduled, cli, or api — so you always know where it came from.
The surfaces, and what each is for
| Surface | Route | What it is for |
|---|---|---|
| Org home | /orgs/<org> | Cross-project posture: a rollup strip and one score-ringed card per project. |
| Engineering dashboard | .../dashboard/engineering | The remediation work queue: score drivers, owner gaps, and findings sliced by service, algorithm, and language. |
| Executive dashboard | .../dashboard/executive | A trend line and a shareable snapshot for leadership. |
| Security dashboard | .../dashboard/security | Enforcement, accepted risk, and external exposure. |
| Findings | .../findings | A filter rail and a paginated table; expand a row for "why this was flagged" without leaving the list. |
| Inventory | .../inventory | The deduped crypto asset inventory and the CBOM download. |
| Quantum exposure | .../quantum | QAST: the HNDL register, attack paths, data assets, probing, remediation, report, retest, and the PQC lab. |
| Reports | .../reports | Asynchronous exports in PDF, CSV, JSON, Markdown, and SARIF. |
Your tenant starts empty — on purpose
So a brand-new tenant shows empty dashboards, an empty inventory, and no score. That is correct, not broken. If a surface is unexpectedly empty, ask three questions in order: has a scan run? is the connector for that signal configured? does that signal apply to this project? Troubleshooting walks through the common cases.
Where to go next
Scans and findings
The scan lifecycle, the filter rail, the triage loop, saved views, and report exports.
The RelixQ Score
What the 0–100 number means and deliberately does not mean, and the three dashboards built around it.
QAST
Which of your data flows could be harvested today and decrypted later — and what to do about them.
Release gates
Stop new crypto debt at the pull request with policy-backed gate decisions.
Related pages
How RelixQ Enterprise works
What gets scanned, how your estate is organized into scopes, how the managed service processes evidence, and what happens when a signal is missing.
Scans, findings and reports
The day-to-day working loop: run a scan, read the live progress stream, filter and triage findings, save views, and export evidence.
Accounts, organizations and administration
The account lifecycle, authentication methods and their honest UI-versus-API status, organizations and the switcher, invitations, members and roles, and project administration.