Dartstudio is home to a group of technology veterans who decided, after years elsewhere, to build something their own way.
Origin
We all come from different places, but our stories sound similar.
Some of us worked at agencies — where quality was always negotiated against deadlines, and every project almost always ended with technical debt left for whoever came next. Some were engineers or architects at large vendors, watching up close how large-scale systems were assembled — and sometimes assembled in a hurry. Others were at corporates: employees whose job was to maintain legacy systems built on years of unquestioned technical decisions.
At every one of those places, we reached the same conclusion: we were tired of being the people who cleaned up other people's messes.
Dartstudio was born from a simpler question: what if we stayed small? Don't scale headcount. Don't chase clients. Just a group of people serious about systems, focused on building their own products, and occasionally — if the vision fits — open to working with the right collaborators.
It's been a few years since then. We're still small. That's intentional.
Principles
A few convictions we hold as standards.
01
Code written without architecture is like a house built without a foundation: fast to erect, hard to extend, collapses at the first tremor. We refuse to start any project without an architecture design phase, however short the timeline.
02
We write code assuming the next reader is not us. That changes many things: naming matters, documentation matters, folder structure matters.
03
If you can't explain why you chose a complex solution to an experienced engineer outside the team, the solution probably didn't need to be complex.
04
Every library, framework, or service you add to a system is a long-term commitment. We think through every choice with the awareness that it will accompany us for a long time.
People
Everyone at Dartstudio has their own page, with a publicly visible work history.
Founder & Product Lead
Founder of Dartstudio. Designer and product thinker with a decade of UI/UX experience in global education tech, plus founder-side experience building his own products elsewhere. His focus: translating business complexity into experiences that make sense in users' hands.
Co-Founder & CTO
Co-Founder of Dartstudio. Engineering leader with deep mileage in MLOps, backend architecture, and AI platforms. Over a decade of building systems from infrastructure layer up to user-facing products.
Co-Founder & Business Partner
Co-Founder of Dartstudio and Director of Prihaditama Consulting — a Geosciences consultancy he has run since 2010. Aldi brings something rare to a technical studio: business sense proven by time, not by decks.
How We Work
Focus, not multitasking. We don't take on many parallel projects. Every active engagement gets the full attention of the assigned person, without having to share headspace with three other clients.
Async-first, but not async-only. Written communication is our default — so decisions have a trail. But for complex thinking, we believe in focused direct conversation. Weekly syncs, decision documentation, no surprises.
Senior-led, in every engagement. There's no 'junior engineer does it, senior reviews'. Projects at Dartstudio are led by the same person who joined the initial call. You talk to the ones doing the work.
Honest about timeline. We don't promise timelines we know aren't realistic. If a project takes three months, we say three months.
—you might be interested in how we collaborate with outside partners.