Kasetsart University Sriracha CampusWeb application
KU DMS
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.
Web development studio — Thailand
We buildwebsites
Web apps · APIs · MVPs — from idea to production
Compax Tech is a small senior team. You get a written scope before anyone writes code, a working URL every week, and the whole thing handed over at the end — no lock-in.
Six things, done properly
Not a menu to browse. We build the software layer a business runs on, design it before it is built, and test it — including trying to break it — before your customers do.
- 01
Web development
The surface your customers use — a site or an app that stays fast as the content and the traffic grow.
- React / Next.js
- Performance audit
- SEO groundwork
- 02
Mobile development
One codebase, both stores — an app that behaves like it belongs on the phone rather than a website in a frame.
- iOS + Android
- Store submission
- Offline-first
- 03
Software testing
A suite that catches the regression before your customer does, on the paths that actually cost you money.
- End-to-end tests
- CI gate
- Regression suite
- 04
Penetration testing
We attack the system the way someone else eventually will, then hand you the findings ranked by what each one would actually cost.
- OWASP Top 10
- Ranked findings
- Free retest
- 05
UX & UI design
Flows and screens agreed before anyone writes code, in a file a developer can build straight from.
- Flows + wireframes
- Figma library
- WCAG contrast
- 06
MVP development
The smallest version that proves the idea, built so version two is not a rewrite.
- Scope in weeks
- Scalable foundation
- Built to iterate
A list is easy to write. The systems we have shipped are right below.
Systems that are in production
Built, handed over, and running on infrastructure the client owns.
Chang Joe — construction, extensions and fit-outMarketing site
Chang Joe
A single-page site for a Bangkok contractor with more than ten years of work behind it and nowhere to show it.
Manamanee CoworkingMarketing site
Manamanee
A single-page site for a coworking space, seven meeting rooms, a restaurant and overnight rooms outside Bangkok.
Four steps, no surprises
The same sequence on every project. You always know which step you are in and what arrives at the end of it.
Step 01
Scope
One call to understand the business, then a written scope: what ships, what is deliberately out, what it costs. You approve it before anyone writes code.
OutputWritten scope + estimate
Step 02
Design
Screens and states before the backend exists, so decisions get made on something you can see rather than a description of it.
OutputClickable UI
Step 03
Build
Short cycles against the scope. You get a working URL every week, not a status report — changes land while they are still cheap.
OutputWeekly working build
Step 04
Handover
Deployed in your accounts, with the repository, environment notes and runbook in your hands. Keep us on for changes, or take it in-house.
OutputRepo, docs, deploy access
A small team is the feature
- Architecture
- ModernTyped, tested, documented
- Tech stacks
- 10+Chosen per project, not per habit
- Delivery
- WeeklyA working build every cycle
- Shipped
- 5+Projects live in production
- You talk to the people writing the code, not an account manager.
- The scope is written down before the build starts, and it is what we are held to.
- Everything is handed over: repository, environment notes, deploy access.
What founders ask first
What does a project cost?
There is no price list, because there is no standard project. You get a fixed figure with the written scope in step 01 — before any work starts — and that figure is what we are held to unless you change the scope.
Who owns the code?
You do, from the first commit. At handover the repository, environment notes and deploy access move into your accounts. Nothing runs on infrastructure you cannot reach.
Can you work with our existing codebase or team?
Yes. We start by reading what exists and writing down what we found — risks, quick wins, what we would leave alone — so the first decision is an informed one rather than a rewrite.
What happens after launch?
Your call. Keep us on for changes and maintenance, or take it in-house — the handover in step 04 is built so the second option is genuinely available.
Which stack will you use?
Whichever one fits the problem and the people who will maintain it. In practice that is usually TypeScript across the stack, React or Next.js on the front end, and Node or Python behind the API.
Something not covered here? Ask us directly — a real answer, not a brochure.
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.