Your data stays yours.
Canopy runs every client on a private, single-tenant instance with its own database. API keys for a client's tools live only in that instance, and each workspace gets only the CRM access it needs. Every send is logged with the person who approved it, every automated CRM change can be reverted, and your CRM stays the system of record.
One client, one instance.
Canopy is single-tenant by design. Nothing about your accounts, your messages or your results is pooled with anyone else's.
Private instance
Every client runs on its own deployment and its own database. There is no shared tenant to leak across.
Isolated credentials
API keys for your tools live only in your instance, are never stored in code or documents, and are never in scope while we work for anyone else.
Least privilege
Each workspace is granted only the CRM and tool access it needs. Read and write scopes are agreed in the workshop.
Every action on the record.
You can always answer who sent what, why, and what they saw before they approved it.
- Every send logged with the approver and the exact preview they saw
- Every automated CRM change logged, with a revert
- Every brief and playbook change versioned, with who approved it
- Pause any workspace instantly
Canopy is a system of intelligence, not a new system of record.
Your customer data lives where it lives today. Canopy reads what agents need, keeps working state in your private instance, and writes every outcome back to your CRM, so the record your team trusts stays complete.
How we operate.
Founder-led access
Access to client instances is limited to the GTM Engineers on your deployment.
Secrets never in context
Our internal tooling blocks credentials from ever appearing in logs, documents or model context.
Consent respected
Lifecycle sends through your existing sender, so opt-outs and suppression lists apply automatically.
Clean offboarding
On exit, your instance and its data are deleted on your instruction, and your CRM keeps every record.
Running a vendor review?
We'll share our data-handling note and walk your security team through the architecture on a call.
From connection to deletion.
Scoped access
Your CRM and tools are connected with only the access each workspace needs.
In your instance
Agents work inside your private instance, and results are written back to your CRM.
On the record
Every send, change and approval is logged with who did it and what they saw.
On your instruction
At the end of an engagement, your instance and its data are deleted when you say so.
How we use AI models.
Agents use leading models through business APIs. Those providers do not use your data to train their models.
- Every output cites the facts it used, so claims can be checked
- Prompts and briefs are versioned and reviewed by your GTM Engineer
- Customer-facing messages follow your send settings
Train models on your data
Pool your data with other clients
Sell or share your data for anyone else's use
Put credentials in code, documents or chat
Security questions.
Anything else, contact us.
Is Canopy single-tenant?
Yes. Every client runs on a private instance with its own database, so there is no shared tenant to leak across. Nothing about your accounts, messages or results is pooled with any other client, and there is no shared model.
Are you SOC 2 certified?
Not yet. We will share our data-handling note and walk your security team through the architecture on a call.
Where is our data stored?
In your own private instance, plus your existing CRM and tools. Nothing is pooled with other clients.
Who at Canopy can access our instance?
Only the GTM Engineers on your deployment.
What happens if we leave?
Your instance and its data are deleted on your instruction, and your CRM keeps every record agents wrote.
Can we review the agents' actions?
Yes. The audit log records every send, change and approval, and can be exported.
Do agents train a shared model on our data?
No. There is no shared model and no pooled data, and Canopy never trains models on your data. Agents use leading models through business APIs, and those providers do not use your data to train their models.
How are API keys and credentials stored?
API keys for your tools live only in your private instance and are never stored in code or documents. They are never in scope while we work for another client, and our internal tooling blocks credentials from appearing in logs, documents or model context.
How does Canopy support a vendor security review?
We share our data-handling note and walk your security team through the architecture on a call before kickoff. Most teams start with Outbound, which needs the lightest integration, while the review runs.
Does Canopy become a new system of record?
No. Your customer data lives where it lives today. Canopy reads what agents need, keeps working state in your private instance and writes every outcome back to your CRM, so the record your team trusts stays complete.
How does Canopy handle consent and opt-outs?
Lifecycle sends through your existing sender, so opt-outs and suppression lists apply automatically. Unsubscribes apply to every journey and campaign, and frequency caps keep a contact in several journeys from hearing from you too often.
Apply to become a launch partner.
We're onboarding a small group of revenue teams ahead of general availability. Launch partners get founder-led deployment, launch pricing in writing, and a direct line into what we build next.
- Founder-led deployment
- Launch pricing, in writing
- A say in the roadmap