Developer Tools · head to head
Blacksmith vs Portworx

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

Portworx
Cloud
Kubernetes-native storage and data services, priced by the node hour
- From
- $0.33/node hour
- Rated
- -
The short version
- Only Blacksmith has a free tier, so it costs nothing to try first.
- Each has a real cost: Blacksmith per-minute pricing model requires estimating usage to predict costs; Portworx bare metal nodes are charged at 1.11 USD per node hour against 0.33 for virtual nodes, so a bare metal cluster costs more than three times a virtualised one for identical capability.
- They diverge on capability: Blacksmith covers Bare metal runners, Portworx covers Container-native volumes.
- Prices and features above were last checked on 1 September 2026.
Where they differ
Only the attributes on which Blacksmith and Portworx actually diverge.
| Attribute | Blacksmith | Portworx |
|---|---|---|
| Starting price | Free | $0.33/node hour |
| Pricing model | Unknown | Per node hour |
| Free tier | Yes | No |
| Platforms | GitHub Actions, Linux, Windows, macOS | Linux |
| Category | Developer Tools | Cloud |
Identical on both: user rating (Not yet rated).
What each one covers
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 Portworx
- Container-native volumes
- Failure domain placement
- Volume encryption
- Database automation
- Disaster recovery
- Autopilot capacity management
- Hardware independence
What people use each for
The jobs each tool is most often brought in to do.
Blacksmith
- Replacing GitHub Actions runners with faster, cheaper infrastructurenot Portworx
- Accelerating CI build times for organizations with heavy CI loadnot Portworx
- Reducing cloud spend on GitHub Actions by 60% or morenot Portworx
- Supporting ARM architecture builds without GitHub runnersnot Portworx
Portworx
- Running a production PostgreSQL or Cassandra cluster on Kubernetes and needing the data to survive node lossnot Blacksmith
- A platform team offering self-service databases to developers on an internal Kubernetes platformnot Blacksmith
- Failing over stateful applications between clusters in different regions as a disaster recovery positionnot Blacksmith
- An OpenShift estate where the built-in storage option does not meet the availability requirement for stateful setsnot Blacksmith
Where each one falls short
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
Portworx
- Bare metal nodes are charged at 1.11 USD per node hour against 0.33 for virtual nodes, so a bare metal cluster costs more than three times a virtualised one for identical capability.
- A 1,000 node hour monthly minimum applies, which means small or intermittent clusters pay for capacity they do not consume.
- Replicating volumes across nodes consumes real capacity and network bandwidth, so the underlying infrastructure cost rises alongside the licence in a way the node hour rate does not show.
- Pure Storage ownership means roadmap priorities are set by an array vendor, and buyers should confirm that hardware independence remains contractual rather than assumed.
- Operating it well requires Kubernetes storage expertise, and teams that adopted Kubernetes to simplify operations often find they have added a distributed storage system to run.
Pricing, plan by plan
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
Portworx
$0.33/node hour- Portworx Enterprise on virtual machine nodes$0.33/node hour
- Minimum 1,000 node hours per month
- Replicated persistent volumes
- Encryption and disaster recovery
- Portworx Enterprise on bare metal nodes$1.11/node hour
- Minimum 1,000 node hours per month
- Same capabilities on bare metal clusters
- Higher rate reflects node density
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 Portworx if
- You need container-native volumes.
- You work on Linux.
- You also want failure domain placement.
Questions people ask
- Is Blacksmith or Portworx better?
- Neither clearly leads. Blacksmith starts at Free and Portworx at $0.33/node hour, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Blacksmith or Portworx?
- Blacksmith has a free tier; the other does not. Paid plans start at Free for Blacksmith and $0.33/node hour for Portworx.
- Does Blacksmith or Portworx run on more platforms?
- Blacksmith runs on GitHub Actions, Linux, Windows, macOS. Portworx runs on Linux.
- Can I use Blacksmith for free?
- Yes. Blacksmith has a free tier, so you can try it without paying. Portworx starts at $0.33/node hour.
- 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 Portworx is typically brought in for.
- What can Blacksmith do that Portworx cannot?
- Blacksmith covers Bare metal runners, Multiple OS support, ARM support, Docker layer caching. Portworx covers Container-native volumes, Failure domain placement, Volume encryption, Database automation.
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.
SourcePortworx: Is Portworx tied to Pure Storage hardware?
No. It runs on any Kubernetes distribution over any underlying storage, though Pure has owned it since 2020 and sets the roadmap.
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.
SourcePortworx: What does a real cluster cost?
At 0.33 USD per virtual node hour, twenty nodes running continuously is roughly 4,800 USD a month. Bare metal at 1.11 USD per node hour is around 16,000 USD for the same node count.
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.
SourcePortworx: Is backup included?
No. Portworx Backup is a separately priced product covering Kubernetes application backup.
Related pages
Other head to heads
- Blacksmith vs WarpBuild
- Blacksmith vs Depot
- Blacksmith vs Namespace
- Blacksmith vs Earthly
- Blacksmith vs Nx Cloud
- Blacksmith vs OpsLevel
- Blacksmith vs Garden
- Blacksmith vs ConfigCat
- Blacksmith vs Dagger
- Blacksmith vs Nix
- Blacksmith vs Rust
- Blacksmith vs Ansible
- Blacksmith vs Refact
- Blacksmith vs Restate
- Blacksmith vs RubyMine
- Blacksmith vs Soketi
- Blacksmith vs SonarQube
- Blacksmith vs Sourcegraph
- Blacksmith vs OpenEBS
- Blacksmith vs Rancher
- Blacksmith vs Longhorn
- Blacksmith vs Podman
- Blacksmith vs Scaleway
- Blacksmith vs DigitalOcean
- Blacksmith vs Packer
- Blacksmith vs Crossplane
- Blacksmith vs Dokku
- Blacksmith vs Encore
- Blacksmith vs Fastly
- Blacksmith vs Google Cloud Platform
- Blacksmith vs K3s
- Blacksmith vs Flux
- Blacksmith vs Vagrant
- Blacksmith vs Kustomize
- Blacksmith vs minikube
- Portworx vs WarpBuild
- Portworx vs Depot
- Portworx vs Namespace
- Portworx vs Earthly
- Portworx vs Nx Cloud
- Portworx vs OpsLevel
- Portworx vs Garden
- Portworx vs ConfigCat
- Portworx vs Dagger
- Portworx vs Nix
- Portworx vs Rust
- Portworx vs Ansible
- Portworx vs Refact
- Portworx vs Restate
- Portworx vs RubyMine
- Portworx vs Soketi
- Portworx vs SonarQube
- Portworx vs Sourcegraph
- Portworx vs OpenEBS
- Portworx vs Rancher
- Portworx vs Longhorn
- Portworx vs Podman
- Portworx vs Scaleway
- Portworx vs DigitalOcean
- Portworx vs Packer
- Portworx vs Crossplane
- Portworx vs Dokku
- Portworx vs Encore
- Portworx vs Fastly
- Portworx vs Google Cloud Platform
- Portworx vs K3s
- Portworx vs Flux
- Portworx vs Vagrant
- Portworx vs Kustomize
- Portworx vs minikube
