Licensing
White-label and embedded analytics
Three deployment models with different answers to whose brand is on the screen, who owns the customer relationship and who owns the interface. Conflating them is how these arrangements go wrong, so they are separated here before anything else.
Three deployment models
Internal deployment is the baseline the other two are described against. Read across the three and the differences are the whole commercial conversation.
Internal deployment
You use DeepGarden inside your own organization, under the DeepGarden name. Your people sign in, ask questions of your data, and the product is visibly ours. This is the standard platform subscription and the baseline the other two models are described against.
- Brand
- DeepGarden
- Customer
- You are the customer
- Experience
- Canopy, as we ship it
- Suited to
- Any organization deploying internally. Most customers are here.
White-label deployment
You offer the intelligence experience to your own customers under your own name, on your own domain, with your branding throughout. We are not visible to your customers, and the commercial relationship with them is yours. The product is still Canopy — you are rebranding it, not rebuilding it.
- Brand
- Yours, throughout the product
- Customer
- Your customers, and they are yours
- Experience
- Canopy, restyled and rebranded
- Suited to
- Consultancies, data providers and service businesses that want to deliver analytics as part of what they already sell.
Embedded or OEM deployment
You build the interface. DeepGarden's governed query path sits underneath it: scope resolution, semantic interpretation, query generation, validation, execution and evidence, reached programmatically rather than through Canopy. Your users may never know we exist, which is the point.
- Brand
- Yours. We are not on the screen at all
- Customer
- Your customers, inside your product
- Experience
- Yours — you own the interface entirely
- Suited to
- Software companies adding analytics to a product they already sell, where the interface is part of their differentiation.
Who owns what
The table procurement actually reads. These are commercial descriptions of how we intend to contract, not drafted legal terms — the agreement itself is reviewed by both sides' counsel.
| Area | Internal | White-label | Embedded / OEM |
|---|---|---|---|
| Branding and visual identity | DeepGarden | Yours — name, colours, logo, domain | Yours — we are not rendered |
| User interface | Ours | Ours, restyled to your identity | Yours, entirely |
| End-customer relationship | Not applicable | Yours | Yours |
| Customer data ownership | Yours | Your customers', held under your agreement with them | Your customers', held under your agreement with them |
| Definitions and semantic model | Yours, built with us | Yours, per tenant | Yours, per tenant |
| Platform intellectual property | Ours | Ours, licensed to you | Ours, licensed to you |
| Configuration | You, or us under Managed Intelligence | You, for your tenants | You, through the licensed interfaces |
| Tier-one support to end users | Not applicable | You — they are your customers | You — they are your users |
| Platform support and escalation | Us, to you | Us, to you | Us, to you |
| Product updates | Continuous | Continuous, with notice for anything user-visible | Versioned interfaces, with a deprecation window |
| Security of the underlying platform | Us | Us | Us |
| Security of what you build on top | Not applicable | Shared — your identity model, our enforcement | Yours, above the licensed boundary |
| Commercial model | Subscription | Licence plus per-tenant fees | Licence plus usage, scoped to deployment |
What does not change
However it is branded or embedded, the governed path underneath is the same one.
Evidence travels with the answer
A white-labelled or embedded deployment does not get a cheaper version of traceability. If your customers see a number, they can see the query behind it. There is no tier that removes this, because an answer nobody can check is a different product rather than a discounted one.
Read-only stays read-only
There is no licensing arrangement in which a question becomes able to write to a system of record. It is enforced at the database role, so it is not something a licensee can configure their way past.
Scoping happens underneath
Access is resolved in Roots before a question is planned, so it cannot be undone by whatever interface sits on top. Your tenancy model maps onto that; it does not replace it.
Definitions stay singular
A metric agreed once applies per tenant without being maintained separately for each, which is what stops a white-label deployment turning into a hundred divergent forks of the same logic.
Where customization stops
Better said now than discovered in delivery. Every item here has cost somebody a difficult conversation at some point.
- The workspace can be restyled — identity, colour, typography, domain, wording. It is not a blank canvas, and a fundamentally different interaction model means the embedded route rather than white-label.
- The governed path is not configurable. Validation, read-only enforcement, scope resolution and evidence capture are not features that can be traded away for a lower price or a simpler integration.
- Programmatic access to the governed query path is available under an embedded agreement and scoped per deployment. It is not a public, self-serve API today.
- New connectors, new domain models and customer-specific workflows are scoped work, not licence inclusions.
- We do not currently support customer-managed hosting. Dedicated and private-network deployment is planned.
What a licensing agreement covers
Every arrangement here is negotiated rather than clicked through, because the questions that decide it — where the data lives, who is liable, what happens to your customers if either side walks away — do not have default answers.
- Deployment model, and the boundary between what you build and what you license
- Territory, exclusivity and permitted end-customer segments, if any
- Branding rights and any attribution requirements
- Tenancy, isolation and the identity model
- Which interfaces are licensed, at which versions, with what deprecation notice
- Data ownership, residency, retention and deletion on termination
- Security review, escalation paths and notification obligations
- Support boundaries: what you handle for your customers, what escalates to us
- Commercial model, minimums and how growth is priced
- Term, renewal, and what happens to your customers if either side walks away
Nothing on this page is legal advice or a binding commitment. It describes how we intend to structure these agreements so both sides can have a useful first conversation; the terms themselves go through counsel.
This one starts with a call.
Tell us which of the three models fits and roughly what scale you have in mind, and we will come back with terms rather than a brochure.