Ship without the auth detour
Avoid assembling ceremonies, cookie policy, token signing and credential lifecycle code across the product.
For SaaS product teams
RustyAuth packages WebAuthn ceremonies, durable sessions, token issuance and key operations behind one narrow service boundary.
The operating reality
The team wants phishing-resistant sign-in now, but does not want authentication logic spread across the application or customer identity locked into a mandatory hosted provider. It starts with a local deployment, integrates through explicit HTTP and gRPC contracts, and keeps the option to run the same boundary in customer-controlled infrastructure later.
Avoid assembling ceremonies, cookie policy, token signing and credential lifecycle code across the product.
Give people a passkey-first path instead of making passwords the permanent centre of the account model.
Keep a route from a normal cloud deployment to customer cloud, on-premises or isolated installations.
What the core contributes
RustyAuth establishes who authenticated and issues narrow claims. Sector-specific systems keep every business decision.
Server-side, five-minute and single-use registration and authentication state.
HttpOnly browser sessions with idle and absolute expiry.
Short-lived ES256 access tokens with explicit issuer, audience and tenant claims.
Honest boundary
Regulated infrastructure earns trust through evidence. These boundaries remain explicit while RustyAuth is pre-release.
RustyAuth does not replace
Production profile requires
Begin with evidence
RustyAuth is pre-release. Start with a synthetic account and a controlled evaluation—not a sole production identity dependency.