Decxy Malvin
Lead engineer
Leads the team and owns the architecture and the estimate. Full-stack by background, with AI engineering on top of it, and the person accountable when a date is at risk.
The team
A small team of senior people, and no bench.
Seven core disciplines. You will meet everyone who touches your project, and they stay on it until it is live.
Who you work with
Seven disciplines, one room.
We staff a project with the disciplines it needs rather than with whoever is free. If your build does not need a mobile engineer, you are not paying for one.
Jeram Tejano
Full-stack developer, frontend-leaning
Takes a product from design to deployed: React, Next.js, Vue and Nuxt on the front, Laravel and Node behind it. Most of the platforms, storefronts and dApps in our work are his.
Kevin Anthony Wong Caicedo
Full-stack developer, backend-leaning
Data models, APIs and the integrations that have to survive a provider changing their mind on a Friday. Comfortable in the front end when a feature needs both halves moving together.
Fajar Hadi Saputra
Full-stack developer, mobile-leaning
Full-stack, but mobile is where he lives. Ships to both stores from one codebase in React Native and Flutter, and handles the release treadmill that starts the day after launch. Seven of the apps in our work are his.
Reynel Olaer
Ecommerce developer
Shopify, WordPress and WooCommerce. Custom themes, headless storefronts, product configurators and the awkward commerce requirements a bought template cannot do.
Vitto Lewerrisa
QA & release engineer
Automated coverage on the paths that take money, and the person who says no to a release when it is not ready.
Maya Lestari
Product designer
Designs the flows and then builds the design system, which is why the build matches the mockup.
How the team runs
Why a team of seven beats an agency of eighty.
Not a slogan: these are the structural reasons, and they are the same reasons a big agency cannot match them.
No layer between you and the work
At this size there is nobody whose job is to translate. You talk to the engineer, the engineer talks to you, and nothing gets lost in a weekly status call.
Everyone knows the whole codebase
Small enough that any one of us can pick up any part of your project. If someone is ill the week before launch, it is an inconvenience rather than a crisis.
We only take work we can staff
This is why the header of this site says how many slots are open rather than inviting everyone in. Overcommitting is how agencies end up putting juniors on a senior project.
One timezone band, deliberately
Core hours that overlap European and US Eastern working days. You get same-day answers instead of a 12-hour round trip on every question.
Proof you can check
We would rather show you the work than quote ourselves.
Client testimonials are easy to write and impossible to verify. These are running products with our work in them. Open any of them.
Next step
Tell us what you are trying to build.
Thirty minutes with the engineer who would lead the project. You will leave with an opinion on what to build, what to skip, and roughly what it costs, whether or not you hire us.
2 build slots open · Next start: early next month
What happens next
- 1You send a few lines about the product and the deadline
- 2We reply within one working day with times
- 3A 30-minute call, no deck, no sales script
- 4A written summary and a ballpark range within 48 hours