Background
Latchkey
Effective Date:July 2, 2026

Terms of Service

Please read these terms carefully before using the Latchkey AI-powered CI/CD monitoring and optimization services.

TL;DR: Key Terms

  • We're in Open Beta — the Service, including managed runners and self-healing, is provided "as is" with no guarantees
  • AI features (insights, self-healing, AI Scan runners) operate within bounded actions; you're responsible for reviewing and testing any change
  • We retain IP rights to our platform; you retain rights to your code and data. Runner execution is ephemeral — your source code is not persisted on Latchkey infrastructure

By accessing or using the website located at https://www.latchkey.dev/ (the "Site") and the AI-powered CI/CD monitoring and optimization services provided by Latchkey, you agree to be bound by these Terms of Service.

If you do not agree to these Terms, do not use the Service.

Last Updated: May 18, 2026
Questions: legal@latchkey.dev

Latchkey provides an analytics, runner, and optimization platform designed for engineering teams. Our Service integrates with GitHub Actions to provide predictive insights, cost visibility, and performance optimization recommendations, and offers managed ephemeral GitHub Actions runners with AI-driven self-healing of failing build steps.

✓ Performance Analytics✓ Cost Optimization✓ AI-Powered Insights✓ Managed Runners✓ Self-Healing✓ AI Scan Runners

Latchkey Runners are managed, ephemeral GitHub Actions runners offered as part of the Service. You adopt a runner by setting the corresponding runs-on label (for example, latchkey-medium) in your workflow YAML. Latchkey provides four preset sizes (small, medium, large, extra-large) and AI Scan Runners that generate a runner configuration tailored to your repository.

Execution Environment

When a job is dispatched to a Latchkey Runner, your code is checked out into a fresh, isolated runner instance provisioned by Latchkey. The runner is destroyed at the end of the job, and no data, artifacts, or state persist between jobs. Latchkey does not store, retain, or use your source code beyond what is required to execute that single job.

AI Scan Runners

AI Scan Runners analyze a monitored repository to detect languages, build tools, package managers, and CI configuration, and return a suggested runner configuration with a confidence score. The scan is a recommendation. You decide whether to approve, modify, or discard the generated configuration before any job is routed to it.

Your Responsibilities

You are responsible for the workloads you run on Latchkey Runners, including the code, dependencies, secrets, and third-party actions you choose to execute. You agree not to use Latchkey Runners for any purpose prohibited by these Terms (see "Prohibited Uses") or by GitHub's terms of service.

Latchkey Runners are fully compatible with existing GitHub Actions workflows. Standard GitHub Actions concepts (caching, artifacts, marketplace actions, secrets) continue to apply.

Self-healing is a capability of Latchkey Runners. When a workflow step fails, Latchkey detects the failure, diagnoses its cause, and applies a fix within a bounded action set so the build can keep moving. Self-healing targets transient and environmental failures — network errors, out-of-memory kills, disk-full errors, missing tools, and predictable configuration mismatches — and explicitly does not heal user-code bugs such as segfaults or deterministic crashes.

Default Behavior and Controls

Self-healing is enabled by default for every Latchkey organization. Owners and admins can disable self-healing at any time under Settings → Self-Healing Runners. Other members can view the setting but not modify it.

Bounded Agent Actions

When the self-healing agent engages, it operates on a tightly scoped view of the failing step — stderr, stdout, exit code, and a curated set of manifest files (e.g., package.json, requirements.txt, Cargo.toml). The agent does not have access to your source code. Its available actions are limited to a vetted allowlist; it cannot run arbitrary commands, modify your code, or persist anything outside the build environment.

No Guarantee

Self-healing operates on a best-effort basis. We do not guarantee that any given failure will be successfully diagnosed or remediated, and you remain responsible for reviewing your build outcomes. Additional time consumed by self-healing is billed at the standard per-minute rate of the runner the failing step is using.

Please Note: The Service is currently in an "Open Beta" or "Early Access" phase.

Beta Terms

  • As-Is Status: The Beta Service is provided "as is" and "as available," and may contain bugs, errors, or other defects.
  • Data Integrity: We do not guarantee that your data will be preserved without corruption or loss during the Beta phase.
  • Feedback: You agree that we may use any feedback, suggestions, or ideas you provide without any obligation or compensation to you.

Registration

To use Latchkey, you must register for an account and integrate the Service with your CI/CD provider (e.g., via GitHub OAuth).

Permissions

You grant Latchkey the necessary permissions to access, read, and analyze your CI/CD pipeline data, workflow YAML files, and runner telemetry solely for providing the Service. Permissions are scoped to the minimum required for the features you use.

Pull Request Creation

The Latchkey GitHub App has write access to the repositories you choose to monitor for the limited purpose of creating pull requests on your behalf when you explicitly request one (for example, by clicking "Create PR" on an optimization insight). Latchkey will not push commits, merge code, or modify your repositories without your explicit, per-action consent. You review and merge any pull request Latchkey creates.

Runner Workloads

If you use Latchkey Runners, you direct your workflow jobs to Latchkey's infrastructure by setting the corresponding runs-on label in your workflow YAML. You remain solely responsible for the workloads you execute on Latchkey Runners and for ensuring those workloads comply with these Terms, GitHub's terms, and all applicable law.

Security

You are responsible for maintaining the confidentiality of your account credentials and for safeguarding any secrets, tokens, or credentials you provide to Latchkey Runners through GitHub Actions.

Latchkey offers tiered subscription plans sized by the number of monitored repositories you analyze and the number of seats included on the plan. Latchkey Runner usage is metered separately on a per-minute basis, with a pool of free runner minutes included with every plan.

Automated Billing Transition

Your first 30 days are free. Unless you cancel before the trial ends, your subscription will automatically transition to your selected paid tier, and your payment method on file with Stripe will be charged. No additional confirmation emails will be sent prior to this initial charge.

Billing Terms

  • Subscription tiers are sized by the number of monitored repositories included in your plan.
  • Per-seat fees apply based on your selected plan. Each plan includes a baseline seat count, and additional seats can be purchased at the current per-seat rate.
  • Latchkey Runner usage is metered separately on a per-minute basis. Each plan includes a pool of free runner minutes per billing period, and usage beyond the included pool is billed at the published per-minute rate for the runner size in use.
  • After the 30-day free trial, the card provided during onboarding is charged automatically.
  • You can cancel at any time via your account dashboard to prevent future charges.
  • No refunds are provided for partial billing periods.

Payment Processing

All payments are securely processed through Stripe. We do not store your credit card information on our servers.

Our Service uses AI in several places, including optimization recommendations surfaced on the dashboard, AI Scan runner configurations, and self-healing diagnoses and remediations applied to failing build steps.

No Guarantee

AI models can make mistakes. We do not guarantee specific results from following our recommendations, from any AI Scan runner configuration, or from any self-healing action. You are responsible for reviewing changes Latchkey proposes and for verifying that any healed build behaves correctly. Where AI actions involve cost (for example, self-healing minutes), those costs are billed at the standard per-minute rate of the runner in use.

Our Rights

Latchkey retains all rights to the Service, including our AI models, algorithms, and underlying code.

Your Data

You retain ownership of your data. You grant us a limited license to use it to provide the Service, including the generation of account-specific insights.

AI and Machine Learning

To improve Latchkey for all users, we may use anonymized metadata (such as job durations and failure patterns) for model training, provided such data cannot be traced back to you or your workspace. We do not use your proprietary logs or source code to train global, multi-tenant AI models.

Opt-Out

Latchkey may use aggregated, non-identifiable data to improve its predictive models. Users on Scale or Enterprise tiers may request to opt-out of global model training by contacting legal@latchkey.dev.

Latchkey publishes educational and comparative content, including guides, glossaries, and product comparisons in our Learn hub, that may reference third-party products, services, and companies.

Third-Party Trademarks

All third-party names, logos, product names, and trademarks referenced in our content are the property of their respective owners. Any such reference is for identification, commentary, and comparison purposes only and constitutes nominative fair use. It does not imply any affiliation with, sponsorship by, or endorsement by the trademark owner, and does not imply that Latchkey is endorsed by or affiliated with those owners.

Basis of Comparisons

Comparative statements are made in good faith and are based on information Latchkey believes to be accurate at the time of publication, drawn from publicly available sources such as each third party's own documentation, pricing pages, and public announcements, as of the date indicated on each page. Third-party features, pricing, availability, and terms change frequently and are outside Latchkey's control. Latchkey does not warrant that such information is current, complete, or error-free, and you should verify any third-party detail directly with the relevant provider before relying on it.

Opinions and No Reliance

Comparative content may reflect Latchkey's own views and opinions and is provided for general informational purposes only. It is not a representation, warranty, or guarantee regarding any third party or its products or services, and it is not a substitute for your own independent evaluation. Latchkey is not responsible for decisions made in reliance on this content.

Corrections

We aim to keep comparative content fair and accurate. If you are a third party or a reader and believe any statement is inaccurate or out of date, contact legal@latchkey.dev and we will promptly review and, where appropriate, correct or remove it.

You agree not to:

  • Reverse engineer, decompile, or disassemble any aspect of the Service.
  • Use the Service to benchmark without our prior written consent.
  • Use the Service for any illegal purpose.

The Service depends on third-party platforms (e.g., GitHub, GitLab).

Third-Party Disclaimer

We are not responsible for interruptions caused by third-party providers.

To the maximum extent permitted by law, Latchkey shall not be liable for any indirect, incidental, special, consequential, or punitive damages.

We reserve the right to suspend or terminate your access to the Service at our sole discretion for conduct that violates these Terms.

Contact Us

If you have questions about these Terms, please contact us at:

Changes to These Terms

We reserve the right to modify these Terms at any time. Your continued use constitutes acceptance of the new Terms.

We use cookies to improve your experience. Privacy Policy