Custom business systems, built right

That is the fair question to ask, and the honest answer is that there is no team to escalate to and capacity is finite. What reduces the risk is deliberate: you own the code and the database in your own repository, deploys run from a pipeline rather than from a laptop, and the stack is intentionally mainstream — NestJS, Express, Spring Boot, PostgreSQL, Vue and Next.js — so any competent engineer can pick it up. You are not holding a system only one person can read.

Because scope decides it, and scope is not knowable before the first conversation. What you get instead is a written scope and a number before anything is built, so the decision is made on paper rather than on trust. If it does not look worth it at that point, that is a perfectly good place to stop.

Those four are multi-tenant SaaS: you subscribe per organisation rather than commissioning a build. A new workspace starts on a free 30-day trial of the Pro plan, and there is no permanently free tier — when the trial ends you move to a paid plan, or the workspace is suspended with your data kept intact for a grace period. Payment is by Bakong KHQR or ABA PayWay in Cambodia, and by card elsewhere. Hotel and Shop are not sold this way: they are deployed per client, and Chat runs on your own servers.

Yes — the code and the database, in your repository, on a stack you could hire for. That is the point of avoiding a bespoke framework: nothing here is designed to make leaving expensive.

Usually that is the whole job. Most operational pain is not a missing tool, it is a person re-typing data between two tools you already pay for. Integrations run on APIs, webhooks or schedules, are idempotent so a retry cannot double-post, and alert loudly when they break rather than failing quietly.

Often, yes — and you will be told so. Custom software earns its cost when the way you work is genuinely different from the assumptions an off-the-shelf tool makes, or when the tool built for another market leaves you maintaining a pile of workarounds. If that is not your situation, buying is the cheaper answer.

Not yet, and the site says so rather than blurring it. Nine systems are built and six are deployed and running on the pre-production environment — reachable, demonstrable, shipped through the same CI-gated pipeline. They are labelled Pre-live rather than Live because a visitor reads "Live" as "in production", which is exactly what they are not. The labels will change when that changes.