in collaboration with
Run 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
on idle computers and SMART displays in Canadian schools. Up to 5x less than the cloud, with the revenue shared with those schools.
Canadian governments and enterprises can redirect what they would otherwise pay a hyperscaler into revenue for schools in their community, while cutting compute costs, keeping data under sovereign control and reducing reliance on foreign-controlled data centres. SMART Distributed Compute is powered by the Distributive Compute Platform (DCP), a Canadian technology.
Move batch, analytics and AI workloads off the hyperscalers and onto idle computers and SMART displays in Canadian schools, at up to 3 to 5x lower cost. Your spend stays in Canada and becomes revenue for schools.
Express interest → For school boardsSchool computers and SMART displays sit idle up to 16 hours a day. With SMART Distributed Compute they process government and enterprise workloads after hours, securely and with no impact on teaching, and your schools receive a share of the revenue from equipment they already own.
Express interest →Same compute job, same results, for a fraction of the hyperscaler price. Data stays private and under sovereign control.
Each compute dollar pays for results and funds schools at the same time. Organizations buy compute credits, and the schools whose computers and displays run the work receive a share of that revenue.
Every job runs in an isolated sandbox and sees only its own task. Workloads can't access anything on the device: no student data, files or school network resources. Work is split into small pieces so no single device sees the full workload, and only vetted, approved organizations can submit jobs. The DCP Worker has been penetration tested by trusted external security firms.
Five steps, alongside the organizations bringing workloads. Your board supplies idle compute, helps bring customers to it, and shares in the revenue.
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.
You, Sheena Dixon (SMART) 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, and how the school network works. We identify one or more suitable use cases, walk through the process below, and confirm next steps.
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 with a hyperscaler. Distributive adapts it to run on DCP across the SMART school network. Alternatively, Distributive can show your engineers how to adapt their own code. The pilot measures four things:
Distributive and SMART
We run the adapted workload on the SMART school network 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.
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 team, Sheena Dixon (SMART) and Dan Desjardins (Distributive)
A working session with your board's IT, finance and leadership to answer whatever you need answered: security and privacy, how the DCP Worker runs on your devices, and how revenue sharing works. We confirm the scope of your participation and next steps.
Your board, SMART and Distributive
A short agreement that sets out how workloads run on your devices, what the DCP Worker handles, and how revenue is shared during the pilot.
Your IT team, with SMART and Distributive
SMART and Distributive meet with your IT team to plan the rollout and answer security questions. Your IT team then picks the computers and SMART displays to include and deploys the DCP Worker software. It is throttled to compute after school hours, so classes are unaffected.
Your board, with SMART and Distributive
More workloads mean more revenue for your schools. Help bring government and enterprise customers to the network through your networks, government relations and lobbying contacts, social media and press releases.
Your board, SMART and Distributive
Use what the pilot shows to help define how the program runs formally after the pilot: operations, support and revenue sharing at scale.
Only a few hours of your team's time. The pilot runs one of your own workloads on DCP and measures the true ROI, so you know what switching is worth before committing to anything.
Up to about 5x, depending on which cloud services the workload replaces. Replacing raw compute saves less than replacing compute bundled with a managed service, such as a cloud media transcoding service. The pilot measures the actual savings on your own workload.
Under NDA, sample code, a representative data set and sample outputs for a workload you already run in the cloud. Distributive adapts it to run on DCP, or shows your engineers how to do it themselves.
Very little. Distributive adapts the workload during the pilot and you keep the adapted code and documentation. After that it's pay-as-you-go with compute credits: no reserved capacity, no lock-in, and you can stop anytime.
No. Only vetted school boards host workers, and they act as data subprocessors under contract, with obligations and access controls that bar them from accessing your data. It's the same model every cloud provider uses: only a machine's host administrators have the technical ability to see what runs on it, and they are contractually bound not to. On top of that, every job runs in an isolated sandbox, work is split into small pieces so no single device sees the full workload, and the DCP Worker has been penetration tested by trusted external security firms.
Yes. Workloads run on computers and SMART displays in Canadian schools, operated by Canadian companies under Canadian law, and the data never leaves Canadian soil.
It depends on what the workload needs. Overnight and opportunistic capacity costs the least, which makes it ideal for enterprise batch jobs, data analytics, scientific computing and other latency-tolerant work. For latency-sensitive workloads that need guaranteed real-time availability, workers can run on dedicated machines.
Only marginally. The DCP Worker is throttled and does its compute after school hours, so the added power draw is small.
No. Compute runs after school hours, and its effect on the school network is marginal.
No. Every job runs in an isolated sandbox and can't access anything on the device: no student data, files or school network resources. Only vetted, approved organizations can submit work.
Your IT team selects the machines and deploys the DCP Worker, with support from SMART and Distributive throughout the pilot.
A pilot data processor agreement with SMART and Distributive, covering how workloads run on your devices and how revenue is shared.
It depends on the workloads run, how efficient the device is and how many hours it is available, so we don't quote a figure before the pilot produces real data. Measuring it is one of the things the pilot is for.
Money, data, and compute stay in Canada
Creating a SMART compute economy
Governments and enterprises save. Schools earn. Every dollar, byte and FLOP stays in Canada.
| Hyperscalers | DCP with SMART | |
|---|---|---|
| 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 | Computers and SMART displays in Canadian schools |
| Where the money goes | US-headquartered corporations | Canadian schools, through a revenue share, and Canadian technology companies |
| 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 compute 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.
Let us know your level of interest and we'll be in touch. You can also reach out to Sheena and Dan directly via email.
Where organizations and school boards manage compute credits, jobs, workers and keys.
Open the PortalOtherwise idle computers and SMART displays in classrooms run the DCP Worker, which pools their spare CPU and GPU capacity and puts it at your fingertips through the DCP Compute API. Organizations that switch from traditional cloud pay a fraction of the price, and schools earn passive revenue from equipment they already own.
| Name | Worker ID | Last active | CPU cores | Slices running | Earnings | Earning rate | ||
|---|---|---|---|---|---|---|---|---|
| Loading live data… | ||||||||
