Partner Program | Dweve Revenue Share

Choose the audience that matches your question

The page contains three selectable readings of the same subject.

The Dweve managed service (via Fabric) runs within the contracted processing boundary on Dweve's public Mesh. Licensed customers operate the products directly on their chosen infrastructure, including isolated environments.

Privacy controls, retention, and erasure responsibilities are documented for the selected service, licence, and processing role.

Dweve operates the managed surface; licensed customers operate the licensed products directly. Keys, environments, and operating responsibilities are stated in the agreement.

Where the selected product and workflow support evidence capture and deterministic replay, customers can inspect how a result was produced.

Fourteen foundations are open source on github.com/dweve-ai under their published project licences. Commercial product source and modification rights are separate from those open foundations.

Supported evidence surfaces connect a result to the relevant rules, inputs, and decisions so the selected workflow can be reviewed.

The deployment boundary, operating rights, evidence surface, and open-source scope are documented before signature.

The data your customers trust you with stays in the jurisdiction you promised them.

The agreement makes clear who handles access, retention, and erasure requests for the selected deployment.

The agreement states the legal entity, processing boundary, operating party, and applicable jurisdiction.

Where deterministic replay applies, an auditor can inspect the recorded evidence instead of relying on an unsupported assertion.

Data-portability terms, the fourteen open foundations, and any separately licensed product rights are stated independently.

Supported evidence surfaces help explain a result through recorded inputs, rules, and decisions rather than model weights alone.

European partners, published shares by route

Rather than dress it up with logos we do not have, we are direct about being early. Every path starts with a conversation, not a contract.

Four partner routes, one actual-net-collected revenue basis, and explicit terms for every route. Here is the commercial programme on a single page.

Incentives aligned to keeping AI and data inside Europe, on terms procurement can sign.

Registered referral, technology, channel, and strategic. The opening share is 10%, 10%, 20%, and 30%.

Registered referral: 10% in year one only. Technology, channel, and strategic: higher share in years one to three, followed by the lower share while eligible.

Share follows the responsibility carried

Market development funding paid separately

A conversation first, then a written agreement

Both sides are named in one signed agreement

The first conversation is free and non binding.

The agreement names your route and your share.

Paid on the revenue Dweve actually collects.

14 open repositories on github.com/dweve-ai carry project specific licences, so the surface can be read before any commercial conversation.

Loom routes 528 domain specialists sparsely over the same hardware, at 96% less energy than a comparable GPU stack.

validated binary operations you can run on the hardware you already sell

Role-based training and certification is available at the published rate, or can be included explicitly in the partner agreement.

A managed demonstration environment for approved partner work, prepared around the agreed product surface.

A direct channel to Dweve engineers, with technical questions answered in writing.

Joint marketing and co-branded material can be proposed through a separately approved market-development budget.

Early. We are open to first partners across all categories and we are building the structure as we go. We are not going to show you a partner roster or logos we do not have. When there are partners worth naming, with their consent, they will appear here.

Technology partners can receive scoped technical enablement, a managed demonstration environment, and a direct support channel for approved partner work. Training, certification, response commitments, and market-development funding follow the published offer or signed agreement. Approved market funding is paid separately and is never deducted from partner share.

We work with European technology vendors, integrators, resellers, infrastructure operators, hardware providers, and research groups. The fit we care about is alignment with the platform and the sovereignty thesis, not the size of your logo.

Write to [email protected] for a registered referral, a technology, channel, or strategic path, or academic collaboration. Tell us what fits and what you want to build, sell, or study; we will document registration, responsibilities, and the revenue basis before attribution begins.

If your question is not here, write to [email protected] and we will answer in writing.

Government, critical-infrastructure, GCI

Every contract starts with a conversation, not a paper.

However you meet us, you are using the same software, and the arrangement behind it is written down before anyone is paid anything.

A larger organisation agrees a longer piece of work with us and brings their own teams.

A local supplier sells the software, sets it up and answers your questions.

A company puts our software inside their own product, so you may never see our name.

Someone who already helps you with computers mentions Dweve and introduces you.

An accepted, registered customer introduction

actual collected revenue, after discounts

Registered referrals earn 10% in year one with no tail. Technology, channel, and strategic shares are 10%, 20%, and 30% in years one to three, then 5%, 10%, and 15%. Partner services remain partner revenue.

Market-development funding is separately approved and paid by Dweve, not taken from the partner share.

The opening share tracks the responsibility carried, from a registered introduction to government, critical-infrastructure, and GCI programmes.

Opening revenue share by route: registered referral 10 percent, technology 10 percent, channel 20 percent, strategic 30 percent.

Government consultancies, enterprise strategic access

System integrators, consultancies, regional distributors

Hardware, infrastructure, and toolchain integration

Share is calculated on Dweve's actual net collected software revenue after customer discounts, refunds, indirect taxes, credits, and pass-through charges, never on list or pre-discount value.

At five years that is EUR 800K: 20% in years one to three, followed by a 10% continuing share in years four and five.

Accumulated channel share, this customer

One customer, EUR 1M a year of actual collected Dweve software revenue.

You are incentivised for retention, not just acquisition. Help customers succeed, and you both win. There is no closing a deal and moving on, because the relationship is where the value lives.

Build a portfolio of customers generating recurring revenue. Know your income 12 months ahead. The work transforms from deal-hunting into portfolio management.

Build a portfolio, not a pipeline of one-offs.

EUR 1M of collected software revenue generates EUR 200K a year for a channel partner in years one to three and EUR 100K a year thereafter, subject to registration and continuing eligibility.

Lab cycles contributed to the federated mesh.

Joint work on binary constraint discovery.

Open projects and specifically agreed research code.

Named products and experiments in the research agreement.

Credits can be agreed for accepted compute contributions.

A written research agreement defines access, accepted compute, credits, publication, IP, and confidentiality.

Advisers, specialists, customers, and independent professionals making a qualified introduction that Dweve accepts and registers.

Confirm the customer, need, and buying context before registration

Register the accepted opportunity before commercial work begins

Receive 10% of eligible net-collected software revenue in year one, with no tail

Every path starts with an accepted registration and a signed partner agreement.

Position sovereign AI for critical infrastructure

Navigate public sector procurement frameworks

Introduce Dweve to government decision-makers

Government and critical-infrastructure advisers supporting eligible programmes. Strategic partners with senior access and continuing programme responsibility.

Implement on-premise deployments and integrations

Sell eligible Dweve licences to organisational customers

System integrators and consultancies selling, implementing, and supporting Dweve for organisations. Regional distributors with deep vertical knowledge.

Build DevOps toolchains and deployment automation

Integrate Dweve with supported infrastructure and platform products

Validate binary operations on specific hardware

Hardware vendors and platform integrators maintaining a supported product, hardware, or toolchain integration for Dweve CPU and FPGA infrastructure.

None of these are extras you pay for. They are simply how it works.

It is honest about what it does and does not know.

Like a builder who tells you a job will take longer, instead of promising the moon.