Question 1

What is Sprintr?

Accepted Answer

Sprintr lets you run GitHub Actions workflows on your own cloud infrastructure — AWS. Instead of paying for GitHub-hosted runners or managing self-hosted runners manually, Sprintr provisions, scales, and tears them down automatically on your behalf.

Question 2

Who is Sprintr for?

Accepted Answer

Sprintr is built for engineering teams that have outgrown GitHub's free tier — typically mid-size to enterprise companies running hundreds or thousands of workflow minutes per month. If your GitHub Actions bill is climbing or your pipelines are hitting concurrency limits, Sprintr was designed for you.

Question 3

How is Sprintr different from GitHub-hosted runners?

Accepted Answer

GitHub-hosted runners run on GitHub's shared infrastructure and come with usage limits and fixed hardware specs. Sprintr runners run inside your own cloud account, giving you full control over machine size, region, network access, and cost — with no GitHub minute caps.

Question 4

Does Sprintr replace GitHub Actions, or work alongside it?

Accepted Answer

Sprintr works alongside GitHub Actions. Your workflows stay exactly as they are — Sprintr simply provides the runners they execute on. No changes to your .yml files are required.

Question 5

How long does it take to get started?

Accepted Answer

Most teams are up and running within minutes. You connect your cloud provider, authorize Sprintr on your GitHub organization, and select which repositories or workflow labels should use Sprintr runners.

Question 6

Which cloud providers does Sprintr support?

Accepted Answer

Sprintr currently supports AWS. Support for additional providers is on the roadmap — reach out if you have a specific request.

Question 7

Do I need to modify my existing GitHub Actions workflows?

Accepted Answer

In most cases, no. If you use ubuntu-latest or similar standard labels, Sprintr can intercept those automatically. For teams that want fine-grained control (e.g., routing specific jobs to specific machine types), you can use custom runner labels that Sprintr registers on your behalf.

Question 8

What permissions does Sprintr need on my GitHub organization?

Accepted Answer

Sprintr requires permission to manage self-hosted runners at the organization or repository level. It does not require access to your source code, secrets, or pull request contents.

Question 9

Does Sprintr ever have access to my source code or CI secrets?

Accepted Answer

No. Sprintr only orchestrates runner lifecycle (provisioning, registration, teardown). Your code and secrets remain inside GitHub and your own cloud environment — Sprintr never touches them.

Question 10

Where do the runners actually run?

Accepted Answer

Runners are launched directly inside your own cloud account, in the region and VPC of your choice. Sprintr never routes your workload through its own infrastructure.

Question 11

Are runners ephemeral?

Accepted Answer

Yes. By default, each Sprintr runner is a fresh, single-use VM that is terminated immediately after a job completes. This ensures no state bleeds between jobs and significantly reduces your attack surface.

Question 12

Is Sprintr SOC 2 compliant?

Accepted Answer

Sprintr is not yet SOC 2 Type II certified.

Question 13

How does Sprintr pricing work?

Accepted Answer

Sprintr charges a flat 30% of whatever the instance cost is, eg: if the instance cost is $100 Sprintr will charge $30.

Question 14

Will Sprintr actually save us money compared to GitHub-hosted runners?

Accepted Answer

For most teams running more than a few thousand minutes per month, yes — significantly. Cloud compute costs are typically 40–70% lower than GitHub's per-minute runner pricing, and Sprintr's auto-scaling ensures you're never paying for idle capacity.

Question 15

Is there a free trial?

Accepted Answer

Yes. Sprintr offers a 14-day free trial with no credit card required. Your cloud provider charges for compute still apply during the trial.

Question 16

Do you offer annual pricing or volume discounts?

Accepted Answer

Yes. Annual plans come with a discount compared to monthly billing, and enterprise pricing is available for organizations with large runner fleets or custom requirements. Contact our sales team for a quote.

Question 17

How quickly does Sprintr spin up a new runner?

Accepted Answer

Typical cold-start time is under 60 seconds for standard machine images. Teams using Sprintr's pre-warmed runner pools can achieve start times under 10 seconds.

Question 18

Can I use custom machine images or pre-installed toolchains?

Accepted Answer

Yes. Sprintr supports custom AMIs (AWS), custom images (GCP/Azure), and Docker-based runner images. This is especially useful for teams that want to avoid reinstalling large dependencies on every job.

Question 19

What happens if my cloud provider has an outage?

Accepted Answer

Sprintr's control plane monitors runner health and will surface alerts in your dashboard.

Question 20

Is there a concurrency limit?

Accepted Answer

Concurrency is limited only by your cloud account's quotas. Sprintr itself imposes no artificial cap — teams routinely run hundreds of parallel jobs without issue.

Question 21

What support options are available?

Accepted Answer

All plans include email support and access to our documentation.

Question 22

Can Sprintr be deployed fully within our own infrastructure (self-hosted control plane)?

Accepted Answer

No, not yet. Support for self-hosted Sprintr is on the road map.

Question 23

Do you offer onboarding assistance?

Accepted Answer

Sprintr's control plane monitors runner health and will surface alerts in your dashboard.

GitHub Actions Runners That Scale With You.

Self-Hosted GitHub Actions Runners, Without the Headache.

Simple, Transparent Pricing

30% of whatever your cloud provider charges you.

Free in beta

Frequently Asked Questions

General

Setup & Integration

Security & Compliance

Pricing & Cost

Performance & Reliability

Support & Enterprise