PlatformBuilt
One platform. Every tenant its own.
Aegis is a complete know-your-customer platform run for many organisations at once. Each tenant chooses its products, builds its flows, picks its providers, verifies people on its own domain and reviews them in its own console — and can rely on another tenant’s verification, claim by claim, when the person agrees.
Tenancy
Multi-tenant from the first line.
Every record, event and permission carries its tenant. One tenant never reads another’s people, runs or configuration; the only way across is a trust agreement both sides opt into.
- Tenants and organisations
- A tenant is an organisation with its own people, teams and settings, onboarded by the platform team and approved by a second person.
- Built
- Relationship-based access
- Who may do what is a graph of relationships — tenant, team, role, resource — checked on every request, so access follows the organisation’s real structure.
- Built
- Roles that mean something
- Tenant administrators configure and reviewers adjudicate; the platform team works as trust and safety, operations and finance, or administration. Onboarding, platform roles and credential revocation need a second approver.
- Built
- Branches and groups
- A group with many branches is one tenant with branches, each with its own people and permissions.
- In progress
Configuration
Products, flows and providers, chosen per tenant.
The platform publishes a catalogue of verification products. A tenant switches on what it needs, arranges the steps into flows, and chooses which provider answers each one.
- A catalogue of products
- Identity, documents, biometrics, screening, registries, signing and credentials, each a product a tenant can enable.
- Built
- Flows with versions
- A flow is an ordered set of steps with its rules. Every change makes a new version; a run always finishes on the version it started with.
- Built
- Two layers of configuration
- The platform layer says what is allowed; the tenant layer chooses within it. Both must agree before a provider or method is used.
- Built
- Provider choice and fallback
- Each step names its providers in order. If one fails, the next answers; if all fail, the tenant’s policy decides what happens.
- Built
- Digital identity methods
- Whether a person may prove themselves with a national wallet or an Aegis credential is a method policy, set on both layers.
- Built
Where people verify
The tenant’s own domain, the tenant’s own brand.
People verify on a hosted journey under the tenant’s name, inside the tenant’s own app, or through an invitation — never on a page that looks like someone else’s.
- Hosted verification
- A white-label journey served on the tenant’s own domain, with the certificate and routing managed for them.
- Built
- Embeddable journey
- The same steps as a self-contained package a tenant places in its own site or app.
- In progress
- Invitations
- Start a run by email or text message; the person continues on any device.
- Built
- The API
- Create runs, receive signed decisions and manage configuration from your own systems.
- In progress
Consoles
A console for each tenant, and one for the platform.
- Tenant console
- Runs and their evidence, review queues, flows, products and providers, team and roles, domains and branding — one view per entity, not a wall of cards.
- Built
- Platform console
- Tenants and their onboarding, the provider registry, the catalogue, prices, approvals, privacy requests and the audit trail.
- Built
- Review and adjudication
- Cases a flow cannot decide go to a reviewer with every step’s evidence, who approves, declines or asks the person to redo a single step.
- Built
Operations
Metered, notified, accounted for.
- Usage and billing
- Every billable step is metered from the event that recorded it, against price schedules that go through approval, with credits, discounts and statements.
- Built
- Two people for money
- Rating at period boundaries, and a second approver on every movement of money.
- In progress
- Notifications
- Email and text messages, an in-console inbox, announcements, preferences and webhooks, sent on the platform’s events.
- Built
- An audit trail
- Every action by every person and service is recorded at its source, with retention, legal holds and exports.
- Built
- Verifiable by anyone
- Signed checkpoints and inclusion proofs a standalone verifier checks without trusting Aegis. The verifier is built.
- In progress
- Privacy operations
- Export, erasure and objection requests are worked as typed requests across the services that hold the person’s data, with deadlines on exports.
- Built
Build on identity that is proven, not assumed.
Aegis is built by Protoworks and offered to partners on request. Tell us what you need to verify, issue or accept, and we will show you the platform running.