← Aman Kumar Limited · RegisterNotes to the accounts · FLYW
Flagship segment · product · 2026 · Building
Flywheel
An AI-native creative platform that turns a brand into on-brand campaign assets, then reviews, approves and ships them.
- Role
- Multi-tenancy, access control and client portal
- Contributor
- Outcome
- I built Organizations, RBAC and client-org sharing, with route-level authorization enforced by tests.
- Links
- Private codebase — described below
- Stack
- Next.js 16 · TypeScript · Supabase (RLS) · Claude · Gemini · SendGrid · Vercel
Problem
A creative platform serving agencies and their clients needs real tenancy. Teams, invites and roles, plus clients who can review without ever seeing another client.
What I built
- Organizations. Tables for organizations, members and invitations, a data migration and org-scoped row-level security, shipped with SendGrid invites and E2E tests.
- RBAC and client organizations. Roles, client-org sharing and access grants, plus an org-settings portal.
- Tenant isolation by design. Client users sit in separate client-org tables, so they can't leak across tenants. That decision is recorded as an ADR.
- Authorization as a test. Every API route has a permission gate tied to the org that owns the resource, and a test fails the build if a route is missing one.
- An embedded assistant. "Ask about this screen" and feedback summaries.
Result
57%Of a 1,300-commit team product, built by mesrc: git log: 746 of 1,303 commitsUnder the hood
Next.js (agency workspace + client portal)
proxy auth + revocation
route handlers with org-bound permission gates
Supabase Postgres (RLS) + Storage
Risk factors
- I'm one of several engineers: my scope is tenancy, access control and the client portal, not the generation pipeline.
This is a portfolio, not an offer of securities. No shares exist. Figures are about shipped work.