Anyone can build the screens. The things that decide whether a SaaS survives — tenancy, roles, billing, metering, dunning, the admin console you did not scope — are the things a team learns by operating one. We operate ten.
Asli One Global builds SaaS products for clients worldwide — multi-tenant architecture, authentication and role-based access, subscription and usage-based billing, webhooks and public APIs, and the internal admin console every SaaS eventually needs. The team runs ten of its own software products in production, including live subscription billing through Razorpay and a prepaid wallet that meters usage per message sent.
Every item here exists in something we run today. None of it is a capability we would be attempting 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. One of our products 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 gateway. Ours runs live on Razorpay today.
Prepaid wallets, per-unit debits and balance enforcement. Ours meters at one paisa per email, which is as small a unit as billing gets.
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.
Five of our own products — the industry ERPs — are sold 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 early choice and it has real benefits: total data isolation, per-customer hosting regions, and the freedom to modify one customer's system without touching anyone else's. It is also why those five products have no list price, 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. We have lived on both sides of it and can tell you which one your business model actually wants, before you write the first migration.
The same stack our own 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, Evani-class marketplaces, five ERPs |
| Data | PostgreSQL with Prisma, Redis for queues and cache | Every product |
| Web front end | Next.js and React | QRasli, Aslio Web, Asli Campus, Asli Dine |
| Mobile | Flutter, one codebase for iOS and Android | Staff, driver and patient apps |
| Payments | Razorpay — subscriptions, one-off top-ups, webhooks | Aslio and QRasli, live |
| Messaging | Aslio — our own email, SMS and WhatsApp API | Every product that sends anything |
| Hosting | AWS; application data in Frankfurt (eu-central-1) | Aslio, QRasli |
Yes, and usually as a fixed-scope phase one: the narrowest thing that a real customer can pay for, priced against a written scope so you know the number before you commit. You see it work, then decide on phase two. That is how our healthcare marketplace client has bought from the start.
Yes — it runs in our own products today. Plans, upgrades and downgrades, renewals, failed payments and webhooks, live on Razorpay. We have also built prepaid wallet metering that debits at one paisa per message, which is the harder half of usage-based billing.
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, per-customer hosting regions and per-customer modification — which is why enterprise and regulated buyers often demand it. We run five products on single-tenant and the rest multi-tenant, 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. We already operate ten products, so keeping something alive is the normal state of affairs here 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 we retain the core. We settle this in writing first, every time.
Quoted against a written scope. The published reference point is a phase-one two-sided marketplace — NestJS and Prisma API, Flutter app, partner and admin panels — contracted at INR 70,000, about USD 733. Scope drives everything, so send yours to info@asli.one for a real number.