Skip to content
Latchkey home
Documentation menu

Frequently asked questions

Quick answers about accounts, runners, self-healing, data, and billing.

In short

  1. Quick answers on accounts, runners, self-healing, data, and billing.
  2. Every answer here is covered in depth elsewhere in the docs and links onward.

Quick answers, grouped by topic, with links to the full pages where more detail exists. If you are debugging a specific problem rather than looking for an answer, start with the symptom list instead:

Accounts and setup#

Q.01Can I use Latchkey with a personal GitHub account?

Yes, for Latchkey CI: a personal account connects and runs it; add the repository from Settings, Code hosts, Enrol repositories, then commit a workflow file under .latchkey/workflows/ and push. Latchkey on GH (Latchkey's managed runners in GitHub Actions) needs a GitHub organization account. Creating a GitHub organization is free and takes a minute.

Q.02Do I need a credit card to try it?

No. Your first workspace automatically starts a 30-day free trial on the Launch tier, with no credit card and no plan picker at signup. Once you are subscribed, you can change plans any time from Billing, Change plan; there is one free trial per person.

Q.03Who becomes the workspace owner?

The person who installs the GitHub App. There is exactly one owner per workspace, and ownership can be handed to another member later with Transfer ownership. See Team and roles.

Q.04Can I use Latchkey with more than one GitHub organization?

Yes. Each installation gets its own workspace with its own plan, team, repositories, and data, and the workspace menu at the head of the sidebar moves between them.

Q.05Can I be in multiple workspaces?

Yes. If you belong to several workspaces, the workspace menu at the head of the sidebar moves between them; each workspace has its own plan, team, and data.

Q.06Do I have to select repositories during onboarding?

No. You can skip repository selection and add repositories later from Settings, Code hosts, Enrol repositories (owners and admins). See Managing repositories.

Q.07Can I use the dashboard on my phone?

Not yet: the dashboard needs a tablet, laptop or desktop screen, and a screen narrower than 768 px shows a notice after sign-in. Email, Slack, and push notifications cover you away from your desk.

Runners#

Q.01Do I have to change my workflows to use Latchkey?

Only the runs-on: line, and only for jobs you choose to move. Everything else stays as is, and GitHub-hosted runners keep working side by side.

Q.02What operating systems are available?

Ubuntu 24.04 LTS on x86_64. There are no Windows, macOS, arm64, or GPU runners today; keep those jobs on other runners and mix freely within a workflow.

Q.03Does Docker work?

Yes, natively: Docker CE with BuildKit, buildx, and compose are preinstalled, including QEMU for multi-arch image builds.

Q.04How fast do jobs start?

About two seconds when a warm runner is already online. A cold start takes longer, because a fresh machine has to boot first.

Q.05How long can a job run?

A Latchkey CI job can set timeout-minutes up to 180 (30 by default), a CLI job runs for up to 3 hours, and a Latchkey on GH runner for up to 4 hours from its start, or up to 8 when the job is still running at 4. Full limits in Limits and concurrency.

Q.06How many jobs can run at once?

Each plan sets it: Developer 20, Launch 40, Scale 80 busy runners per workspace, and a trial runs at the Launch number; Enterprise limits are set by contract. Idle warm and parked runners do not count, and jobs beyond the ceiling wait for a slot.

Q.07Can I keep files on the runner between jobs?

No. Runners are single-use: one job per machine, destroyed afterward, so anything written to local disk is gone when the job ends. Use artifacts or caches for persistence.

Q.08Where do runners run?

In AWS us-east-1, on Ubuntu 24.04 LTS x86_64 machines. See Limits and concurrency.

Q.09How are custom runners billed?

Custom-configuration runners bill at the xlarge rate ($0.0200/min), whatever their shape. See Custom runners.

Q.10How many custom runner configurations can I create?

2 on Developer and Launch, 10 on Scale, and unlimited on Enterprise. See Custom runners.

Q.11Can my AI coding agent see my CI failures?

Yes: connect it to the Latchkey MCP server with an API key and it can triage failures, pull failure bundles, and drive fixes from your editor. With the matching opt-in keys it can also re-run workflows and run one-off jobs on fresh Latchkey runners. See Connect your AI agent.

Self-healing#

Q.01Will self-healing change my code?

No. In-run fixes only touch the ephemeral runner, which is destroyed after the job. Durable fixes are only ever proposed as pull requests for your review, and nothing is auto-merged.

Q.02Can I turn self-healing off?

Yes: workspace-wide, in Settings under Self-healing or in the Self-heal section of the Runners page, which share one switch (owners and admins). There is no per-repository toggle today.

Q.03Will it mask real failures?

Not a failure that repeats: a test that fails on every try keeps its failure. Self-heal repairs known transient classes (network, memory, disk, missing tools, config drift), and it can re-run a step that failed, so a real failure that happens only sometimes can pass on the re-run. Every heal is recorded; on a Latchkey CI job, Open the heal shows the report.

Q.04How do I see what self-healing did?

The Runs page marks a healed run on Latchkey CI, or a healed job on Latchkey on GH, Healed beside its result. On a Latchkey CI job the healed step's record says what Latchkey did, and Open the heal shows the full report, with its category, verdict, and the action taken in plain language. The Self-heal outcome report on AI Insight counts the failures self-heal fixed in the last 30 days, and states the flaky re-runs that passed apart from them. On Latchkey on GH, list_heals and get_heal on the MCP server read the heal's record.

Q.05Can retries run up my bill?

No. Retries are bounded per step, the AI diagnosis stage has a hard time budget of about four minutes, and the job itself has a time limit: a Latchkey CI job can set timeout-minutes up to 180 (30 by default), a CLI job runs for up to 3 hours, and a Latchkey on GH runner for up to 4 hours from its start, or up to 8 when the job is still running at 4. Details in Self-healing.

Data and billing#

Q.01What does Latchkey read from GitHub?

Workflow run and job metadata and your workflow files, and for a repository you enable, its docs and CI config (indexed for the knowledge base) and its file layout (scanned to tell build configuration from application code, opening up to 11 files). When a step fails on a Latchkey runner, self-heal reads the step's output and can read the job's files. When a pull request runs on Latchkey CI, Latchkey also reads the list of files the pull request changes and keeps their paths for 90 days. Latchkey never calls GitHub's API for your secrets or variables. What each read is for, and what goes to an AI provider, is in Security and GitHub permissions.

Q.02What happens to my data if I disable a repository or cancel?

Disabling a repository stops ingestion, removes its knowledge base index and file layout scan, and keeps its GitHub Actions run records and AI history stored out of your dashboard. Canceling blocks access but retains your data so re-subscribing restores it. Deleting the workspace removes it permanently.

Q.03How is runner usage billed?

Per minute, rounded up per job, at per-size rates, after your plan's free minutes. See Runner usage and free minutes.

Q.04When do free minutes reset?

On the first of each calendar month. Minutes within the free tier cost nothing; only usage beyond it is billed at the per-minute rates.

Q.05Is there a spend cap on runner usage?

Not by default. An owner or admin can set a spend limit in US dollars for the calendar month on the Billing page. At the limit Latchkey refuses new jobs, holds queued ones and stops running ones, GitHub Actions jobs on Latchkey runners included; the limit resets with the month. Without one, a workspace with a subscription keeps running and the overage is metered to your invoice, with warnings at 80% and again at 100% of your included minutes. On a card-less trial, new managed-runner jobs are blocked once free minutes are exhausted, until you subscribe.

Q.06What happens if my payment fails?

The subscription goes Past Due: dashboard and API access are blocked and runner launches stop until the payment method is fixed in the Stripe portal. Your data is unaffected. See Managing your subscription.

Q.07Where do I find my invoices?

In the Stripe customer portal: open the Billing page and click Invoices & payment method. Invoices (with PDFs), payment methods, and subscription details are all managed there.

Q.08Can I change plans later?

Yes: Change plan on the Billing page upgrades or downgrades a subscription in place; during a card-less trial, choosing Developer, Launch or Scale under Plans and pressing Confirm opens Stripe Checkout, the paid plan starts when you finish, and the rest of the trial is not carried over. Downgrading below your monitored-repository count asks you to choose which repositories stay monitored, and downgrading to Developer requires the workspace to have only one member. The trial does not restart on a plan change.

Team and workspaces#

Q.01How many seats do plans include?

Launch includes 3 seats and Scale includes 5; extra seats are $5/month each. The Developer plan is for individual use, so team invites are unavailable there. See Team and roles.

Q.02Can I grant the Owner role by invite?

No. Invites grant Admin or Member. To hand over the workspace, the owner uses Transfer ownership.

Q.03How long do invites last?

You choose an expiry between 1 and 30 days (7 by default) and a maximum number of uses. Invites can be revoked any time from the Pending invites tab.

Security#

Q.01Can you complete our security questionnaire?

Yes. Send it through Support and we will work through it with you directly. Most questionnaires are already covered by Security architecture and Security and GitHub permissions, and vulnerability reports go to security@latchkey.dev.