Engineering
The order that arrives twice
A customer taps pay, the connection stalls, they tap again. Somewhere in the warehouse two identical boxes get packed. The fix is not a faster button.
Read →Product studioBali, ID
Software that earns its keep.
We buildapplications
We build the systems businesses actually run on — the application, the back office, the payment rail, the thing that has to be correct on a Monday morning.
ID / ENWorking languages
UTC+8Studio time
staging.apex — back office
OverviewOrdersPaymentsStockUsers
Orders
1,284
Paid
96%
What we do
Nine disciplines, one team. Most projects use three or four of them at once.
Web Development
Software that runs the business, not a brochure with a contact form.
UI/UX Design
Interfaces designed against the job, not against a screenshot competition.
Mobile App Development
One codebase, two stores, and a release process that does not frighten anyone.
E-commerce Solutions
Checkout that clears, stock that reconciles, and payment methods people here actually use.
SEO Optimization
Technical foundations first. Content second. Tricks never.
Digital Marketing
Spend attached to outcomes you can defend in a board meeting.
CRM
The pipeline your team keeps updated, because it costs them nothing to.
B2B Platforms
Dealer portals, tiered pricing and approval chains that mirror the real hierarchy.
Selected work
All projects
Web Development
depodinamik
A warehouse network you can search the way tenants actually think about it — by province, by floor area, by how many pallets fit.
Web Development
Karaport
A marketplace for used industrial machinery, built so a machine can be found the way it is actually bought — by category, by seller, and by where it is standing.
- 01
Discovery, written down
A week of mapping data, roles and the flows that carry the business. It ends in an architecture decision record — what we chose, what we rejected, and why. You keep that document either way.
- 02
Two-week increments
Work lands on a staging environment you can open at any time. Nothing is hidden until launch, which means course corrections cost days rather than months.
- 03
Built for the second year
We write the boring version — explicit names, obvious control flow, tests around anything that touches money. The expensive part of software is the person who inherits it.
- 04
Handover that holds
What transfers at the end — repository, deployment pipeline, runbook, credentials — is written into the agreement before the work starts, not decided once it is finished. Whatever that says is yours is handed over in your name, and if you want to continue without us, you can.
From the blog
The decisions behind the work, written up rather than explained twice.
Design
Nobody reads your homepage
They scan it, decide in a couple of seconds whether you do the thing they came for, and leave if the answer is anywhere below the fold.
Read →
Commerce
Stock that lies
The number on the product page is not the number in the warehouse, and the gap between them is where refunds, apologies and lost customers live.
Read →Ask us something.
One question, one answer, no qualification call and no account manager. WhatsApp is the fastest; email is fine too.
Message us on WhatsAppWe read every message ourselves and reply within two working days.
Tell us what is not working.
A quote takes about five minutes to request and we reply within two working days — with a real assessment, not a brochure.