A working system beats a claim about one.
The public portfolio here is short, and it is short on purpose. What we can show, you can open and test yourself. What we cannot show yet is explained further down instead of dressed up.
API Indonesia
We designed it, built it, and we operate it. A REST API platform that turns scattered Indonesian public data into unified, documented endpoints. It is not a case study written after the fact. It is a running product with a self serve dashboard, published pricing, and a free tier anyone can sign up for.
- Indonesian public data is spread across separate agencies and portals.
- The same information arrives in different shapes, with different codes.
- Most teams write the same fetching, cleaning, and matching code again.
- One REST surface over 23 API groups, with consistent responses.
- 77 MCP tools, so an agent can call the same data without glue code.
- A dashboard, documentation, and a billing path around the endpoints.
- Single x-api-key authentication with a self serve dashboard.
- Credit quotas where only successful requests are counted.
- Free and paid plans, deployed on the Cloudflare edge network.
Provinces down to villages, plus postal codes
Schools by NPSN code and universities
Hospital directory across Indonesia
BMKG earthquake feed, refreshed hourly
Prayer schedules, national holidays, Hijri dates
Halal certificates and BPOM product registry
Every figure above is on the live product, not reported only here.
Gated API
A managed way to work with APIs that are difficult to reach: provider onboarding, customer authorization with defined scopes, rate limit handling, and a request trace for every call.
Read the outlineThis one is honest about its stage. There is no live platform, no signup, and no pricing. It is a direction we are validating with people who have the problem, and it is listed here so the shape of the studio is clear rather than to imply a product exists.
- Nothing to buy today
- No customer deployments
- Built only where a provider permits it
- Will move to a live entry once it ships
Patterns we build.
These are the shapes of a typical engagement rather than descriptions of specific client work. Read them as the kinds of systems we build, not as projects that have been delivered to the companies you might picture.
Intake to record
A form, an inbox, or a marketplace order becomes a validated record in the system of truth. Duplicates are caught, and bad input is held with its context instead of disappearing.
Lead routing and CRM sync
Deduplicate, enrich, assign to a named owner, and write back. The first response stops depending on who happens to be awake.
Scheduled reporting
Figures pulled from several tools on a schedule, reconciled, and delivered as one report where every number can be traced to its source.
System to system sync
Two systems that drift apart, kept in step, with a reconciliation pass that reports the differences it cannot resolve rather than hiding them.
Internal tool over a messy source
A small interface over data that currently lives in spreadsheets and exports, so answering one question stops meaning five open tabs.
Alerting and escalation layer
Failures across existing workflows routed into one channel with the run, the input, and the next action attached, so an alert is actionable.
Each of these is built the same way: error handling written alongside the happy path, alerts routed to a named owner, and a runbook handed over at the end. See how a build is scoped.
Client case studies.
There are none on this page, and that is a decision rather than an oversight. Client work runs under agreement, and an outcome number is only worth reading if you can see how it was measured and who stands behind it.
When there are figures we can publish, with permission and with a method next to them, they will appear here. Until then the proof we offer is a product you can open, sign up for, and test in a few minutes.
Check the work yourselfNo client names without permission
Client work sits under agreement. A logo wall is easy to assemble and easy to fake, so there is not one here.
No number we cannot show the method for
Hours saved and percentages need a baseline, a measurement window, and someone willing to confirm them.
No invented testimonials
There are no client quotes on this site. When there are real ones, they will carry a real name attached to them.
Illustrative things are labelled
Any example interface or example figure anywhere on this site is marked as an example where it appears.
Judge the work, then bring us the workflow you are tired of babysitting.
A fit check is a short conversation about what is breaking and how often. If it is not a fit, we say so in that call.