[PLATFORM: TAXBOX]
Multi-tenant SaaS for sensitive tax documents on the SnapNgo system: host shell and domain MFEs over a gateway to auth, billing, and vault services — isolation as a product constraint, firm/client vaults, and a calm operator UI under deadline pressure.
Portfolio deliverables
Business narrative
Problem, approach, and outcome in plain language. Hooks decision-makers who care about value delivered.
Read case study ↓System Architecture
Technical depth: SnapNgo layers, service ownership, data flow, and failure modes. Built for people who review systems.
Open architecture →UX + visual language
Why the aesthetic pivot happened — palette psychology, hierarchy, and workflow — not “it looked cool.”
Open design →Platform extras · SaaS
Live View
Click through the real product surface — workspaces, vaults, and billing beat screenshots.
Pair the desktop. Mount the vault.
How TaxFort gets files in without the browser UI: inbound webhooks to a vault inbox, and a desktop client that pairs to a user then mounts org-scoped storage with STS.
Case study · business narrative
Problem
Tax and compliance teams drown in unstructured PDFs. Manual handling is slow, error-prone, and hard to audit. Multi-tenant products must isolate data hard — one wrong path across firm or client vaults is an incident, not a feature request.
Approach
- SnapNgo shape: host shell + Auth / Billing / Vault MFEs over a single API gateway.
- Ownership-clear services — auth (people + workspaces), billing (Stripe + entitlement), vault (presign / STS only if allowed).
- JuiceFS object prefixes
orgs/{organizationId}/…so tenancy is structural, not a filter. - Firm pool vs Client Pays vs personal vaults; seats and safe limits on the payer workspace.
- Inbox ingress (email / SMS / storage webhooks) into Valkey agent queue + Python worker.
- Desktop pairing: device → web approve → long-lived token → STS mount without emailing PDFs.
Production SaaS path for sensitive documents: firm and client vaults, paid capacity gates, and architecture that treats isolation as a first-class constraint — not a bolt-on filter.
What shipped
Gateway-fronted auth, billing, and vault; JuiceFS storage with org prefixes; dual Valkey (edge rate-limit vs agent jobs); inbound webhooks; desktop STS mount; firm-pool and Client Pays billing modes. White paper and design deliverables document the cut lines for review.