Help with Lockstep

For account, billing, or CI setup help, contact .

Checkout and activation

After checkout, return to Lockstep in the same browser and enter the GitHub repository as owner/repository, or the GitHub organization name for the organization plan. If activation cannot verify your purchase, retry after a short wait and confirm you returned from the Lockstep checkout link.

CI check setup

Save the issued key as the GitHub Actions secret LOCKSTEP_API_KEY in the repository or organization covered by your plan. The starter workflow needs read access to repository contents; its generated configuration uses contents: read and does not need the GitHub pull requests API. A 401 response means the key is missing or invalid; a 403 means the subscription is inactive or does not cover that repository.

When contacting support

Include the GitHub repository, the approximate time of the issue, and the HTTP status or error message. Never send your CI key, Stripe checkout session URL, credentials, or migration SQL.

See the privacy notice for data handling and the terms of service for service and billing details.