Tell us what you’re building.

Plain language is fine — better, in fact. We read every proposal ourselves. How this works →

Not ready to fill this in yet? Create an account and come back to it whenever you like — you can start a project from your dashboard at any time.

Project title *

Give your project a title.

In one sentence, what does it do? *

This is the line we read first, and the one that appears on your project page.

0 / 140

One sentence is enough — but we need it.

What are you building, and how? *

Tell us a little about the work.

What changes if this works? *

Be concrete. “Cuts triage time at 3 clinics from 20 minutes to 5” tells us more than “improves healthcare access”.

Who benefits, and how would you know it worked?

Field *

Pick the closest one.

Link (optional)

Where should we send your link back?

So you can finish this later, and so we can reply. This does not create an account.

We need an address we can reach you at.

What will it take to run?

If you already know your numbers, give them. If you don’t, describe the work and we will size it with you.

I have an estimate

You know roughly the hours and hardware.

I’m not sure yet

Describe the workload instead.

Total GPU-hours *

Across all GPUs, not per GPU.

Give a number, or choose “I’m not sure yet”.

How many GPUs at once? *

Most projects run on one.

Enter the hours and we’ll show how long that runs for.

GPU memory needed per job

Typical job length

Model and size

Frameworks

Describe the workload *

What you want to train or run, on how much data, and how many times. We will turn that into an estimate with you.

A few sentences is plenty.

Dataset size

Does it involve sensitive data? *

Please answer — it changes how we set the machine up.

How ready is it to run?

This tells us how much setup help you need — not whether you qualify.

Where is the project now? *

Pick the closest one.

When could you start? *

When could you begin?

Is your code in a container?

Docker or similar. If not, we help you package it.

Can training resume from a checkpoint?

Matters if a run is interrupted.

Do you have a reliable connection to upload data?

We can arrange another route if not.

Where does your training data live now?

Where should outputs be saved?

What will exist at the end?

Compute is donated on the understanding that something open comes back.

What you will deliver, and by when *

Add a line for each one. Models, datasets, papers, tools.

OutputExpected by

Add at least one output.

This list becomes your agreed outputs. We will not ask you to confirm it again.

Will the outputs be public?

If something must stay closed, tell us why below.

Licence

How others may use what you release.

Prior compute support or grants

Remaining compute budget

Data residency requirements

Anything else we should know

And finally, about you.

We use this to check the institution and to know who we are writing to.

Your name *

We need a name.

Role *

What is your role?

Institution *

Where are you based?

Country *

Which country?

Email *

From step 1 — change it here if it was wrong.

We need an address we can reach you at.

Does this look right?

Nothing is sent until you press the button at the bottom.

What happens after you send this

A person reads it — usually within a week.

If we take it forward, we set up your account and send you the login. You do not need to create one.

If we cannot, we say so plainly and tell you why.