Single binary
One static binary or one small container image. Start it with no config: you get an Issuer, a Client and two Users.

Single binary
One static binary or one small container image. Start it with no config: you get an Issuer, a Client and two Users.
No infrastructure
No database and no other service to run. It works offline, on a laptop and in CI.
Real login flow, real signed tokens
Your app goes through the real authorization code flow with PKCE. It gets real signed JWTs, with discovery and JWKS.
Test API
Mint tokens without a browser, with the claims you need. Inject failures to test how your app handles a provider outage.
Admin dashboard
See the Issuers, Users, Clients, keys and the Request log in the browser. Mint tokens and inject failures from the same page.
OpenID conformance in CI
Each change runs the OpenID Foundation conformance suite plans “Basic OP” and “Config OP” in CI.
Built in Rust
One static binary with low memory use and a fast start. For the measured numbers, see the Footprint page.





Start the server with Docker:
docker run --rm -p 9000:9000 ghcr.io/schmas/fauxidcOr download the binary from the GitHub releases,
or install it with cargo install fauxidc --locked.
With no config, fauxidc starts in Zero config mode: one Issuer default in Lenient mode,
one public Client test, and the Users alice and bob. In a second terminal:
# Discovery documentcurl -s http://localhost:9000/default/.well-known/openid-configuration# Tokens for alice, without a browsercurl -s http://localhost:9000/_mock/default/token -H 'content-type: application/json' -d '{"user": "alice"}'# Health checkcurl -s http://localhost:9000/_mock/healthPoint your app at the Issuer URL http://localhost:9000/default with the client id test.
Open http://localhost:9000/default/debugger and click “Run login flow” to see the login page.
The README has all the install options.
A coding agent can add fauxidc to an app project, write its config, mint tokens in tests and inject failures. The repo gives the agent two skills: skills/fauxidc (reference) and skills/fauxidc-setup (project setup). llms.txt lists the docs for agents that read it. Install the skills, then give your agent a prompt such as:
Our single-page app uses oidc-client-ts. Make it log in against a local fauxidc in Zero config:start it with "docker run --rm -p 9000:9000 ghcr.io/schmas/fauxidc".Use the authority http://localhost:9000/default, the public Client id "test", the code flow with PKCE (S256)and the scope "openid profile email". Put these values in .env.development, not in the code.Then open the app, log in as alice on the fauxidc login page and check that the app shows her email.Write an integration test for GET /api/orders of our API. Start fauxidc with examples/generic.toml(Issuer "generic" at http://localhost:9000/generic). Before the request, mint an access token with the Test API:POST http://localhost:9000/_mock/generic/token with the JSON body{"user": "alice", "audience": "https://api.example.test", "claims": {"roles": ["viewer"]}}.Send the access_token as a Bearer token and expect 200. Add a second test that mints a token with"expires_in": -60 and expects 401. Configure the API to trust the issuer http://localhost:9000/genericand to accept the access token header typ "at+jwt".For more prompts and the install steps, see Use fauxidc with an AI coding agent.
fauxidc is pre-alpha: the config and the library API can change before 1.0. Anyone who can reach a fauxidc server can mint tokens. Never trust a fauxidc Issuer in production. It is free software under the MIT or Apache-2.0 license.