ReadyComply
Menu

Solutions · Portfolio companies

One identity graph. Separate compliance records.

You sign in to ReadyComply. The workspace binds to your organization. Jockbroker’s evidence is not InsightHire’s. Shared templates do not mean shared proof.

ReadyComply controls table with Trust Services Criteria codes, owners, and status pills

Tenancy

The organization is the wall.

Authio already knows users, orgs, and roles. ReadyComply does not invent a second login. It receives a project-bound session and stores the register behind that org. Cross-portfolio rollups are an explicit product decision — not a default view.

ReadyComply overview: control status, evidence count, and open tasks for Authio LLC

First tenants

The companies this has to work on.

Authio

Identity platform. First dogfood: systems, starter controls, evidence, policies, and the trail we will later collect automatically.

Jockbroker

Own system boundary, own evidence, same control families where they apply. Inheritance does not erase exceptions.

InsightHire

A different product, a different cloud story. The register is still one org in Authio and one tenant in ReadyComply.

MentorHQ

Same practice, separate RLS. Portfolio visibility is explicit. Impersonation cannot open evidence.

What does not leak

Impersonation cannot open evidence.

Support sessions that impersonate a user are blocked from compliance artifacts. A portfolio operator does not get a god mode over another company’s register unless that access is a real, audited role.

ReadyComply evidence library with hashed artifacts linked to controls

Open the org you actually belong to.

Sign in. ReadyComply follows the organization. Do not mix evidence across products.

Sign in