AI Platform

Isolated jobs in a fresh microVM.

Run a container image as a one-off job, without deploying an app. Start it from the dashboard or the API, read the logs, done.

# define the job once: image, command, size, region
curl -X POST https://api.nodion.com/v2/runners \
  -H "Authorization: Bearer $NODION_TOKEN" \
  -H "X-Nodion-Project: $NODION_PROJECT" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "migrate",
    "image": "ghcr.io/acme/shop:v2",
    "run_command": "bin/rails db:migrate",
    "region_id": "reg_…",
    "timeout_seconds": 900
  }'

How it works

A job, not an app.

Define it once, run it as often as you need. Nothing keeps running between runs.

  1. DefineImage, command, size and region.
  2. StartFrom the dashboard, the API or your agent.
  3. RunA fresh microVM pulls the image and runs it.
  4. DoneLogs and exit code stay, the microVM is gone.

Built in

Safe to run anything.

A fresh microVM per run

Every run starts in its own short-lived microVM and is torn down when it ends. Nothing leaks between runs.

Isolated network

Runs are network-isolated from your other services by default.

Same sizes as apps

Pick a package for memory, CPU and disk, just like for an application process.

Timeouts up to 24 hours

One hour by default. Long builds and batch jobs can run up to 24 hours.

Logs and exit codes

Every run keeps its logs, status and exit code, in the dashboard and over the API.

Cancel any time

Stop a run that is stuck or no longer needed with one call.

Use cases

What teams run on runners.

Database migrations

Run the migration as its own job before or after a release.

CI steps

Tests, builds and checks in a clean environment every time.

Webhook jobs

Kick off work from a webhook without keeping a worker running.

Agent sandboxes

Give a coding agent a disposable place to run code and shell.

Need something that keeps running? Deploy an application

Give your agent a cloud.

Earn up to 15 € in credit when signing up.

Continue with GitHub

or with email