Account-centric infrastructure
Account-centric auth, identity, and email infrastructure.
Create OAuth clients, organize users into accounts with memberships, and ship transactional email with verified domains and observable events.
Client app
│
▼
Accountmaker
├─ OAuth + OIDC
├─ Accounts + Memberships
├─ Email + Domains
└─ Webhooks + Events
Most SaaS platforms rebuild the same identity infrastructure.
- Auth stops at login and tokens.
- Account logic is reimplemented per product.
- Email lives in a separate stack.
- Webhook failures are invisible.
- Ownership and permissions drift.
What Accountmaker changes
- One system for auth, accounts, email, and events.
- Explicit account memberships and roles.
- Domain verification and deliverability checks.
- Observable event delivery for email and webhooks.
Standards
OAuth 2.0 + OpenID Connect
Use standards-based flows with explicit scopes and predictable tokens.
Scope
Account-first permissions
Accounts and memberships are first-class primitives, not derived concepts.
Visibility
Observable events
Webhooks and email delivery events are first-class and auditable.
How it works
-
1. Configure OAuth clients
Define redirect URIs, scopes, and token lifetimes.
-
2. Create accounts and memberships
Model ownership, roles, and account-level permissions.
-
3. Configure email and webhooks
Verify domains and observe delivery events.
Proof
Account-scoped primitives
Every token, email identity, and webhook delivery is scoped to an account and membership role.
POST /accounts
POST /accounts/{account_id}/memberships
What Accountmaker does not do
- Does not replace application UI.
- Does not hide OAuth or token behavior.
- Does not send marketing campaigns.
Ready to integrate
Start with docs, then create a client and account in minutes.