University of Southern Queensland in collaboration with
Invitation to pilot
University of Southern Queensland · Distributive

Massive-scale computing, powered by UniSQ

Run your research simulations, genomics pipelines, agricultural and climate models, astrophysics data analysis, AI batch inference, enterprise batch jobs, video transcoding, and parallel workloads of any kind

Securely distributed by DCP across UniSQ's idle computing infrastructure in Queensland. Free for UniSQ researchers, and a fraction of the price of traditional cloud for industry.

A university compute fabric

UniSQ runs the Distributive Compute Platform (DCP), built by Distributive, on computing infrastructure it already owns. Spare capacity that would otherwise sit idle becomes free research computing for UniSQ, and low-cost, Australian-hosted compute for organisations ready to leave the hyperscalers.

For UniSQ researchers

Free research computing on your own campus

Run simulations, models and analysis on UniSQ's own infrastructure at no cost to your project. Compute no longer has to come out of a grant budget, and your workloads run on university hardware.

Register your research workload →
For industry and government

Move your cloud workloads to UniSQ

Switch batch, analytics and AI workloads off the hyperscalers and onto UniSQ infrastructure in Queensland, at up to 4 to 50x lower cost. Your spend supports a regional university instead of a foreign data centre.

Express interest →

Up to 4 to 50x lower cost compute

For external organisations: same compute job, same results, for a fraction of the hyperscaler price. Your data stays private.

Parallel compute workloads

Data analytics, batch inference, fan-out workflows, modelling and simulation, optimisation, 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

  • Free for UniSQ researchers
  • No onboarding cost for external organisations
  • Evaluate ROI before committing
  • Pay-as-you-go thereafter, no lock-in
Your path to low-cost compute starts here

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. UniSQ researchers follow the same steps, at no cost.

1

Meet UniSQ and Distributive

You, Chris Davey (UniSQ) 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 UniSQ cluster works. 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

Your team to Distributive

Under NDA where needed, your team sends Distributive sample code, a representative data set and sample outputs for a compute workload you run today, whether on AWS, Azure, GCP, a lab workstation or an HPC queue. Distributive adapts it to run on DCP on the UniSQ cluster. Alternatively, Distributive can show your team 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 what you pay today.
  • dPrivacy and sovereignty. Where your data and compute actually ran.
3

Run it and get the results

Distributive and UniSQ

We run the adapted workload on the UniSQ 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 operationalise the DCP version of the workload for real: free for UniSQ research, and pay-as-you-go with no lock-in for external organisations. 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 compute spend supports a regional university

Up to 4 to 50xlower cost than hyperscalers, depending on the workload
Hyperscalers DCP at UniSQ
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 UniSQ infrastructure in Queensland
Platform ownership US-headquartered corporations Canadian platform, run on UniSQ's own hardware
Who benefits Offshore shareholders A regional Australian university
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 Australian-hosted compute, with no US hyperscaler in the loop

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

Tell us whether you are a UniSQ researcher or an external organisation, and we'll be in touch. You can also reach out to Chris and Dan directly by 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 UniSQ infrastructure runs the DCP Worker, which pools its spare CPU and GPU capacity and puts it at your fingertips through the DCP Compute API. UniSQ researchers use it free, organisations that switch from traditional cloud pay a fraction of the price, and that revenue supports the university.

–
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…