Built on the WhatsApp Business Platform
Buy the platform. Not a seat on someone else's.
Oriel Chat Engine, licensed as source. Your infrastructure, your brand, your customers, your data, no recurring platform rent. Production-proven on four live brands before it was ever offered for sale.
Every white-label programme in this market keeps you dependent.
You can verify this in five minutes, and you should.
Search for a white-label WhatsApp platform in India and you will find perhaps a dozen offers. Read what each one actually delivers and they collapse into one shape: you get a branded panel on the vendor's infrastructure. You pay a setup fee, or a wholesale price per workspace, or you fund a message wallet. You put your logo on their dashboard. Then you pay, per client, forever — and the day the vendor changes their pricing, deprecates a feature, or stops answering email, your clients are on their servers and you have no code, no database and no leverage.
Several of them market this as the benefit. No technical knowledge required — we handle the servers. That is true. It is also the whole trap, stated plainly.
You rent the panel forever. We hand over the code.
We license the repository. You deploy it on infrastructure you control, under your own name, and you are not our tenant. There is no per-client fee, no per-seat fee, no wallet, no kill switch, and no month in which we can change your economics.
Three licences, described by what you may do
Tiers here are rights, not feature lists. Every tier includes the entire platform — the core library, the deployed application, all eighteen resources, the automation engine, the canvas, the API, the webhook framework and the n8n nodes. Nothing is held back to sell you later.
Single Deployment
Run the platform for your own business, on your own infrastructure, under your own name. Unlimited tenants, agents and WhatsApp Business Accounts within your organisation. Modify the source for your own use. You may not resell it, sublicense it, or operate it as a service for third parties.
White-Label
Everything above, plus the right to operate the platform as a service for your own clients under your own brand, with your branding throughout the product. Your clients are your clients; we do not see them, do not contract with them, and do not bill them.
Reseller
Everything above, plus the right to sublicense deployments to other businesses who will run their own instances. Territory and exclusivity are negotiated case by case, and the answer is not always yes.
Licences begin at ₹6,00,000 one-time, plus 18% annual maintenance from year two. Final price depends on rights granted, deployment count and support scope, so we quote rather than publish. All prices exclude 18% GST.
If you would rather this were run for you than handed over, start here → — a business that needs the software but not the ownership is better served at ₹25,000 a month, and we would rather point you there than sell you a licence you did not need.
Yes, there are ₹6,000 scripts. We know. You have already found them.
Search CodeCanyon for a WhatsApp SaaS script and you will get roughly a hundred results between $39 and $139. Several have a thousand sales. The feature lists read almost exactly like ours: multi-tenant, chatbot builder, broadcasts, API, white-label. On paper there is no difference at all.
We are not going to argue that the paper is wrong. We are going to tell you what the paper does not contain.
| Marketplace script | Oriel Chat Engine licence | |
|---|---|---|
| Who you are buying from | An anonymous marketplace seller | A registered Indian company running this software in its own production |
| Evidence it works at load | Sales count | Four live brands, migrated off a commercial platform, in production today |
| Who is accountable when it breaks | Marketplace comment thread | A named engineer, in a contract, with a response time |
| If the seller stops shipping | You own an unmaintained codebase | Source escrow can be arranged as part of the licence agreement |
| Handover | A zip file | Structured knowledge transfer with your engineers |
| Two years from now | Whatever the seller decided | 18% AMC — security patches, Meta API changes, upgrades |
The honest version: if your requirement is a working WhatsApp panel and you have an engineer who enjoys owning unfamiliar code, a $69 script may genuinely be the right purchase, and we will tell you so on the call. What ₹6,00,000 buys is not more features. It is a counterparty — a company with its own revenue riding on the same codebase, which is a materially different incentive from a seller whose relationship with you ended at checkout.
Written for whoever has to own this
The architecture was decided before there was anyone to sell it to.
Oriel Chat Engine is two repositories, not one.
chat-engine-core is an installable Composer library. It is headless and deliberately UI-agnostic — no Filament, no admin panel, no presentation layer of any kind. Domain logic, migrations, services. chat-engine-deployment-oriel is the runnable Laravel application that depends on it and carries every Filament resource and panel asset.
That separation costs real effort to maintain and buys nothing in a demo. It exists because the domain layer should be consumable by any presentation layer — which means if you already have an agent console, a CRM, or an internal operations UI, you can drive this from it rather than around it. No marketplace script offers that, and no rented panel can.
We mention it because it is the kind of proof that cannot be staged. It was built that way when the only customer was us.
The rest of the engineering picture
- Multi-tenant isolation at the query layer. A global Eloquent scope, registered once, not hand-written where clauses scattered through the codebase. A query that names no tenant refuses to run rather than returning every tenant's rows. The isolation test is the first test in the suite and has been since the first week.
- Referential integrity chosen deliberately. Deletes are restricted, not cascaded and not nulled. We learned that the hard way: cascading deletes silently destroyed campaign records when a template was removed, and nulling silently un-attributed data. Both failures were invisible until we went looking. Now the database refuses the delete instead.
- Queue architecture. Campaigns are Redis-queue-backed and resumable — a broadcast survives a worker restart mid-send and picks up where it stopped. Nothing long-running touches the web process.
- Outbound webhooks with a circuit breaker and alerting. A failing endpoint trips out rather than retrying forever, and someone is told. Silence is treated as a failure mode, not a quiet success.
- Audit logging across template edits, role changes and administrative actions — who, what, when, before and after.
- Automation engine, nineteen node types, with a resumable node contract, SSRF-guarded outbound HTTP, abandoned-run expiry, and three-stage validation on save and publish.
- Deployment and rollback tooling. A release script that takes a verified database dump — verified, not merely taken — tags a rollback point, fast-forward-pulls, traps errors, and runs a health smoke test before it returns. Nightly backups on cron.
- Documented provisioning runbook and a development document covering architecture, decisions and known constraints. Both ship with the licence.
- Test suite, run in CI on every push, gating release.
Stack: PHP 8.4, Laravel 12, Filament 3, MySQL, Redis, Alpine.js. Deployed on nginx. Nothing exotic; your team will recognise all of it.
What a licence does not include
Stated plainly, because finding out later is how these deals sour.
- Hosting. You provide and pay for infrastructure. We will specify it.
- Meta's message charges, and your relationship with Meta generally. You register your own accounts, submit your own templates, and pass your own business verification. We advise; we cannot approve.
- Business Solution Provider status. We are not a BSP and neither are you by buying this. You connect to Meta's Cloud API as a business or as your clients' Third Party Service Provider, with the obligations that carries.
- Ongoing operations. A licence is software, not a service. If you want it run for you, that is the managed offering, and the two can be combined.
- Custom development. Quoted separately.
- Feature guarantees. AMC covers security patches, Meta API compatibility and the upgrades we ship. It is not a commitment to build what you ask for.
- AI agents. Not in the product today. We will not sell you a roadmap.
Tell us what you are trying to build
We reply to every enquiry within one working day. If a licence is not the right purchase for you, we will say so — including when the answer is the ₹25,000-a-month managed deployment instead.