Deal economics
Capacity, not seats
Licensing scales with data volume rather than users, so expansion does not run into a per-seat approval every time. Enterprise deals are private offers with negotiated terms.
Partners
Sell the answer to the question that keeps stopping your AI deals.
If you already sell infrastructure, security or AI into regulated accounts, you have met the data-residency wall. K-Lake is what you take back to those accounts.
Why partner
Margin on the deal, and on the work around it
Marketplace
Azure Marketplace and MACC
Transactions run through the Azure Marketplace, count toward the customer's committed Azure spend, and are co-sell eligible. Budget that already exists, with an expiry date.
Services
The work is yours
Deployment, connector onboarding, entity discovery engagements, custom schema configuration and managed evidence packs. The product opens the door; the services follow.
Programme
Three ways to work with us
Referral
Lowest commitment
- Introduce an opportunity, we run it
- Referral fee on closed business
- No technical certification required
- Deal registration protects the introduction
Reseller
Most common
- You own the customer relationship and the contract
- Partner pricing set in your reseller agreement
- Sales and technical enablement
- Access to the ICP guide, use-case briefs and demo environment
- Co-sell support on qualifying deals
Delivery
Services-led
- You deploy and support customer environments
- Technical certification and deployment training
- Named escalation path into Zegress support
- Suited to partners with existing managed services
Partner pricing, referral rates and deal-registration terms are set in your agreement rather than published here. Ask us for the partner pack.
How it works
From first conversation to first deal
01
Talk to us
A short call to check fit both ways: your accounts, your existing practice, and whether the regulated-sector pain you are seeing matches what we solve.
02
Agreement and enablement
Partner agreement, then the enablement pack: ideal customer profile, qualification scorecard, objection handling, use-case briefs and pricing.
03
Register the deal
Register opportunities before first technical engagement. Registration protects your position and triggers our support on the deal.
04
Prove it
A proof-of-concept on the customer's own infrastructure, using their documents. This is the strongest conversion lever the product has, and we support you through it.
05
Transact and expand
Close through the Azure Marketplace, apply the customer's committed spend, then expand from the first department into the wider estate.
Talk to us about partnering Or email [email protected] See the use cases
Alliances and marketplaces
Where you can already transact, and where next
K-Lake is bought through cloud marketplaces so the spend draws down against commitments the customer has already made.
Alliance
MicrosoftPartner
Microsoft Partner and Azure Marketplace
Transactable today. One Azure bill, counts toward the customer’s Azure Consumption Commitment, co-sell eligible, and private offers for enterprise deals.
Marketplace
Google CloudMarketplace · listing in progress
Google Cloud Marketplace, next
The Google Cloud listing is in progress, with AWS Marketplace to follow. No dates published; ask us if a customer is committed to either.
Partner questions
What partners ask first
Does this compete with the Microsoft assistant our customer already has?
No — it sits underneath it. Assistants answer well on data already inside the productivity suite; they cannot see the file shares, NAS and object storage where most regulated document estates actually sit, unless that data is migrated first. K-Lake connects those in place and feeds the assistant the customer already licenses. Their existing investment gets more useful, not replaced.
Is this a one-time deployment, or can we run it as a managed service?
Both are supported. Deployment is light by design — a single-command proof of concept, or one click from the Marketplace, into the customer’s own environment, where it stays. Partners can operate it on the customer’s behalf on a partner-of-record basis: you contract with the customer, bill them, hold the relationship and provide first-line support, with Zegress behind you on second and third line.
Is the route to market Marketplace-only, or is there a channel?
Marketplace is the transaction rail, not the strategy. The offer is co-sell eligible and counts toward the customer’s committed Azure spend, which matters for joint motions with infrastructure vendors. Two-tier distribution is the intended channel alongside it.
Is pricing consumption-based, or can we transact a SKU?
Both. Consumption is list pricing for Marketplace and direct. Annual prepaid capacity SKUs in fixed blocks are available for channel and distribution — easier for distribution systems to carry and easier to wrap services around. Same product, different packaging. Partner rates and deal-registration terms are set in your agreement.
Who is the ideal partner for this?
Three types. Storage-led infrastructure resellers with an installed base of unstructured data in regulated accounts. Microsoft partners running a Copilot practice, who are already meeting the “it can’t see our file shares” problem. And MSPs with a managed infrastructure practice. The attach point in all three is storage you have already sold or already manage.