Developer Tools · head to head
Blacksmith vs Ozone API

Blacksmith
Developer Tools
2x faster GitHub Actions with 60% cost savings
- From
- Free
- Free plan
- Yes

Ozone API
APIs
Standards-compliant open banking API layer for banks and regulators
- From
- On request
- Free plan
- No
The short version
- Blacksmith is a GitHub Actions runner service.
- Blacksmith starts at $0.004/mo; Ozone API prices on request.
- Only Blacksmith lists bare metal runners; only Ozone API lists consent management.
- Where Blacksmith falls short: per-minute pricing model requires estimating usage to predict costs.
- Where Ozone API falls short: value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend.
- Prices and features on this page were last checked on 20 November 2026.
How do Blacksmith and Ozone API differ?
Blacksmith and Ozone API differ on starting price (Free against On request), free tier (Yes against No) and platforms. Only the attributes on which Blacksmith and Ozone API actually diverge.
| Attribute | Blacksmith | Ozone API |
|---|---|---|
| Starting price | Free | On request |
| Free tier | Yes | No |
| Platforms | GitHub Actions, Linux, Windows, macOS | Web, API, Linux |
| Category | Developer Tools | APIs |
Not yet recorded: pricing model for Blacksmith, founded for Ozone API.
Which features does each one have?
They share no listed features; 8 appear only for Blacksmith and 6 only for Ozone API. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.
Only in Blacksmith
- Bare metal runners
- Multiple OS support
- ARM support
- Docker layer caching
- Sticky disks
- GitHub Actions observability
- Free tier
- Static IPs
Only in Ozone API
- Multi-standard support
- Consent management
- Developer portal
- Regulatory reporting
- Premium API monetisation
- Deployment flexibility
What is each one used for?
Blacksmith is most often brought in for replacing GitHub Actions runners with faster, cheaper infrastructure; Ozone API for A regulator or standards body building national open finance infrastructure. The jobs each tool is most often brought in to do.
Blacksmith
- Replacing GitHub Actions runners with faster, cheaper infrastructurenot Ozone API
- Accelerating CI build times for organizations with heavy CI loadnot Ozone API
- Reducing cloud spend on GitHub Actions by 60% or morenot Ozone API
- Supporting ARM architecture builds without GitHub runnersnot Ozone API
Ozone API
- A building society facing an open banking compliance deadline with no API team of its ownnot Blacksmith
- A bank operating in several jurisdictions that must satisfy different open banking standards at oncenot Blacksmith
- A regulator or standards body building national open finance infrastructurenot Blacksmith
- A bank wanting to sell premium APIs beyond the regulatory minimum without building entitlement plumbingnot Blacksmith
Where do Blacksmith and Ozone API fall short?
Blacksmith's most cited limit: per-minute pricing model requires estimating usage to predict costs. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Blacksmith
- Per-minute pricing model requires estimating usage to predict costs
- macOS M4 pricing ($0.08/min) is significantly higher than GitHub Actions
- Docker layer caching and sticky disks are paid add-ons at $0.50/GB/mo
- Static IP add-on costs $100/IP/mo
Ozone API
- It provides the API layer, not the core connectivity, so the bulk of the project is still integrating your own core banking systems and that cost is not in the licence
- Value is driven by regulatory obligation, so an institution not under a mandate struggles to build a business case for the spend
- It is a small UK vendor selling to large regulated institutions, which raises procurement and vendor viability questions during bank due diligence
- Premium API monetisation is a genuine capability but few banks have found real demand, so revenue projections used to justify the purchase often do not materialise
- Standards evolve continuously and each revision means a change programme in your own systems, even where Ozone absorbs the specification work at the API edge
How much do Blacksmith and Ozone API cost?
Blacksmith has a free plan, with paid plans from $0.004/mo; Ozone API is priced on request. Plan by plan below, from each vendor's own pricing page.
Blacksmith
Free- Ubuntu x64$0.004/minute
- 3,000 free minutes per month
- 2x faster hardware
- 4x faster cache downloads
- Ubuntu ARM$0.0025/minute
- 3,000 free minutes per month
- 2x faster hardware
- 4x faster cache downloads
- Windows x64$0.008/minute
- 3,000 free minutes per month
- 2x faster hardware
- 4x faster cache downloads
- macOS M4$0.08/minute
- 3,000 free minutes per month
- 2x faster hardware
- 4x faster cache downloads
Ozone API
On request- Ozone APIOn request
- Annual licence or managed service subscription, quoted
- Scaling by institution size, standards in scope and API call volume
- Implementation and core integration charged separately
Which should you pick?
Choose Blacksmith if
- You need bare metal runners.
- You want to start without paying.
- You work on GitHub Actions, Linux, Windows, macOS.
- You also want multiple os support.
Choose Ozone API if
- You need multi-standard support.
- You work on Web, API, Linux.
- You also want consent management.
Questions people ask
- Is Blacksmith or Ozone API better?
- Neither clearly leads. Blacksmith starts at Free and Ozone API at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Blacksmith or Ozone API?
- Blacksmith has a free tier; the other does not. Paid plans start at Free for Blacksmith and On request for Ozone API.
- Does Blacksmith or Ozone API run on more platforms?
- Blacksmith runs on GitHub Actions, Linux, Windows, macOS. Ozone API runs on Web, API, Linux.
- Can I use Blacksmith for free?
- Yes. Blacksmith has a free tier, so you can try it without paying. Ozone API starts at On request.
- What is Blacksmith best used for?
- Blacksmith is most often used for replacing github actions runners with faster, cheaper infrastructure, accelerating ci build times for organizations with heavy ci load, reducing cloud spend on github actions by 60% or more, supporting arm architecture builds without github runners. Of those, replacing github actions runners with faster, cheaper infrastructure and accelerating ci build times for organizations with heavy ci load are not what Ozone API is typically brought in for.
- What can Blacksmith do that Ozone API cannot?
- Blacksmith covers Bare metal runners, Multiple OS support, ARM support, Docker layer caching. Ozone API covers Multi-standard support, Consent management, Developer portal, Regulatory reporting.
Answered from the vendors’ own pages
Blacksmith: How much do Blacksmith runners cost compared to GitHub Actions?
Blacksmith offers 60-75% cost savings depending on OS. Ubuntu x64 costs $0.004/min vs GitHub at $0.012/min. All plans include 3,000 free minutes monthly.
SourceOzone API: Is this a competitor to Plaid or TrueLayer?
No, the opposite side. Ozone is bought by the bank exposing data; Plaid and TrueLayer consume it on behalf of third parties.
Blacksmith: Can I use Docker layer caching with Blacksmith?
Yes, Docker layer caching is available as an add-on at $0.50/GB/mo. Managed Docker layer persistence is included with the base service.
SourceOzone API: Does it connect to my core banking system?
It provides the standards-compliant API surface and adapters, but connecting your core is an integration project you scope separately.
Blacksmith: What is the SLA for Enterprise plans?
Enterprise Blacksmith plans include a 99.9% SLA guarantee along with 24/7 priority support, dedicated Slack channels, white-glove onboarding, and CI optimization support.
SourceOzone API: Which standards does it support?
UK Open Banking, Berlin Group, FDX, Consumer Data Right and Gulf regional standards, among others, from one platform.
Related pages
Other head to heads
- Blacksmith vs WarpBuild
- Blacksmith vs Depot
- Blacksmith vs Namespace
- Blacksmith vs Jenkins
- Blacksmith vs Kubernetes
- Blacksmith vs GitLab
- Blacksmith vs Earthly
- Blacksmith vs Nx Cloud
- Blacksmith vs OpsLevel
- Blacksmith vs Terraform
- Blacksmith vs GitHub
- Blacksmith vs LaunchDarkly
- Blacksmith vs Coder
- Blacksmith vs Envoy
- Blacksmith vs JetBrains IntelliJ IDEA
- Blacksmith vs Keycloak
- Blacksmith vs Penpot
- Blacksmith vs Argo CD
- Blacksmith vs TrueLayer
- Blacksmith vs Enable Banking
- Blacksmith vs Salt Edge
- Blacksmith vs Token.io
- Blacksmith vs Temenos Transact
- Blacksmith vs MX Technologies
- Blacksmith vs Tink
- Blacksmith vs Akoya
- Blacksmith vs Sensedia
- Blacksmith vs Tribe Payments
- Blacksmith vs Bud Financial
- Blacksmith vs Synctera
- Blacksmith vs Trustly
- Blacksmith vs WSO2 API Manager
- Blacksmith vs Brite Payments
- Blacksmith vs Dwolla
- Blacksmith vs Liveblocks
- Blacksmith vs Parse Server
- Ozone API vs WarpBuild
- Ozone API vs Depot
- Ozone API vs Namespace
- Ozone API vs Jenkins
- Ozone API vs Kubernetes
- Ozone API vs GitLab
- Ozone API vs Earthly
- Ozone API vs Nx Cloud
- Ozone API vs OpsLevel
- Ozone API vs Terraform
- Ozone API vs GitHub
- Ozone API vs LaunchDarkly
- Ozone API vs Coder
- Ozone API vs Envoy
- Ozone API vs JetBrains IntelliJ IDEA
- Ozone API vs Keycloak
- Ozone API vs Penpot
- Ozone API vs Argo CD
- Ozone API vs TrueLayer
- Ozone API vs Enable Banking
- Ozone API vs Salt Edge
- Ozone API vs Token.io
- Ozone API vs Temenos Transact
- Ozone API vs MX Technologies
- Ozone API vs Tink
- Ozone API vs Akoya
- Ozone API vs Sensedia
- Ozone API vs Tribe Payments
- Ozone API vs Bud Financial
- Ozone API vs Synctera
- Ozone API vs Trustly
- Ozone API vs WSO2 API Manager
- Ozone API vs Brite Payments
- Ozone API vs Dwolla
- Ozone API vs Liveblocks
- Ozone API vs Parse Server
