EXEA_RESERVE
Dashboard

Your compute queue.

Point us at a public repo, hand over a token so we can pull and push for you, then claim up to five slots. Your job runs 10:00–13:00 PST each day and picks up from its own checkpoint the next morning.

Book next slot →Log in
Before you can book
1 · Repo
neededA public GitHub repository we can clone.
2 · Token
neededUsername + PAT so the runner can pull and push unattended.
3 · exea.md
yours to writeAt the top of that repo. Template and guide →

Data source · …

Signed in
Guest (mock OK for demo)
Bookings
0 / 5
1 · GitHub repo
Must be public · must contain exea.md at the top level
2 · GitHub credentials

The runner clones and pushes without you present, so it needs a token. It is encrypted here and released only to the runner at 10:00 PST. It is never shown in this browser again and never written into your repository.

Fine-grained · your repo only · Contents: read and write
Making the token

GitHub → Settings → Developer settings → Personal access tokens → Fine-grained tokens → Generate new token. Under Repository access pick only the repo you are submitting. Under Permissions → Repository permissions set Contents: Read and write. Set an expiry past your last slot. Nothing else is needed.

My bookings
Not ready to book

Add a repository and your GitHub credentials above first — the runner cannot do anything with a job it cannot clone.

No bookings yet. Open the slot list and claim one.

Need help

Something broken you cannot fix from your repo? DM Avneh on Discord. Include your job id and the slot date — both are on this page.