◈ Education

Busy in term.
Quiet in summer.
Never paying for the gap.

Schools, universities and education companies run to an academic calendar: enrolment, assessment, results day, then a long quiet. Research groups need GPUs for weeks at a time and then nothing. Compute prices the same machines under the leading cloud and bills only for the seconds they run.

Used by schools, colleges, universities, edtech start-ups and Fortune 500 learning businesses for teaching, research and administration.

30%
Under the leading cloud on GPU hours
Per-second
Billing through term and holiday
Zero
Commitments or minimums
Free
Repositories for teaching

What this looks like in practice

◆Learning platforms and course delivery◆Enrolment, admissions and timetabling◆Assessment and results publication◆Research computing on GPUs◆Student coursework repositories and CI◆Tutoring and feedback with AI inference◆Library, archive and records systems◆Learning platforms and course delivery◆Enrolment, admissions and timetabling◆Assessment and results publication◆Research computing on GPUs◆Student coursework repositories and CI◆Tutoring and feedback with AI inference◆Library, archive and records systems
What holds true here

Four things you stop arguing about

◆

Research without the queue

H100, A100 and L40S instances started for a study and stopped after it, 30% under the leading cloud on-demand for the same GPU.

◇

Results day holds

Capacity rises for enrolment and results and falls back after, so the busiest day does not set the year’s bill.

◈

Student records kept properly

Records in managed databases with a full access and change history, separated where your policies require.

○

Teaching with real tools

Students get repositories, code review and CI on CodeGraph, with ten repositories and 100 GB free.

The shift

From budget cycles to the academic one

Education buys infrastructure annually and uses it seasonally. The gap between the two is money that could have gone to teaching or research.

The usual arrangement
  • ✕Capacity sized for results day and idle in summer
  • ✕Research groups waiting for a shared cluster
  • ✕Grant funding spent on reservations that went unused
  • ✕Coursework scattered across personal accounts
  • ✕Separate bills for every department
What replaces it
  • ✓Capacity that follows the academic calendar
  • ✓GPUs started for the study, billed by the second
  • ✓Grant spend that maps onto the work it paid for
  • ✓Coursework on one platform with review and CI
  • ✓One bill, itemised by department and project
What you can count on

Stated plainly, and qualified

30%
Under the leading cloud on GPU hours
H100, A100 and L40S, against the leading cloud on-demand
30%
Under the leading cloud’s model service
Tokens on the general model
Per-second
Billing
Summer costs what it uses
Free
Allowance
Ten repositories and 100 GB of repo storage
Closer in

Education, specifically

Grant money that goes on the research

A research group needs a few weeks of GPU time for an experiment, then writes up. Reserving capacity for a year to cover that is a poor use of a grant. On Compute the machines start for the experiment and stop after, priced under the leading cloud for the same GPU. That holds for a single lab and for a whole university.

Learning platforms from git

Course sites and portals deployed on Panel, with builds priced under the leading cloud’s hosting builds.

Tutoring by the token

Feedback and tutoring tools through AI inference, 30% under the leading cloud’s model service for the same model.

Coursework with CI

Student and staff repositories on CodeGraph, with code review built in.

Records in one place

Admissions, timetabling and results on CosmoBase, with a history of every change.

Against the leading cloud

Education on Compute, against the leading cloud

A100 GPU hour
$1.92/hr
Leading cloud $2.74/hr · Same GPU (A100 40 GB)
30% less
H100 GPU hour
$4.82/hr
Leading cloud $6.88/hr · Same GPU (H100 80 GB)
30% less
General & code model — input
$0.105 / million tokens
Leading cloud $0.15 / million tokens · The same open-weight model, input tokens
30% less
Build minutes
$0.007 / build minute
Leading cloud $0.01 / build minute · Managed hosting build minutes
30% less

Compared with the leading cloud's own published on-demand prices, US East. Every comparison.

Questions we are actually asked

Answers without the hedging

Can research groups pay from their own budgets?+

Usage is itemised by project, so each group’s spend can be charged to its own budget or grant.

How does this compare with the leading cloud for research?+

For the same H100, A100 or L40S, 30% under the leading cloud’s published on-demand price, shown beside ours. Billing is per second with no reservation required.

What about student data?+

Records are separated and access is recorded. Where data lives is configured and held to. If you need a specific attestation, ask us and we will answer plainly.

Is there anything free for teaching?+

Yes. Ten repositories and 100 GB of repository storage, two databases with 40 GB of storage, and 10 GB of object storage are included.

Other industries

Where else this goes

AI Agents

Run agents, the tools they call and the models behind them on one platform, billed by the token and the second, for less than the same work costs on the leading cloud.

Customer Acquisition

Host the landing pages, attribution pipelines and onboarding flows that bring customers in, and spend less on the infrastructure than you would on the leading cloud.

Marketing

Run campaign sites, personalisation, content pipelines and marketing data on one platform that costs less than the leading cloud for the same machines and models.

Lead Generation

Run the forms, enrichment jobs, scoring models and routing that turn interest into leads, for less than the same infrastructure costs on the leading cloud.

Sales

Run CRMs, sales data, call analysis and AI assistants on one platform, priced under the leading cloud for the same machines, databases and models.

Creator Economy

Host creator platforms, media processing, storefronts and AI tools on infrastructure that bills by the second and costs less than the leading cloud for the same machines.

Start where it matters most

Begin with one workload. Keep what you have running. Decide whether to continue once you have seen it carry something real.

No migration required to begin. Nothing to tear down if you stop.