General FAQs

Common questions about what WaDesk is, how the three WhatsApp engines work, what your CodeCanyon license allows, and whether you can run it as a multi-tenant SaaS or resell it. If you are evaluating WaDesk before buying, start here.

About the Product

Q: What exactly is WaDesk?

A: WaDesk is a self-hosted WhatsApp business platform built on Laravel 12. It combines a shared Team Inbox, bulk campaigns, a visual flow builder, template management, an AI suite, and a full multi-tenant admin panel with plans and billing. You install it once on your own server and own the whole stack — there are no per-message or per-seat fees charged by us.

Q: Is it self-hosted or a cloud service?

A: WaDesk is fully self-hosted. You download the source from CodeCanyon and deploy it to your own hosting or VPS. There is no central WaDesk cloud your data passes through — all conversations, contacts, and credentials live on your server. See the Installation FAQs for hosting requirements.

Q: Who develops WaDesk?

A: WaDesk is a commercial product distributed on CodeCanyon by Media City. Support and updates are delivered through your CodeCanyon purchase. WaDesk is an independent product and is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta. See the Disclaimer for details.

The Three WhatsApp Engines

Q: What are the three engines, and how do they differ?

A: Every workspace connects WhatsApp through one of three interchangeable engines. The inbox, campaigns, flows, and templates all adapt to whichever engine a workspace is on:

  • Unofficial API: Connect any WhatsApp number by scanning a QR code, exactly like WhatsApp Web. Powered by the bundled Node.js bridge. Fastest to set up and needs no Meta approval, but it is unofficial and carries ban risk — see WhatsApp & Ban Safety.
  • WhatsApp Cloud API (Meta): The official Meta Cloud API. Requires a verified WhatsApp Business Account and pre-approved message templates, but offers the highest trust and access to official features such as WhatsApp Forms and the verified green tick path.
  • Twilio WhatsApp: Send through a Twilio WhatsApp sender using Twilio's own content templates. A good fit for teams already using Twilio for their messaging and billing.

Q: Which engine should I start with?

A: If you want to be live in minutes and are comfortable with the risk profile of an unofficial connection, start on the Unofficial API. If you are running a real business at scale, marketing to opted-in contacts, or need long-term stability, the Cloud API is the durable choice. Because engines are per-workspace, you can begin on the Unofficial API and migrate a workspace to the Cloud API later without changing how the app works.

Q: Do all features work on every engine?

A: Most do, but a few are engine-specific. For example, native WhatsApp Forms require the Cloud API engine because they rely on Meta Flows, and template approval workflows differ between Cloud API and Twilio. WaDesk hides or gates engine-specific features automatically, so operators never hit a dead end.

Licensing Basics

Q: What license do I get when I buy on CodeCanyon?

A: WaDesk is sold under the standard Envato Market licenses. The Regular License covers a single end product where end users are not charged for access. The Extended License is required when end users are charged for access — which is the case for a paid multi-tenant SaaS. Review the official terms on the Envato Market Standard Licenses page.

Q: Can I use one license on multiple domains or installations?

A: No. Each license covers one single end product (one installation). If you want to run WaDesk for several unrelated businesses on separate installations, you need a separate license for each. Note this is different from multi-tenancy — one installation serving many client workspaces is a single end product (see below).

Q: What about support and updates?

A: A purchase includes 6 months of support from Media City through CodeCanyon, extendable at checkout or later. Updates are free for the lifetime of the item — you can download every future version from your CodeCanyon downloads page regardless of whether your support window is still active.

Multi-Tenant & SaaS

Q: Is WaDesk multi-tenant out of the box?

A: Yes. WaDesk is multi-tenant by design. Each customer gets an isolated workspace with its own WhatsApp connection, contacts, team members, conversations, and branding. The admin panel includes subscription plans, free trials, coupons, wallet credits, and granular per-plan feature gating — everything you need to run it as a WhatsApp SaaS without writing code.

Q: Can I charge my own customers a monthly subscription?

A: Yes — that is a primary use case. You define plans in the admin panel, connect one of the 30+ supported payment gateways, and customers subscribe and self-serve. Because you are charging end users for access, this requires the Extended License from CodeCanyon.

Q: How isolated is each tenant's data?

A: Workspaces are logically separated, and team access is governed by role-based permissions (for example owner, manager, and agent roles). A user in one workspace cannot see another workspace's conversations, contacts, or settings. The platform owner (you) retains full oversight through the admin panel.

White-Label & Reselling

Q: Can I white-label WaDesk with my own brand?

A: Yes. You can change the application name, logo, favicon, colors, and message footers. Branding can be set at the platform level and, where enabled, per workspace — so an agency can present its own brand to clients. No WaDesk or Media City branding is forced on the front end of your installation.

Q: Can I resell WaDesk itself?

A: You can sell access to your end product (subscriptions to your hosted WaDesk-powered service) under the Extended License. You cannot resell or redistribute the WaDesk source code, repackage it as your own item, or sell it on as a script — that violates the Envato license. In short: sell the service you build with it, not the code.

Q: Can I modify the source code?

A: Yes. You have full source access and may customize WaDesk for your own end product. Keep in mind that heavy core modifications can make future updates harder to apply, and support does not cover issues introduced by custom code changes. See the Developer Guide for safe extension points.

WaDesk Documentation