Loading TechDinoYes, where the written agreement grants resale. 36 products are rebrandable, and 6 of them run as multi-tenant platforms where the reseller operates one deployment and onboards clients as accounts underneath it. Applicable source code is provided for the agreed scope, self-hosting is standard, and no revenue share is taken on the reseller's client sales.
Client pricing, setup fees and subscription tiers are the reseller's to set. No revenue share is taken on those sales; licence and project cost is agreed separately in the quotation.
Clinic, school, garage, retail, laundry and rental products already exist and run live demos, so an agency can quote a vertical it has no engineering capacity to build from scratch.
Each of these is expensive to reverse once clients are live, so they are settled in writing before build rather than discovered later.
A multi-tenant platform means a single deployment the reseller operates, with each client as an account underneath it — one codebase, one upgrade, shared infrastructure. A per-client deployment means a separate instance each time, which isolates clients completely but multiplies hosting and upgrade work. Moving from shared to isolated after launch is substantially more work than choosing correctly at the start.
Platform name, logo, colours and domain are usually the reseller's. Per-client branding — the client's own logo, login page, invoice header and notification sender name — is a separate layer that only some products support. Which layers exist is confirmed per product against its white-label options.
The default commercial licence covers deployment for an agreed operational scope and does not by itself grant resale or redistribution. Reselling to third parties is permitted only where the written agreement says so. Permitted client counts, sub-licensing and what happens if the reseller relationship ends are settled in that agreement before build, not after a client is signed.
In most reseller arrangements the reseller is the client's support contact and TechDino supports the reseller, not the end client. That boundary decides what documentation and admin access the reseller needs at handover, so it is agreed rather than assumed.
On a multi-tenant platform, adding a client should be an admin action the reseller performs without developer involvement — account, branding, plan and limits. If provisioning requires a developer each time, the model does not scale past a handful of clients, so this is specified as part of the platform admin scope.
Hosting, domains, payment gateway fees, SMS, WhatsApp, maps, email delivery and app-store accounts are third-party costs that remain separate from the software. In a reseller model they usually sit with whoever operates the deployment, and that allocation is worth stating in the reseller's own client pricing.
One deployment the reseller operates, with each client as a separate account underneath it — their own branding, their own data, added by an admin action rather than a new build.
Runs either as a single-business deployment or with multiple client accounts under one platform; which applies is set during scoping.
Runs either as a single-business deployment or with multiple client accounts under one platform; which applies is set during scoping.
One platform deployment with separate client accounts underneath it, each with its own branding and data.
One platform deployment with separate client accounts underneath it, each with its own branding and data.
One platform deployment with separate client accounts underneath it, each with its own branding and data.
One platform deployment with separate client accounts underneath it, each with its own branding and data.
Rebrandable, but deployed once per client rather than sharing a platform. This isolates each client completely, at the cost of separate hosting and upgrades for every deployment.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Rebranded and deployed once per client, on hosting that client or the reseller controls.
Resale is permitted where the written agreement grants it. The standard commercial licence covers deploying the software for an agreed operational scope and does not by itself allow redistribution or resale, so reseller terms — permitted client counts, sub-licensing and branding rights — are agreed in writing before build.
6 of the 36 rebrandable products are built to run one deployment with separate client accounts underneath it. The rest are white-label in the sense that they are rebranded and deployed once per client. Which model a product supports is a property of that product, not a pricing option.
No revenue share is taken on the reseller's own client sales. The reseller sets their client pricing, setup fees and subscription tiers. Licence and project cost is agreed separately in the quotation.
Applicable source code, database schema, included migrations and setup documentation are provided for the applications and modules listed in the agreed purchase scope. What may then be done with it — modification, deployment, redistribution, resale — is governed by the applicable agreement or licence.
In most reseller arrangements the reseller is the client's first line of support and TechDino supports the reseller. That boundary is agreed during scoping, because it determines the admin access and documentation handed over at launch.
On a multi-tenant platform that is the intent: creating a client account, applying their branding and setting their plan should be an admin action. Where a product is deployed once per client instead, each new client is a new deployment and needs setup work.
Yes. Deployment to a reseller-controlled VPS, cloud instance or dedicated server is the normal arrangement. Hosting, domains and third-party services are separate accounts and costs.
Send the vertical you serve and the number of clients you expect to onboard. The tenancy model, branding layers, licence terms and support boundary are confirmed in writing before any build starts.