About

We build ityou own it

No lock-in · No account managers · Full handover

Compax is three senior engineers who build web apps, APIs and MVPs, and then hand them over completely. This page is the four positions that decide every project we take — and the one system you can go and check them against.

Core team
3
Ownership
Yours, day one
Hosting
Your accounts
Account managers
None

01Where we stand

Four positions, and what each costs us

Any agency can claim these. What makes them real is the second line under each one — the thing we give up by holding it. If a position costs us nothing, it is a slogan.

01

You own everything we build

The repository, the environment notes, the deploy access and the keys. Work ships into your accounts and runs on your infrastructure — the last system we handed over runs entirely on the client’s own servers, and there is no account they keep paying us for.

What it costs usWe earn nothing from hosting you. A project that is finished is finished.

02

You talk to the people writing the code

There is no account manager between your business and the build. The person who answers your question is the person who wrote the thing you are asking about.

What it costs usThere are three of us. We take the work we can actually build, and we say so when a date does not fit.

03

The scope is written before the code

What ships, what is deliberately out, and what it costs — agreed as one figure before anyone opens an editor. It is what we are held to.

What it costs usIt binds us both ways. A good idea arriving mid-build gets written down and priced, not absorbed quietly and delivered late.

04

We pick the boring option when boring wins

Choices get made on what the project needs to survive five years of other people maintaining it, not on what is interesting this quarter. We keep the list public.

See what we build with

What it costs usSome of what we would enjoy building never reaches your project.

02On the record

One system you can go and open

The positions above are only worth reading if something was actually delivered under them. This is the most recent one, named, with the numbers taken from its own case study.

Kasetsart University Sriracha Campus

KU DMS — approvals, budgets and document generation for a university campus

An internal system that routes documents for approval, tracks project budgets against the documents that spend them, and lets staff design the forms and documents themselves. Built on Bun, ElysiaJS and SvelteKit, hosted entirely on the university's own infrastructure.

Build span
3 months, ongoing
Backend modules
19
Database tables
35
Migrations
32
Svelte components
242
Commits
722

03Who you get

The whole company

Not a leadership page with a delivery team behind it. These three are who scopes the work, writes the code and answers the phone afterwards.

  • CEO

    Bunyarit Jerdrujikul

  • CTO

    Pawit Thongkum

  • CCO

    Kamonchat Bunchoed

Next step

Tell us what
you need built

Send the idea in whatever shape it is in — a document, a sketch, or two sentences. You get a written scope and a fixed figure back before anything is committed to.