Depllo Docs

Depllo is GitLab-CI-style CI/CD for your GitHub repositories. Connect a repo, commit a .depllo-ci.yml, and every push runs on Depllo's own Docker runners — with live logs, artifacts, masked secrets, and a commit status posted back to GitHub. It's a drop-in replacement for GitHub Actions, priced flat per workspace.

What Depllo does

• Reads a GitLab-CI subset. Stages, a needs job DAG, rules, only/except, extends, YAML anchors, artifacts, cache, retry, timeout, and manual jobs — all from one .depllo-ci.yml.
• Runs jobs in Docker on Depllo's runners, each in an isolated container with a bind-mounted workspace and CPU/memory caps.
• Talks to GitHub over HMAC-verified push and pull-request webhooks, reports commit statuses under the depllo context, and serves a public SVG status badge.
• Keeps secrets safe. Per-project variables are AES-256-GCM encrypted and masked in log output.

Your code never leaves GitHub — Depllo connects through a webhook and clones over HTTPS to build.

How the docs are organized

• Getting started — connect a repo, add a config, and run your first pipeline.
• .depllo-ci.yml reference — every supported key, with examples.
• Predefined variables — the CI_* variables Depllo sets on every job.
• Runners — where jobs run and how runner tags work.
• Status badges — add a pipeline badge to your README.
• Migrating from GitHub Actions — convert your workflows with one command.
• API reference — the REST API.
• SDKs & CLI — the depllo CLI and the Node SDK.

The Forjio family

Depllo shares one identity layer (Huudis) and one billing spine (Plugipay) with the rest of the Forjio family. One account works everywhere — see the product switcher at the top of these docs.