Anyone can build the screens. The things that decide whether a SaaS survives — tenancy, roles, billing, metering, failed payments, the admin console you did not scope — are the things a team learns by operating one. The team that builds for MLV Empire operates ten.
MLV Empire builds SaaS products for Malaysian founders and companies — multi-tenant architecture, sign-in and role-based access, subscription and usage-based billing, webhooks and public APIs, and the internal admin console every SaaS eventually needs. The engineering is done by our technology partner's team, which runs ten software products in production, including live subscription billing and a prepaid wallet that meters usage per email sent.
Every item here exists in a product the team runs today. None of it would be attempted for the first time on your budget.
Tenant isolation, per-tenant configuration and the migration story. We will also tell you honestly when single-tenant is the better answer — see below.
Sign-up, sign-in, sessions, invitations and role-based access control. Asli Dine ships twelve distinct roles, because a restaurant owner and a floor waiter must not see the same screen.
Plans, upgrades, downgrades, renewals and failed-payment handling, wired to a real payment gateway. AsliCRM and QRasli take live subscriptions today.
Prepaid wallets, per-unit debits and balance enforcement. Aslio meters every email sent against a prepaid balance, which is the harder half of usage-based billing.
A public REST API, keys and rotation, rate limits per plan, and outbound webhooks with retries — the integration surface customers ask for in month three.
Impersonation, tenant management, audit trails and the manual override every support team needs at 2am. Nobody scopes this. Everybody needs it.
Several of the products we sell — the industry systems for restaurants, schools and law firms — are delivered as dedicated single-tenant deployments rather than multi-tenant SaaS. Each customer gets their own instance, their own database, their own upgrade and their own support surface.
That was a deliberate choice and it has real benefits: total data isolation, a hosting region per customer, and the freedom to modify one customer's system without touching anyone else's. It is also why those products are quoted rather than list-priced, and why they cap how many customers one engineer can carry.
We tell you this because it is the single most consequential architectural decision in a SaaS build, it is very expensive to reverse, and most vendors will simply say "multi-tenant" because it is the fashionable answer. The team has lived on both sides of it and can tell you which one your business model actually wants, before the first migration is written.
The same stack the products run on. Nothing here is a first attempt on your budget.
| Layer | What we use | Running in |
|---|---|---|
| API and business logic | NestJS / Node.js, TypeScript | Aslio, a healthcare marketplace, the industry systems |
| Data | PostgreSQL with Prisma, Redis for queues and cache | Every product |
| Web front end | Next.js and React | QRasli, Aslio, Asli Campus, Asli Dine |
| Mobile | Flutter, one codebase for iOS and Android | Staff, practice and patient apps |
| Payments | Subscriptions, one-off top-ups and gateway webhooks; we integrate the gateway you choose | AsliCRM, Aslio and QRasli, live |
| Aslio — the email API and SMTP relay we sell | Every product that sends email | |
| Hosting | Cloud servers; a dedicated instance in your own cloud account or region on request | Every product |
Yes, and usually as a fixed-scope phase one: the narrowest thing a real customer can pay for, priced in ringgit against a written scope so you know the number before you commit. You see it work, then decide on phase two.
Yes — it runs in the products we sell today. Plans, upgrades and downgrades, renewals, failed payments and webhooks, live in production. The team has also built prepaid wallet metering that debits per email sent, which is the harder half of usage-based billing. For your product we integrate the payment gateway you choose.
It depends on your buyer, and it is the most expensive decision to reverse. Multi-tenant scales customers per engineer and enables self-serve. Single-tenant gives total data isolation, a hosting region per customer and per-customer modification — which is why enterprise and regulated buyers often demand it. The products we sell include both kinds, so we can tell you what each one actually costs to operate rather than which is fashionable.
If you want us to. Deployment, monitoring and support can be part of the engagement. Keeping software alive is the normal state of affairs for this team rather than a new service line.
Whatever the contract says, agreed before work starts — full assignment to you, or a licence at a lower price where the core is retained. We settle this in writing first, every time.
It is quoted in ringgit against a written scope, usually one phase at a time. Scope drives everything, so send yours to hello@mlvempire.my for a real number. SST is added where it applies.