The irritation
A Delphi clone admin should not have to maintain a manual allowlist every time a user joins, pays, cancels, or needs access removed.
ProductBuildingIn development
Delphi Auth
An admin and authentication portal that lets Delphi clone owners manage, automate, and monetize access to their clones.
- Current state
- Building — In development
- Jack’s role
- Product architecture, Authentication design, Full-stack engineering
- Find it in the workshop
- Systems & Maps Lab · Clone access console
Built because…
The real build story.
What I built
I built an admin portal and authentication layer where Delphi clone owners can manage authorized users, grant or revoke access, automate provisioning, and connect access to paid membership or another entitlement source.
The hard part
The recurring challenge is keeping each clone's access current as users join, pay, cancel, or need access removed, while giving the clone admin one clear place to manage it.
Under the casing
Proof, not decoration.
Build evidence02 items
- Per-clone user administration, automated provisioning, revocation, and paid access
- An admin portal and authentication layer built specifically for Delphi clone owners
- Admin portal
- Authentication
- Access control
- Automated provisioning
- Paid entitlements
Scope of work
What I owned.
- Product architecture
- Authentication design
- Full-stack engineering
No victory-lap math
Outcome and lesson.
Where it landed
Delphi Auth gives Delphi clone admins one place to manage users and support automated, entitlement-based, or paid access to their clone.
What stayed
Authentication becomes a product when it removes the recurring administrative work around access—not just when it can display a login screen.
This project has a physical address.
In the playable workshop, Delphi Auth lives in the Systems & Maps Lab as a clone access console. You can inspect it without unlocking anything.