Quickstart: zero to dashboard

Sign in with GitHub

Go to latchkey.dev/sign-in and sign in with your GitHub account. Use the GitHub account that has access to the organization you want to monitor: the app install in the next step happens under this identity, and the person who installs the app becomes the workspace owner. You land on the dashboard's Get started card ("Welcome to Latchkey"), and your 30-day trial is already running, no credit card required. If you get interrupted at any point, just sign in again; setup resumes where you left off.

Connect GitHub

Step 1 on the Get started card is Connect GitHub. Click it and Latchkey sends you to GitHub to install the app (a short interstitial explains what happens first). When GitHub asks where to install, choose your organization (not your personal account). You need owner or admin permissions on the organization; if you have neither, ask an organization owner to install the app or grant you admin rights. What the app can and cannot access is covered in Install the GitHub App.

Select repositories to monitor

Step 2 on the Get started card, Select repositories, opens the repository picker, which lists your organization repositories with search and a visibility filter. Select the ones you want Latchkey to monitor; the counter shows how many your plan allows (10 on Launch, where every new workspace starts; 1 on Developer and 40 on Scale if you change plans later). Two things worth knowing while you choose: managed runners only serve monitored repositories, so include any repo you plan to point at latchkey-* labels; and the "Skip for now, explore the dashboard first" link lets you defer this and add repositories later from the dashboard. Guidance on choosing under a plan limit is in Managing repositories.

Watch the dashboard fill in

After setup, a short guided tour of the dashboard is offered; you can skip it at any point. For each repository you enabled, Latchkey backfills recent completed workflow runs from the last 30 days, so most teams see data within a few minutes; a progress banner shows while backfill runs. If a page looks empty, check the filter bar at the top first: analytics pages show data for the repositories you select and prompt you to pick one if nothing is selected.

Optional: run a job on a Latchkey runner

Change one line in any workflow to try a managed self-healing runner. After you push, the job shows as queued on GitHub until a runner picks it up: seconds when a warm runner is available, about 10 seconds when a fresh runner cold-starts for you. The full walkthrough, including how to verify where the job ran, is in Run your first job.

jobs:
  build:
    runs-on: latchkey-small
    steps:
      - uses: actions/checkout@v4
      - run: npm ci && npm test

Optional: invite your team

On every plan except Developer, open Team in the dashboard sidebar to invite teammates by email or shareable link (the Developer plan is for individual use, so invites are unavailable there). Invites grant the Admin or Member role. See Team and roles.