Blueprints AI
Back to Media Room

How One Mac Studio Replaced Our Cloud CI Bill and Made Our Tests 4× Faster

11/09/2026

How One Mac Studio Replaced Our Cloud CI Bill and Made Our Tests 4× Faster cover image

Category

Tech Sharing

Read Time

12 mins

Share

How One Mac Studio Replaced Our Cloud CI Bill and Made Our Tests 4× Faster

Blueprints AI moved its automatic code testing (CI) from a pay-by-the-minute cloud service to one $5,499 Mac Studio. On a heavy day, cloud CI cost about $200 per engineer, and we paid it because speed matters. The Mac turned out faster too: jobs take about a quarter of the time GitHub's runners would need. Footnoted, with the arithmetic.

Blueprints AI · Field NotesEngineering
ProjectAutomatic code testing (CI)
on one Mac Studio
Drawn byAl Dram, Founder & CEO
Blueprints AI
Date · ReadNov 9, 2026
~9 min
StatusCLOUD CI BILL REPLACED
JOBS ~4× FASTER THAN GITHUB'S RUNNERS
FIXED COST, NO METER
Abstract

Blueprints AI builds software that turns architectural designs into construction drawings. Like every software company, it pays for CI: computers that automatically test every change an engineer makes. In November 2026 we moved that work from a cloud service that bills by the minute to one Mac Studio that cost $5,499. We expected to save money and give up some speed. Instead, in a test week building a small sample app, our tracker measured jobs taking about a quarter of the time GitHub's own runners would need, and about two-thirds of the time on Blacksmith, the cheaper service we had been paying.[1] Our real cloud CI bill swings with the day. On a heavy day it costs about $200 for each engineer; ten engineers at once is $2,000 a day, and a bill like that can get out of control very fast. We paid it anyway, because speed matters. The Mac gives us more speed for a fixed price: counted only in heavy days, it pays for itself in about 28 of them for one engineer, and in under a week for a team of eight.[10] This note explains what CI is, why teams need it, what it costs, what we did, and when you should not copy us. Every outside figure is cited; where we estimate, we show the arithmetic.

Keywords: continuous integration · CI costs · GitHub Actions · self-hosted runner · Mac Studio · M5 Ultra · Blueprints AI

1. What Is CI?

CI stands for continuous integration. In plain terms: every time an engineer sends in a change, a computer automatically downloads the latest code, builds it, and runs a long list of small tests to make sure nothing broke.[2] If a test fails, the engineer knows within minutes, not weeks later from an unhappy customer.

The computer that does this is called a runner. Most teams rent runners from a cloud company and pay for every minute the runner works.[3] A runner can also be your own computer. GitHub calls that a self-hosted runner, and that is what we switched to.

2. Why Every Software Team Needs It

I come from construction, so here is the comparison I use. CI is a building inspection that happens every day instead of once at the end. Small mistakes get caught while they are still cheap to fix.

It matters even more for us than for most teams. Our engineers work alongside AI coding tools that write and change code all day. More changes mean more checks, and with per-minute billing, more checks mean a bigger bill.

Most teams pay for cloud CI by default and never check whether their own machine could do the job.

3. The Bill: Paying by the Minute

Here is what the minute costs today. We were on Blacksmith, which is already cheaper per minute than GitHub's own runners (Table 1). This is not a knock on them; it was the cheaper of the two options we had.

Table 1. List price per runner-minute, US dollars, smallest standard runners.
RunnerGitHub-hosted[3]Blacksmith[4]
Linux, 2 cores (x64)$0.006$0.004
Linux, 2 cores (ARM)$0.005$0.0025
Windows, 2 cores$0.010$0.008
macOS$0.062 (3–4 cores)$0.08 (6 cores, M4)
Your own computer (self-hosted)$0 per minute to GitHub today. A $0.002 fee was announced, then postponed.[5]n/a

Fractions of a cent sound like nothing. They add up fast. To test our setup, one person built a small sample app for a week. On GitHub's own runners, those jobs would have cost about $56.[1] That is a toy. A real product is much bigger, and our bill changes from day to day with how much the team ships. On a heavy day, when engineers and their AI coding tools send in change after change, cloud CI runs about $200 per engineer.[1] Now picture 10 engineers working at the same time: $2,000 in a single day. A month of days like that is $44,000. At 50 engineers, it is $220,000 a month (FIG. 1).[10] Bigger, faster runners cost more per minute than the ones in Table 1, and fast is exactly what we were paying for.

Horizontal bar chart of cloud CI cost, from a toy app to a real team: small sample app, 1 person, 1 week, $56; real product, 1 engineer, 1 heavy day, $200; 10 engineers at once, 1 heavy day, $2,000; 10 engineers, a month of heavy days, $44,000; 50 engineers, a month of heavy days, $220,000. A dashed line marks one Mac Studio at $5,499, paid once.
FIG. 1. Cloud CI from a toy app to a real team, drawn in code. Not every day is heavy, so the monthly bars are the ceiling, not an average. But the meter has no ceiling of its own. The dashed line is one Mac Studio, paid once.[10]

We paid it because speed matters. An engineer waiting on tests is an engineer not building, and slow tests cost more than the bill.

4. What We Did

Honestly, I expected a trade-off. Cloud CI companies run fleets of fast servers, and one box on a desk did not look like a fair fight. I bought the Mac to stop a growing bill, and I was ready to wait a little longer for our tests. That is not what happened.

We bought one Mac Studio with Apple's M5 Ultra chip: 30 CPU cores, 64 GPU cores, 96GB of memory and a 1TB drive, at a list price of $5,499.[6] We connected it to GitHub, where our code lives, and told GitHub to send our test jobs to the Mac instead of the cloud.

The engineers changed nothing about how they work. They send in code the same way as before. It just comes back faster. And the Mac does not sit idle between test runs: the team uses the same machine for everyday development and video editing.

We expected to wait. The quote for build-to-order Mac Studios said 13 to 15 weeks. Instead, Apple's Business Team at the Third Street Promenade store in Santa Monica found an M5 Ultra in the store and had it in our hands within days.[11] Thank you.

5. The Numbers (Receipts Included)

Table 2. Before and after.
MeasureCloud CIOne Mac Studio
Up-front cost$0$5,499, once[6]
Running costVaries by day. A heavy day: about $200 per engineer, and climbing[1]Electricity: at most about $2.43 a day ($74 a month)[7][8]
Job time, test week (small sample app)59 h 45 m on Blacksmith; 156 h on GitHub (estimated)40 h 15 m[1]
Paybackn/aAbout 28 heavy days for one engineer; under a week for eight[10]
Also used forNothing elseDevelopment work and video editing
Bar chart: how many heavy days of cloud CI one $5,499 Mac Studio costs. With 1 engineer ($200 a heavy day), about 28 days; 2 engineers ($400), 14 days; 4 engineers ($800), 7 days; 8 engineers ($1,600), 3.4 days.
FIG. 2. How many heavy days of cloud CI one Mac Studio costs, drawn in code. A heavy day is about $200 of cloud CI per engineer. For one engineer, the Mac is paid for after about 28 heavy days; for two, 14; for four, 7; for eight, under four. Savings are counted after worst-case electricity.[10]

The electricity figure deserves a word, because it is the one number a skeptic will check. Apple publishes the maximum power draw of the top M5 Ultra Mac Studio: 385 watts, and 9 watts at idle.[7] If ours ran at that maximum every hour of every day, at California's average commercial electricity price, it would cost about $2.43 a day, or about $74 a month.[8] It never does, so the real number is lower. We use the worst case anyway.

A cloud bill has a meter; the Mac does not. Our bill grows with every engineer we hire, every feature we ship and every test our AI coding tools add, and the heavy days come more often. The Mac's cost stays where it is, so the heavier the days get, the faster it pays for itself (Table 3).

Table 3. A fixed cost vs. a meter. How many heavy days ($200 of cloud CI per engineer) one $5,499 Mac Studio takes to pay for itself, worst-case electricity included.
Engineers on a heavy dayCloud CI that dayHeavy days to pay for the Mac
1$200About 28
2$400About 14
4$800About 7
8$1,600About 3.4

Not every day is heavy, so on a calendar it takes longer than these counts. But the heavy days are the ones that decide the bill, and they are exactly the days it gets out of control.

We also built a small app that watches the Mac and keeps score (FIG. 3). To test the setup, we first pointed it at a small sample app, not our real workload, so its dollar figures are the floor, not our bill. In that test week it measured 40 hours 15 minutes of job time on the Mac. It estimates the same jobs would have taken 59 hours 45 minutes on Blacksmith and 156 hours on GitHub's own runners: about two-thirds of Blacksmith's time, and about a quarter of GitHub's.[1][10]

Screenshot of the Blueprints AI CI tracker app on a Mac desktop. It shows 8 runners with 0 jobs queued; CPU at 9%, memory 53%, GPU 4%; for the week, savings of $56.32 against GitHub Actions and $28.68 against Blacksmith; job time of 156 hours on GitHub, 59 hours 45 minutes on Blacksmith and 40 hours 15 minutes on the Mac; and a payback box at $28.68 of $6,118.
FIG. 3. Screenshot, the real thing: our CI tracker on November 9, 2026, during the sample-app test. Eight runners and the week's job time. Its dollar figures ($56.32 against GitHub, $28.68 against Blacksmith) price only that small test app, the starting point of FIG. 1; its payback box is built on them and does not reflect our real workload.[1]
Table 4. The test week, building a small sample app, as measured by our tracker (live since November 7, 2026).
MeasureValue
Job time on the Mac40 h 15 m
Same jobs on Blacksmith (estimated)59 h 45 m, about $29
Same jobs on GitHub's runners (estimated)156 h, about $56
Job-minutes run on our Macs2,415
Runners on the Mac Studio8
Busiest hour, last 24 hours35% of the processor; 3.1 jobs at once (hour average)

What happens when it fills up?

We add another machine. Today the Mac has plenty of room: in its busiest hour of the last day it used 35% of its processor and ran about three jobs at once across its eight runners.[1] But the team is growing, so we're ordering a second, stronger Mac Studio: an M5 Ultra with a 36-core CPU, an 80-core GPU, 256GB of memory and 2TB of storage.[6] By the time we need the extra power, it will already be on the desk. Two machines also mean testing keeps running if one goes down.

On a heavy day, cloud CI costs about $200 per engineer. The Mac costs the same no matter how heavy the day gets.

6. Why One Computer Can Beat the Cloud

We expected to save money and lose some speed. We got both: the bill went away, and the tests got faster.

We paid the cloud's prices because speed matters to us. It turns out the fastest option was the one on the desk.

It sounds backwards. Cloud companies run huge fleets of fast machines. How does one box on a desk win? Three reasons, none of them magic.

No warm-up. A cloud runner usually starts empty for every job. It has to boot, download your code and all its tools, and only then start testing. Our Mac is always on and already has everything.

It remembers. Whatever the Mac downloaded for the last test run is still on its drive, so the next run skips that work.

It is fast, and it is ours. Apple's newest chips have very fast individual cores, and much of a test run is one long chain of steps that cannot be split up. Nobody else's jobs share the machine.

Cloud CI companies solve a harder problem: running thousands of strangers' jobs safely, in parallel, from a clean start every time. We do not have that problem: every job on our Mac is our own code.

7. When This Is Not a Good Idea

  • Open-source projects. If strangers can send code to your project, running it on your own computer is a security risk. GitHub recommends self-hosted runners only for private code.[9] Ours is private and written by our own team.

  • Big bursts of jobs. A cloud service can start dozens of runners at once. One computer can only do so many, so at busy moments jobs wait in line briefly. For us that is a fine trade, and when it stops being one, we add a machine (section 5).

  • Linux-only builds. If you build x86 Linux Docker images, an Apple chip has to imitate a different processor, which is slow. Keep those jobs in the cloud.

  • One machine, one point of failure. If the power or the internet goes out, testing stops. Keep your old cloud setup ready to switch back to, or run a second machine.

  • Prices change. GitHub's postponed $0.002-a-minute fee for self-hosted runners could return.[5] That is a third of GitHub's cheapest Linux rate per minute, and our jobs take fewer minutes on the Mac, but it is worth knowing.[3]

8. Conclusion: Check the Math

A personal note. I spent most of my career on Windows, because that is where Autodesk's tools live, and on Linux for our servers and my own AI training. This Mac is the first machine that does all of it for me at once: our code, our tests, our video. I don't see myself going back to a Windows or Linux desk.

Blueprints AI builds software for the construction industry. Every dollar we save on infrastructure goes back into the product, and every minute our engineers do not spend waiting on tests is a minute spent building.

If your team works on private code and your CI bill keeps climbing, try it. Buy one machine, send a few test jobs to it, and compare. Worst case, you end up with a very good computer.

For engineers: the setup

We installed GitHub's runner app on the Mac, registered it with our organization, and run several runner instances on the one machine so jobs can run in parallel. Then one line changes in each workflow file:

jobs:
  test:
    runs-on: [self-hosted, macOS, ARM64]
Al Dram, Founder & CEO, Blueprints AI. Licensed general contractor. Former architecture professor. Believes in daily inspections, for buildings and for code.
Cite this articleDram, Al (2026). How One Mac Studio Replaced Our Cloud CI Bill and Made Our Tests 4× Faster. Blueprints AI Field Notes, November 9, 2026. blueprints-ai.com.

References & Calculations

Sources consulted November 9, 2026. Prices carry their as-of dates and will drift; the arithmetic will not. Charts marked "drawn in code" were plotted in Python from the figures below.

  1. Blueprints AI internal figures. Cloud CI spend varies by day with how much the team ships; on a heavy day it runs about $200 per engineer. Our CI tracker (FIG. 3), screenshot taken November 9, 2026, day 3 of tracking, during a test building a small sample app rather than our real workload: 8 runners on the Mac Studio; 2,415 job-minutes run on our Macs; job time for the week of 40 h 15 m on the Mac, against an estimated 59 h 45 m on Blacksmith (4-vCPU runners) and 156 h on GitHub-hosted 2-core runners; busiest hour in the last 24 hours at 35% CPU and 3.1 jobs at once. The cloud times are the tracker's estimates for the same jobs, not separate runs. The same sample-app jobs priced at $28.68 on Blacksmith and $56.32 on GitHub. These price only that sample app; the tracker's payback box is built on them and does not reflect our real workload. Speed on our full codebase will differ, and so will yours. ↩ a b c d e f g h
  2. What CI is. GitHub Docs, Continuous integration: committing code often and building and testing it automatically on every commit, so errors are caught sooner. Building and testing requires a server, either your own machine or a CI server. ↩
  3. GitHub-hosted runner prices. GitHub Docs, Actions runner pricing, read November 9, 2026: Linux 2-core x64 $0.006, Linux 2-core ARM $0.005, Windows 2-core $0.010, macOS 3- or 4-core $0.062 per minute. GitHub rounds each job up to the next whole minute. ↩ a b c
  4. Blacksmith runner prices. Blacksmith docs, pricing Removed by the publisher ($0.004 per minute for a 2-vCPU Ubuntu x64 runner, billed per minute), and the full rate list as read by cicdpipelinecost.com on October 1, 2026: Ubuntu ARM $0.0025, Windows x64 $0.008, 6-vCPU macOS M4 $0.08, with 3,000 free minutes a month. ↩
  5. GitHub's self-hosted runner fee. On December 16, 2025, GitHub announced hosted-runner price cuts of up to 39% from January 1, 2026, and a $0.002-per-minute charge on self-hosted runners from March 1, 2026. Within days it posted an update: it was "postponing the announced billing change for self-hosted GitHub Actions" (GitHub changelog; see also Techzine). GitHub's pricing page, read November 9, 2026, lists no charge for self-hosted runners [3]. ↩ a b
  6. Mac Studio, M5 Ultra. Starting configuration: 30-core CPU, 64-core GPU, 96GB unified memory, 1TB SSD, $5,499 in the US (PetaPixel; 9to5Mac; Apple, tech specs). Before sales tax. The stronger configuration we are ordering has a 36-core CPU and 80-core GPU (PetaPixel) and can be configured with 256GB or 512GB of memory (Apple, tech specs). ↩ a b c
  7. Power use. Apple, Mac Studio power consumption and thermal output: the M5 Ultra with 36-core CPU, 80-core GPU, 512GB memory and 16TB SSD draws 9 W idle and 385 W at maximum, measured at the wall. Apple lists only that configuration for the M5 Ultra; we use its maximum as an upper bound for our smaller one. ↩ a b
  8. Electricity price. California's average commercial electricity price for the 12 months ended January 2026 was 26.25 cents per kWh, based on US Energy Information Administration data (Center for Jobs and the Economy). Your utility's rate may differ. ↩ a b
  9. Security. GitHub Docs, Managing access to self-hosted runners: GitHub recommends using self-hosted runners only with private repositories, and by default only private repositories can use them. ↩
  10. Calculations. Worst-case electricity: 385 W × 24 hours = 9.24 kWh a day × $0.2625 = $2.43 a day; 385 W × 730 hours = 281.05 kWh a month × $0.2625 = $73.78 a month. At idle (9 W) a day costs about 6 cents. FIG. 1: a heavy day = $200 × engineers; a month = 22 working days. 10 engineers: $2,000 a day, $44,000 a month. 50 engineers: $10,000 a day, $220,000 a month, about $2.6 million a year if every working day were heavy. Heavy days to pay for the Mac (FIG. 2, Table 3): $5,499 ÷ ($200 × engineers − $2.43): 1 engineer, 27.8 days; 2, 13.8; 4, 6.9; 8, 3.4. Electricity on the days in between is not counted; at worst it adds $2.43 a day. Speed, from the tracker's sample-app test [1]: 40.25 h ÷ 156 h = 26% of GitHub's time (3.9× faster); 40.25 h ÷ 59.75 h = 67% of Blacksmith's time (1.5× faster). A returning $0.002 fee would be one-third of GitHub's $0.006 rate for its 2-core Linux runner [3]. ↩ a b c d e f
  11. Delivery. Blueprints AI correspondence with Apple's Third Street Promenade Business Team, Santa Monica: the October 31, 2026 quotation for build-to-order Mac Studios and its estimated 13- to 15-week wait, and an in-store M5 Ultra (30-core CPU, 64-core GPU, 96GB, 1TB) offered on November 6, 2026. ↩

Ready to redefine the future of AEC?

Join the 4,000+ companies already signed up for the future of architecture, engineering, and construction.