'/%3e%3cpath%20d='M210%2042L210%20336C138%20292%2096%20238%2096%20176V68L210%2042Z'%20fill='%23000'%20opacity='0.12'/%3e%3ccircle%20cx='210'%20cy='142'%20r='36.4'%20fill='%23000'/%3e%3cpath%20d='M194.4%20171.9H225.6L239.9%20257.7H182.7Z'%20fill='%23000'/%3e%3c/svg%3e)
www.sigid.org you are hereLanding, documentation, pricing, and entry points. No credentials, no sessions.
Architecture
Four surfaces, four trust boundaries
Public web, global identity, tenant dashboard, and hosted auth each carry one responsibility and one session boundary. SigID keeps protocol-critical flows on a Rust-owned origin.
Surfaces
Each surface carries one authority boundary
identity.sigid.org Your accountProfile, sessions, passkeys, MFA, memberships, and data sharing controls.
dashboard.sigid.org Tenant operationsApplications, domains, branding, billing, audit, and operator workflows.
auth.sigid.org OAuth flowsAuthorize, consent, callbacks, passkey ceremonies, and token issuance. Rust-owned.
Platform
Enterprise identity, not a login widget
Password, passkey, magic link, social login, enterprise SSO, TOTP, SMS, and SIWE on a hardened first-party origin you never have to build.
AI agents as first-class principals with challenge–response auth, canonical IDP-minted identity, and standard token issuance.
FIDO2 resident credentials with automatic syncing, TOTP enrollment, SMS fallback, and backup codes.
Users choose what each application can see. Scope upgrades require re-consent – silently widening access is not a feature.
Store third-party OAuth tokens, API keys, and SSH keys once. Agents use them through the egress data plane – the secret is injected at the boundary, never enters agent context, and every use is audited. The egress is open source: run it in your own cloud and your workload traffic never reaches SigID.
Per-tenant OIDC federation with dynamic credentials, domain-based routing, and social provider support.
Applications, domains, branding, billing, audit, webhooks, and policy management in one control plane.