I build the systems your organization runs on.
Architecture-level work — authentication & SSO, multi-tenancy, and complex domain systems for government, SaaS, and enterprise.
Laravel · React · Next.js · Inertia.js · TypeScript · Flutter · Python · PostgreSQL · Redis · Docker
Systems that carry real operations
Multi-tenant SaaS platforms
One codebase, many isolated customers.
Tenancy isolation, role-based access, billing, and the data boundaries that keep one customer's data invisible to the next.
Authentication & SSO systems
One identity across every app.
Centralized identity with OAuth2, OIDC and PKCE — so a person logs in once and every internal application trusts it.
Complex web apps & ERP
Domain logic that models the real business.
Workflow systems, integrations and domain modeling for operations that don't fit an off-the-shelf tool.
Rescue & scale existing codebases
Inherit the mess, ship the fix.
Architecture audits, refactors, performance tuning and DevOps for a codebase that has outgrown how it was built.
What I reach for, tiered by how deep I actually go.
Production systems real organizations depend on.
Clients described by sector, not name. Each is a problem, a decision, and an outcome.
Multi-tenant school management SaaS
Problem: Many schools, each needing their own operations platform, without spinning up a separate app per school.
Outcome: One platform, many tenants, fully isolated data — 40+ schools on a single codebase. The same tenancy architecture now runs esko.id, a lighter attendance-only product spun out of it.
Centralized SSO for a government agency
Problem: Password sprawl across HR, attendance, correspondence and e-signature apps.
Outcome: One identity, five apps, zero password sprawl.
Wedding-invitation SaaS
Problem: A self-serve product with per-customer subdomains and billing.
Outcome: A product I architected, built and operate myself.
District-wide student admissions system (SPMB)
Problem: A regency ran new-student admissions for two school levels on paper and spreadsheets — thousands of applicants, manual document checks, and zonal-quota rankings computed by hand.
Outcome: One codebase serving both SD and SMP: online registration, document verification, and automated selection by zonal distance, affirmative-action and achievement paths — around 10,000 applicants ranked automatically, with WhatsApp notifications.
Member & governance platform for a mass organization
Problem: A provincial membership organization ran on paper and spreadsheets — member data scattered, regional branches coordinated ad-hoc, and activities left undocumented.
Outcome: One platform for the whole org: member database, live org-structure chart, agenda, news and an e-office letter workflow — plus a member portal with self-registration gated by admin approval. Deployed as a Dockerized stack behind a shared Caddy proxy with automatic HTTPS.
Centralized HR, attendance & payroll for a multi-branch bakery
Problem: Every bakery branch tracked attendance, payroll and KPI on paper and spreadsheets — no central visibility across branches, no licensing control, and no way to suspend a branch that stopped paying.
Outcome: One centralized platform for every branch: fingerprint attendance, automated payroll with snapshotted slips, per-position KPI, and a per-branch license/billing kill-switch — unified owner and branch dashboards behind role-based access.
Predictable delivery. Foreign clients buy that most of all.
Discovery
I map the domain, constraints and the real problem before writing a line of code.
Architecture
A written plan: data model, boundaries, auth, and the tradeoffs I'm choosing — before build.
Build in increments
Shippable slices you can review, on a cadence you can plan around. No black boxes.
Handover & support
Documentation, a clean deploy, and a system your team can actually maintain.
I'm in Medan, Indonesia (Asia/Jakarta) with a reliable 4-hour daily overlap with EU and ~2 hours with US East. I write things down — decisions, APIs, and runbooks — so progress survives timezones and doesn't live only in my head. Async-first, with a scheduled call when it's faster than typing.
I care about systems that are still maintainable in year three.
Hi — I'm MHD Andra Fahreza, a senior full-stack engineer based in Indonesia. For six years I've built the kind of software organizations actually run on — government digital services, multi-tenant SaaS, ERP, and large-scale data processing. My favourite problems are architectural: identity, tenancy isolation, and domain models that hold up as requirements change.
Have a system that needs building — or fixing?
Tell me the problem and the constraints. I'll tell you honestly whether I'm the right person and how I'd approach it.