Actions
Your GitHub Actions workflows, on a fresh machine for every run.
At a glance
- Workflows
- GitHub Actions syntax, as is
- Triggers
- Push, pull request, merge queue, manual, schedule, release, workflow run
- Runners
- Ephemeral Linux machines, pools, or your own
- Billing
- Per minute of job time
What it does
- GitHub Actions files, run as they are
- Actions from the marketplace,
strategy.matrix,actions/cache, artifacts, concurrency, variables, environments and OIDC work without changes. - A clean machine for every run
- Each run gets a new machine that is destroyed afterwards. Nothing leaks from one run into the next.
- Environments with reviewers
- Hold a deployment job until a reviewer approves it, or until a wait timer runs out.
- Runner pools and your own runners
- Keep a pool of warm runners of a size you choose, or register your own machines, including macOS, and route jobs to them by label.
- Secrets and short-lived credentials
- Give a job access to secrets from Secrets. Registry credentials are injected, scoped to the run and valid for hours, not months.
- Coming from GitLab
- Convert a GitLab CI file into a workflow with one command.
Command line
Follow a repository’s runs and read a job’s log.
$ dcloud ci runs list <repo>
$ dcloud ci jobs logs <job>
$ dcloud ci environments put <repo> production Price
As of 19 November 2026
| What | Price | Unit |
|---|---|---|
| Actions job time | €0.005 | per minute |
| Actions logs, artifacts and caches † | €0.00632 | per GB-month |
† Charged after notice: metered today and shown in the console with what it would cost. It appears on invoices from a date we announce in advance, never retroactively.