White label, contracting and licensing
Yours, next
The same platform, arranged three different ways. Which one applies depends on whether you want DeepGarden for your business, for your customers, or underneath something you are already building.
You are not on the list above
Your industry, next
A domain we have not built is an onboarding, not a rebuild. Domain knowledge lives in configuration, so a new vertical does not wait on a product release.
- We build the vocabulary, metrics, entities and guardrails with your team
- Your definitions are certified in Studio and owned by you
- Delivery measured in weeks, not release cycles
- The package becomes yours to extend
Your brand, our platform
White label
Deploy DeepGarden to your own customers under your own name, with your branding, your domain and your commercial relationship.
- Your brand, colours and domain throughout the product
- Per-tenant provisioning for your customers
- Usage reporting suitable for reselling
- We stay invisible; you own the customer
Embedded or OEM
Platform licensing
License the governed query path to sit underneath something you are already building, where DeepGarden is the engine rather than the interface.
- Governed question execution behind your own interface
- Roots as the semantic and permissions layer for your data
- Evidence preserved end to end, so your product inherits the audit trail
- Commercial terms scoped to your deployment model
What a contract covers
Every arrangement here is negotiated rather than clicked through, because the questions that decide it — where the data lives, who is liable, how long the audit trail is kept — do not have default answers.
- Contracting, licensing and commercial terms
- Deployment model, including private networking or dedicated infrastructure
- Security review, access model and audit retention
- Domain configuration and certified definitions
- Onboarding and training for your team or your customers
- Ongoing account management
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 deployment does not get a cheaper version of traceability. If your customers see a number, they can see the query behind it.
Read-only stays
There is no licensing arrangement in which a question becomes able to write to a system of record.
Access is enforced underneath
Scoping happens in Roots before a question is planned, so it cannot be undone by whatever sits on top.
This one starts with a call.
Tell us which of the three arrangements fits and roughly what scale you have in mind, and we will come back with terms rather than a brochure.