in collaboration with
Invitation to pilot a new national computing capability
November to December 2026

Low-cost, massive scale sovereign computing

Run your enterprise batch jobs, big data analytics, AI batch inference, vector embedding pipelines, modelling and simulation, image processing, video transcoding, and parallel workloads of any kind

Securely distributed by DCP across Bell's idle compute infrastructure in Canada, for a fraction of the price of traditional cloud.

Express interest

Novel distributive compute fabric

Powered by the Distributive Compute Platform (DCP), built by Distributive, a Canadian technology company. It cuts compute costs, reduces reliance on foreign-controlled data centres, and supports Canada's push for digital sovereignty.

Up to 4 to 50x lower cost compute

Same compute job, same results, for a fraction of the hyperscaler price. Your data stays private and under sovereign control.

Parallel compute workloads

Data analytics, batch inference, fan-out workflows, modelling and simulation, optimization, video transcoding, image processing, federated learning, and more.

Independently security tested

The DCP Worker has been penetration tested by trusted external security firms. Security documentation is available under NDA.

What to know about this pilot

  • No onboarding cost
  • Evaluate ROI before committing
  • Pay-as-you-go thereafter
  • No lock-in
A new cloud-alternative computing platform for Canadians

What the pilot entails

Four steps, over a few weeks. You bring a real workload; we show you what it does on DCP, and you decide with the evidence in hand.

1

Meet Bell and Distributive

You, Iver Portillo (Bell) and Dan Desjardins (Distributive)

A working session with your technical and security people to answer whatever you need answered: cyber and data-privacy questions, how your data moves and where it lives, what the Canadian hosting looks like. We identify one or more suitable use cases, walk through the process below, and confirm next steps.

2

Send us a workload you already run in the cloud

Your team to Distributive

Under NDA, your team sends Distributive sample code, a representative data set and sample outputs for a compute workload you currently run on AWS, Azure or GCP. Distributive adapts it to run on DCP on the Bell-hosted cluster. Alternatively, Distributive can show your engineers how to adapt their own code. The pilot measures four things:

  • aExactness. Parity of results against your current cloud output.
  • bPerformance. Run time compared to your cloud setup.
  • cCost. What the same run costs on DCP versus your cloud bill.
  • dPrivacy and sovereignty. Where your data and compute actually ran.
3

Run it and get the results

Distributive and Bell

We run the adapted workload on the Bell cluster and return the measured outcomes on all four points, along with the adapted source code and documentation of what changed and how to use it. Everything is yours to keep.

4

Decide with the evidence in hand

You

If the ROI is there, you can operationalize the DCP version of the workload for real, on a pay-as-you-go basis with no lock-in. If it is not, you have lost nothing but a few hours of your team's time, and you have a hard number for what the alternative would cost.

Your money, data, and compute stay in Canada

Up to 4 to 50xlower cost than hyperscalers, depending on the workload
Hyperscalers DCP on Bell
Pricing model Reserve and rent capacity whether you use it or not Pay only for compute actually consumed
What you pay for Reserved instances, idle time, egress fees Computed results. Nothing else.
Cost visibility Billing surprises at month end Finite and bounded by the number of results
Data location Foreign-controlled data centres Bell-hosted infrastructure in Canada
Platform ownership US-headquartered corporations Canadian-owned and operated by Distributive
Data residency Data can leave the country Never leaves Canadian soil
Workload isolation Shared infrastructure, unclear tenant boundaries Isolated sandbox per job
Commitment Reserved instances, switching costs, lock-in Pay-as-you-go: buy credits, run workloads, stop anytime
Jurisdiction Subject to foreign law including the US CLOUD Act Canadian law, Canadian soil

The pilot runs your actual workload side by side on DCP and on your current cloud provider, so the comparison is on your numbers, not ours.

Express interest

Let us know your level of interest and we'll be in touch. You can also reach out to Iver and Dan directly via email.

What the workload does, roughly how it is built (language, frameworks, GPU or CPU), how often it runs and how big a typical run is. More detail is better.

I am interested in
Live

Live cluster

Otherwise idle or underused infrastructure runs the DCP Worker, which pools its spare CPU and GPU capacity and puts it at your fingertips through the DCP Compute API. Customers who switch from traditional cloud pay a fraction of the price, and hosts earn passive revenue from hardware they already run. Bell's cluster is currently CPU-only.

–
DCP Workers
 
–
CPU cores
 
–
Compute value
Yearly value of unlocked compute capacity
Name Worker ID Last active CPU cores Slices running Earnings Earning rate
Loading live data…