Skip to main content
Blacksmith lists $0.004 per minute for its 2-vCPU Ubuntu x64 runner and includes 3,000 x64 2-vCPU minutes per organization per month. For an organization using only that runner, a zero-priced tier followed by a paid tier models the compute charge without a separate subscription fee.
Blacksmith Ubuntu x64 and Ubuntu ARM cards with the 2-vCPU option selected, showing $0.004 and $0.0025 per minute, free-minute text and add-ons.

Blacksmith's complete Ubuntu runner comparison with 2 vCPU selected. Only Ubuntu x64 at standard rates is modeled. Captured November 18, 2026. Source: Blacksmith's official pricing page, linked below.

View the original pricing page. Scope: Pay-as-you-go compute for one organization using only standard 2-vCPU Ubuntu x64 runners. Not modeled: Mixed runner families or sizes, flex scheduling, enterprise terms, storage, caching and static IP add-ons, any promotional discounts and taxes.

Pricing profile

What Blacksmith charges

Design takeaways

  1. Give the allowance to the organization. A per-repository subscription would multiply the published 3,000-minute allowance. Keep repository as event context, with one billing customer and one subscription for the organization. See the published terms.
  2. Separate runtime from rating. Use the provider-equivalent billed quantity, not the number of jobs or raw elapsed time. Do not infer how partial minutes are rounded from a per-minute sticker price. See the published terms.
  3. Model a single denomination before mixing runners. The x64-only subset avoids conversion. A multi-runner model needs a shared normalized pool rather than a fresh allowance on every meter. See the published terms.

How Blacksmith’s pricing maps to Flexprice

Configure the metered subscription

These examples are illustrative. Replace example IDs with IDs returned by your Flexprice environment. Create a metered feature with POST /features:
Create the plan with POST /plans:
Create the usage price with POST /prices. Use the returned meter ID, not the feature ID. The USD price bills at the end of each period:
Send all eligible rated minutes before the monthly allowance. The graduated tier prices the first 3,000 at zero and applies the paid rate only above that. Do not subtract free minutes upstream or grant a second allowance. Create one customer for the account. If you configure a metered entitlement, make it unlimited so it does not cap the priced usage. Start the subscription with POST /subscriptions:

Send finalized usage

Set external_customer_id to the external ID of the same customer used on the subscription. The event uses integration-defined properties, not a provider response:
Use finalized gross runner minutes for eligible standard jobs before deducting free minutes. Use the provider’s billing quantity or a reconciled equivalent. The cited rate does not establish a partial-minute rounding algorithm. Align the subscription period to the applicable monthly allowance period; examples assume complete months. Keep the same event ID and original timestamp when retrying. Do not emit both individual records and an interval total covering the same usage. Aggregate before rounding currency.

Worked bill

Of 4,250 rated minutes in one organization-month, 3,000 are included. The remaining 1,250 × $0.004 = $5.00. At 3,001 minutes only one minute is paid ($0.004 before currency rounding).

Pricing sources

Pricing checked on 2026-11-18. Recheck the source before implementing. This is illustrative configuration, not a recreation of a full provider invoice. Usage-based pricing recipe