I reverse-engineer private APIs and application protocols, rebuild them as stable backend services, then integrate and deploy them into real products.
Request replayed, signature rebuilt.
The work starts before the code. I capture real traffic, inspect every request, and map authentication, signatures and obfuscation until the protocol underneath stops being a mystery.
Then I write the backend that makes it boring: stable services, honest docs, monitoring, and deployments that stay up.
Five systems in production, from private-API gateways to protocol-level bots.
EXAPI unifies eight independent platforms behind a single private-API gateway: reverse-engineered clients, queued workers, Redis caching and a monitored pipeline, serving live production traffic.
Read the docsI rebuilt the private media endpoints and turned raw audio streams into structured, cacheable responses served with sub-second latency. The hard part was never the audio. It was the handshake in front of it.
Scrapers collect listings across regions. A pipeline cleans, deduplicates and geocodes them, and analytics turn market noise into price curves, supply signals and a queryable dataset that also powers private web apps and price comparison.
Incoming messages are parsed at protocol level, framed, signed and decoded, then routed through a rule engine and LLM helpers and answered in milliseconds. Full conversations, no human in the loop, no official bot API.
I design the backend around the model: prompt pipelines, context stores, streaming endpoints, cost and rate controls. Then I deploy it into existing products, from a single chat widget to a fully automated workflow.
Unknown request, analyzed, reconstructed. Auth, signatures and obfuscation mapped, documented and reproducible.
Requests enter, responses leave, for years. Versioning, rate limits, monitoring and uptime worth trusting.
From a prompt in a notebook to a model serving real traffic, inside software people already use.
Raw web data in, clean structured data out, with pipelines that keep datasets fresh on schedule.
Dashboards, landing pages and admin tools for the systems I build. Explore the demo
Every tool earns its place in a real backend architecture.
It's a gray zone I take seriously. I build for interoperability and automation on accounts and data you legitimately control, document everything transparently, and flag compliance questions before code is written. You own the decisions — I make sure they're informed ones.
Every client ships with contract tests and monitoring that watch response shapes in production. When something drifts, I get pinged before your users do, and fixes usually land the same day.
You send a brief. I reply with a technical take and a feasibility read — sometimes the honest answer is "don't build this." If it's a go, we scope the work, agree on a fixed quote, and start capturing traffic.
It depends on protocol complexity and how much of the surface we need. Small integrations start around a few hundred dollars; full gateway systems become ongoing engagements. You always see a number before any work begins.
Tell me what you're trying to access, automate, integrate or build. I read every brief myself and reply with a technical take, not a sales pitch, usually within a day.
Country-level counts, reset daily at midnight WIB. No IPs, no personal data.