From the build.
Production deep-dives from the team that ships — how we build SaaS, ERPs, apps, payments and automation, what we threw away, and what we learned.
Earlier notes
9 posts- Labs
Shipping Aira Nexus Labs
A cloud LIMS for Indian diagnostic centers — patients, samples, billing, NABL.
Read - Campus
How the Smart Ledger stays consistent at scale
A look inside the double-entry engine behind fee collection — and how it stays correct under load.
Read - Campus
The 7-day go-live playbook for school ERP onboarding
Data migration, staff training, day-one fires, and the rollback plan — how Campus actually goes live in a week.
Read - Platform
Designing Aira Nexus' shared identity layer
SSO across Campus, Creator and Labs — role propagation, tenant boundaries, JWKS rotation, and why we don't use Auth0.
Read - Campus
"Biometric attendance: why we ship our own SDK wrapper"
RFID, face and fingerprint trade-offs, offline-first edge sync, and what tier-2 internet does to your assumptions.
Read - Campus
Idempotent fee posting: designing out double-charges
A double-entry primer, idempotency keys, race conditions, and why money never lives in a float.
Read - Creator
Scaling Meta Graph API automation under load
Rate limits, webhook reliability, and the 24-hour message window — what it takes to run Creator at production scale.
Read - Labs
Why we built our own LIMS instead of buying
NABL alignment, the sample lifecycle, barcode tracking, and the build-vs-buy economics for Indian diagnostics.
Read - Campus
Building a multi-tenant ERP for Indian schools
Architecture decisions behind Campus — tenant isolation, board-specific compliance, and the parent-app trade-offs.
Read