02Craft
Build the plane, not just the feature.
I design and ship multi-tenant platforms and high-concurrency backends — the seams that keep product moving: tenancy, observability, and reliability under load.
Infra · Platform · Multi-tenant
$“Not a front-end enthusiast, but acing the back-end game!.”
03Work
Cases.
Problem → system → outcome. Text first — no dashboards.
- 01
Konfersi Lab Platform
Multi-tenant control plane so teams onboard without forking the stack.
- Problem
- One product, many tenants — shared runtime without leaking state.
- System
- Gateway → control plane → isolated worker pools.
- Outcome
- Ship per-tenant safely; quotas and observability as first-class surfaces.
- 02
Fintech backend
Predictable under peak — backpressure designed in, not bolted on.
- Problem
- Burst traffic, idempotency edges, queues that fail quietly.
- System
- Explicit queues, retry budgets, typed failure contracts.
- Outcome
- Graceful degrade; operators get a clear control surface.
- 03
Teammates Lab
A small agent plane with real seams — useful, not theatrical.
- Problem
- Assistants need memory, tools, and boundaries — not another chat wrapper.
- System
- Roles, tool gates, shared docs as the human–agent contract.
- Outcome
- Quiet proof of craft; optional lab egg, never the hero.
04Writing
Notes live on docs.
Architecture notes and decision logs live on the public Outline at docs.isnan.me — not mirrored here.
docs.isnan.me ↗05Signal
Contact.
Email for work. LinkedIn and GitHub for the trail.