IND's Space / Engineering
ARCHIVED · 2026
Engineering retrospective · November 15, 2026

What we built
around Better Auth.

Better Auth handled core authentication. We built the surrounding identity platform ourselves: user interfaces, administration, provisioning, permissions and integrations.

Stack  Better Auth + Cloudflare Workers + D1Status  Retired November 7, 2026

Our custom implementation

11
01

Authentication UI

Custom sign-in, recovery, verification, MFA and passkey screens. The backend was not a finished user experience.

02

Account management portal

A separate account.inds.space application for passwords, passkeys, MFA, devices, linked providers and connected apps.

03

Administration dashboard

Our own control plane for users, suspensions, roles, OAuth clients, sessions and security operations.

04

SCIM provisioning

Custom user and group provisioning, mappings, organization boundaries and checks. The SCIM implementation file alone reached 365 lines.

05

Application-level RBAC

Scoped permissions, role mappings, organization boundaries and checks that our applications actually enforced.

06

API key and machine access

Key lifecycle, scopes, revocation and service/agent access beyond ordinary browser sessions.

07

Cross-domain sign-on integrations

Shared sessions for inds.space and OAuth/OIDC integrations for separate roots such as hackthe.world.

08

Cloudflare-native auth layer

Workers Service Bindings, D1 integration and backend validation paths for applications inside and outside Cloudflare.

09

OAuth consent management

Connected-application consent, client administration and revocation interfaces.

10

Security emails

Cloudflare Email Sending integration for verification, password recovery, MFA and security notifications.

11

Audit and operational controls

Audit interfaces, security administration, deployment compatibility and maintenance of our own integration layer.

The size of it

Archived source audit
8,395Physical lines
7,679Nonblank lines
65Source / test / config files

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.