Skip to main content
The dashboard is at app.airshipci.com, scoped to one GitHub organization. Organization owners can change things; members can read.

The pages

is anything wrong right now
Jobs and runners at a glance: queued, in progress, succeeded, failed, runner minutes, and the p50 and p90 time jobs spent waiting for a machine. Those last two are the health metric worth watching.
what is switched on
Activate and deactivate repositories, and allow public access where you mean to. Each row shows the airship.yaml Airship last read from the default branch, and whether it parsed.This page also has the config checker: paste a file, see whether it parses and what machines it would plan. Cheaper than a push.
credentials and their state
Connect AWS, Google Cloud and Azure, and see each credential’s account, its principal, when it was last verified, and whether it still works. A credential your cloud has started refusing shows here before you notice it in failed launches.
machines, live and historical
Every runner with its state, cloud, region, instance type, whether it is spot, whether it came from a pool, its instance ID and the job it took. The first place to look when a job is running but you want to know where.
what GitHub asked for, and what happened
Every job Airship was told about: its labels, the runner that served it, and — when none did — the reason why, in plain words. Troubleshooting covers each reason.
the activity log
Launches, launch failures with your cloud’s own message, configs that stopped parsing, clouds connected and rejected, caches that quietly degraded, runners lost. Start here when something did not work. Retained for 30 days.
usage over time
Jobs, runner minutes and queue waits per day and per repository. For cost, your cloud’s own bill is the authority — the machine tags make it per-repository without extra work.
tokens for automation
Create and revoke developer API tokens. A token is shown once, at creation. See the API reference.
who can see this
The organization members with dashboard access and the role each one holds. Roles come from GitHub and are re-checked hourly.
the ceiling
max_runners, the cap on live runners across every repository. See Capacity and limits.

Which page, when

Events worth recognising

cache.unavailable is the quiet one. A cache-enabled job that loses acceleration still passes — just slowly — so nothing fails and nobody notices until the bill or the clock does. It is worth watching.