Why Rust
Safety without a runtime tax.
- Memory safety without garbage-collection pauses
- Predictable latency at the authentication boundary
- One small binary with a narrow operational surface
- A mature cryptography and WebAuthn ecosystem
Open-source identity infrastructure
RustyAuth is a small, self-hosted Rust service for WebAuthn ceremonies, durable browser sessions and short-lived access tokens.
Pre-release · Apache-2.0 · Self-hosted
Built in Rust.
Built on SableDB.
Built for passkeys.
Deliberate technology choices
Each layer has one job: Rust protects the public boundary, SableDB keeps identity state compact and private, and typed contracts keep application integrations explicit.
Why Rust
Why SableDB
Why typed contracts
A deliberately small boundary
RustyAuth authenticates an identity and produces claims. Your application remains responsible for roles, permissions and ownership.
WebAuthn
Sessions
Tokens
Storage
Operations
Ownership
Running in minutes
Docker Compose starts RustyAuth on loopback and keeps SableDB private. The local volume survives container replacement.
Read the complete quickstart →$ git clone https://github.com/
rusty-auth/rustyauth.git
$ cd rustyauth
$ cp .env.example .env
$ docker compose up --build
✓ RustyAuth ready on :8081
✓ SableDB private and healthyHonest by default
RustyAuth is not yet approved as the sole identity system for a production service. The road to 1.0 is documented in public.

Own the boundary