Authentication UI
Custom sign-in, recovery, verification, MFA and passkey screens. The backend was not a finished user experience.
Better Auth handled core authentication. We built the surrounding identity platform ourselves: user interfaces, administration, provisioning, permissions and integrations.
Custom sign-in, recovery, verification, MFA and passkey screens. The backend was not a finished user experience.
A separate account.inds.space application for passwords, passkeys, MFA, devices, linked providers and connected apps.
Our own control plane for users, suspensions, roles, OAuth clients, sessions and security operations.
Custom user and group provisioning, mappings, organization boundaries and checks. The SCIM implementation file alone reached 365 lines.
Scoped permissions, role mappings, organization boundaries and checks that our applications actually enforced.
Key lifecycle, scopes, revocation and service/agent access beyond ordinary browser sessions.
Shared sessions for inds.space and OAuth/OIDC integrations for separate roots such as hackthe.world.
Workers Service Bindings, D1 integration and backend validation paths for applications inside and outside Cloudflare.
Connected-application consent, client administration and revocation interfaces.
Cloudflare Email Sending integration for verification, password recovery, MFA and security notifications.
Audit interfaces, security administration, deployment compatibility and maintenance of our own integration layer.
Counts cover our backend, frontends, gateway, migrations, tests and configuration. They exclude Better Auth itself, dependencies and generated bundles. The exact upstream fork delta is not included in these measurements.
We didn't just configure an auth library. We were maintaining an identity product.
This list describes work we built or customized for our implementation. It does not claim Better Auth lacked all the underlying capabilities; some are available as APIs or plugins.