Opportunities › Self-hosted CI/CD runners for GitHub Actions › Proposed app
Spotrun
Cheaper, faster GitHub Actions runners on your own AWS account, without the ops work
- Score
- 46
- confidence 74
- Evidence
- 15
- items on the page
- Rivals
- 6
- named in sources
- First version
- 45 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2019
- Established market · AI estimate
ScreensConcept
Desktop app: Engineers connect AWS accounts, review cost breakdowns by workflow, and monitor build queues—involved setup and ongoing analytics work. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
Savings
Sample data$3,420
About this appAI proposal
Spotrun sets up self-hosted GitHub Actions runners inside your own AWS account. Connect GitHub, pick a region and instance sizes, and jobs start running on spot capacity that scales up and down with your queue. No cluster to babysit and no Terraform to fork.
It is built for engineering teams whose CI bill has grown into the thousands per month, or whose builds wait on slow hosted machines. Public claims in the material put savings at 6x to 10x, and that is the figure to test here, not a promise.
Unlike running Actions Runner Controller yourself, Spotrun handles runner images, spot interruptions, and cache storage for you. You see cost per workflow and per repository, and you keep your code and secrets in your own cloud.
- Tagline
- Run your Actions on your own AWS, for a fraction of the bill.
- Voice
- PlainPrecisePractical
- Why this name
- Spot instances are the source of the savings, and run is what a CI job does. Two plain syllables, easy to say and to type.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
One-screen AWS setup
Connect GitHub and AWS with a guided setup that creates scoped roles and a runner pool. No cluster or Terraform required.
No member yet
Spot-first scaling
Runners launch on spot instances and fall back to on-demand when capacity is short. Interrupted jobs are retried automatically.
No member yet
Large shared cache
Dependency and build caches live in your own S3 bucket, close to the runners, so they are not capped by hosted limits.
No member yet
Cost per workflow
See what each repo, workflow and job costs on AWS, next to what the same minutes would cost on hosted runners.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#12372ADeep Pine · primary#F6F4EEPaper · surface#1B1F1DInk · text#F2A33ASignal Amber · accent#5E8C61Moss · data, savings
Typography
Aa
Spotrun
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Run your Actions on your own AWS, for a fraction of the bill.
PricingAI proposal
The material lists GitHub Actions plans from $4 to $21 a month, but gives no price for runner minutes or competing runner services. These tiers are a starting point to test, not derived from competitor prices.
Free
Free
- 1 repository
- Up to 5 runners
- 7-day cost history
Team
$49 a month
- Unlimited repositories
- Up to 50 runners
- Cost per workflow
- Queue alerts by email
Scale
$199 a month
- Unlimited runners
- Multiple AWS accounts
- Custom runner images
- Priority support
Would you pay Team · $49 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- No loop in the product. Spotrun runs behind a team's own CI, so other people rarely see it. Reach comes from content, savings write-ups, and word of mouth among platform engineers rather than from use of the product.
- Do they become customers?
- Test whether teams with a large GitHub Actions bill will connect an AWS account after reading a savings estimate. A public savings calculator could bring in readers who then become trial users.
- First customers
- Platform or DevOps leads at software companies of 20 to 200 engineers, on GitHub and AWS, paying at least a few thousand dollars a month for Actions.
- Where to reach them
- Hacker News and engineering blogs: Publish a worked cost breakdown of moving a real pipeline to spot runners, with a link to a free savings estimate.
- GitHub and DevOps communities: Answer questions on Actions Runner Controller pain points and offer a free migration to a few teams.
- Direct outreach: Contact platform engineers who fork or star open-source runner projects and offer a hands-on pilot.
- First milestone
- Five teams on AWS each move one real pipeline to Spotrun, and three of them pay after a 30-day trial.
Why people already pay for this
- VerifiedGitHub repository gained 1360 stars in 1034 days
- Public claimSelf-hosted GitHub Actions runners for AWS cost 10x less than GitHub-hosted runners
- Public claimSelf-hosted runners can be significantly faster than GitHub-hosted alternatives
- Public claimCaching capabilities are limited on GitHub-hosted runners
- Public claim
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Cloud provisioningAWS APIs via a scoped cross-account roleCreates and scales spot instances and S3 cache buckets inside the customer's AWS account.
- This app · Job event intakeGitHub App with webhooksReceives queued-job events to scale runners and reads workflow metadata for cost reports.
RisksAI inference
- TechnicalSpot interruptions, slow runner start-up and scaling bugs can fail builds. Teams will drop it fast if CI becomes less reliable than hosted runners.
- PlatformGitHub could change runner APIs, terms or pricing for self-hosted runners, or improve its own large runners, shrinking the cost gap.
- CommercialA free Terraform module and Actions Runner Controller exist, and a commercial rival is named. Teams may prefer to self-build or may choose an established service.
- RegulatoryCustomers must grant cross-account AWS access. Security reviews could slow sales, and the 10x savings claims are unverified until tested on real workloads.
- CommercialCustomers' AWS savings accrue to them, so the subscription must be priced as a share of savings that buyers can see and trust.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.