Portfolio / 2011 - 2026

I build systems that carry real weight.

Fourteen years of fintech engineering: payment infrastructure held to PCI-DSS discipline, ERP implementations end to end, and AI products running in production. I like problems where the cost of failure is real, because that is where careful work shows. I choose systems by the trade-offs they make, not by the frameworks they use.

Open to new projects and roles
14+
Years in technology
6
Brokerage platforms supported
2
End-to-end ERP rollouts
3
AI agents in production
20+
Projects shipped

Selected Work

Case studies from fintech infrastructure, commerce platforms, and AI systems. Every one of these ran (or runs) in production, for real users and real money.

01

MallOps Suite

Mall operations ERP on Odoo 19 Community built end-to-end: leasing contracts with state machine, automated monthly billing (rent + service charge + IoT meter readings), staged payment reminders, DOKU VA/QRIS payments with signed idempotent webhooks, 18-endpoint REST API hub with scoped API keys and rate limiting, Astro tenant portal with per-tenant login tokens, Telegram ops bot, procurement-to-PO flow, and DJP-format e-Faktur XML export. 60+ tests green on fresh databases; documented engineering log of 27 real debugging lessons.

Odoo 19PythonPostgreSQLAstroReactREST APITelegram Bot API
Open project
02

Srabutan.com

Indonesia's next freelance marketplace: full-stack platform with AI-powered matching, real-time collaboration, and secure payments.

ReactVuePythonDocker
03

UMKM St. Servatius

Community commerce platform for a parish micro-business ecosystem (umkm.servatius.id): business directory with multi-role verification workflow, tender and bazar management with a 3-layer contribution guard (UI, consent checkbox, database RLS), and paper SOP forms digitized into auto-numbered PDF permits with digital signatures. 68 static pages hardened with Row-Level Security across 25 SQL migrations.

AstroReactTypeScriptSupabasePostgreSQL
Open project

More work

What I work with

Engineering

  • React
  • Next.js
  • Astro
  • TypeScript
  • Node.js
  • Python
  • PHP
  • Laravel
  • NestJS
  • FastAPI

Data & Platforms

  • PostgreSQL
  • MySQL
  • SQL Server
  • Supabase
  • Docker
  • GitHub Actions
  • Cloudflare
  • Railway

Payments & Compliance

  • PCI-DSS compliant integrations
  • VA, QRIS, and e-wallet rails
  • Reconciliation and settlement flows
  • KYC and AML operations (Sumsub)

AI & Automation

  • LLM workflows
  • RAG pipelines
  • Multi-agent orchestration
  • n8n and Python automation

Operating principles

01

Systems over features

Model boundaries, data flows, and failure modes before code. Features are easy to add; bad seams are expensive to remove.

02

Trade-offs over hype

Every choice has a cost. I make the cost explicit and pick what fits the business, not what is trending.

03

Strategy first

Invest where the business differentiates, buy or borrow the rest. Architecture follows the win condition.

04

Built to change

Reversible decisions, recorded rationale, boring technology where it counts. The system should get cheaper to evolve, not more expensive.

Selected decisions

Architecture is judged by the calls that are expensive to reverse. Four of mine, with the cost left visible.

ADR-001
Srabutan / Payments

Shift payment risk to the provider

Context

A marketplace for Indonesian freelancers needed card, virtual account, and QRIS acceptance without holding a payment licence or building reconciliation from scratch.

Decision

Integrate Xendit's Payment Request API as a pure middleman, render VA numbers and QR codes inside our own checkout, and keep the buyer inside the product. Never redirect to a hosted checkout page.

Trade-off

More integration work and a hard dependency on one provider, in exchange for no compliance overhead and a white-label experience the buyer never sees behind.

PaymentsXenditWhite-label checkout
ADR-002
biotama.cv / Platform

Bake structural data, fetch only what is personal

Context

A personal site with hundreds of generated application pages, a blog, and a job tracker that changes daily, all running on a zero-budget static host.

Decision

Static export with structural data baked at build time. Keep personal or frequently changing data in a runtime JSON that the listing fetches, and regenerate through a sync pipeline.

Trade-off

New records need a rebuild before generated pages change, in exchange for near-zero hosting cost, fast pages, and a minimal attack surface.

Next.jsStatic exportCost control
ADR-003
UMKM St. Servatius / Data

Put trust rules in the database, not only the UI

Context

A community commerce platform handling contributions, tenders, and permits for a parish ecosystem, where a UI-only check would be one bug away from a data incident.

Decision

Enforce access with Row-Level Security across 25 SQL migrations and a three-layer contribution guard: interface, explicit consent, database policy. Digitize paper permits into signed, auto-numbered PDFs.

Trade-off

More migration work and policy maintenance, in exchange for defense in depth and an audit-friendly trail the community can trust.

SupabaseRLSCompliance
ADR-004
MallOps / ERP

Keep the ERP boring where it protects the money

Context

A mall operations suite needed leasing contracts, monthly billing, IoT meter readings, and tax-compliant invoicing under a fixed delivery window.

Decision

Build on Odoo 19 instead of a bespoke stack, and write custom logic only where it differentiates: state-machine leases, billing rules, DOKU payments, and an 18-endpoint API hub. 60+ automated tests run on fresh databases.

Trade-off

Constraint to Odoo's data model and upgrade path, in exchange for a battle-tested accounting and invoicing core and months of delivery time saved.

OdooPostgreSQLAutomation

The road here

Jan 2026 - Present

Founder & Solutions Architect

Srabutan.com · Indonesia

Jan 2014 - Dec 2025

Senior Technology and Trading Operations Manager

CITT Services · Dallas, USA

Aug 2011 - Dec 2013

Host Integrator

Wirecard (PT. Aprisma Indonesia) · Jakarta, Indonesia

Bio consistently delivers exceptional technical solutions that drive real business value. His ability to architect complex systems while maintaining clean, maintainable code is rare. Over the years, he has been instrumental in delivering projects for our most demanding fintech clients.

Nash Wadud, CEO at CITT Services

Let's build something that holds up in production.

“
The best way to get a project done faster is to start sooner.
— Robert C. Martin (Uncle Bob)
”