
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.
Pricing profile
What Blacksmith charges
Design takeaways
- 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.
- 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.
- 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 withPOST /features:
POST /plans:
POST /prices. Use the returned meter ID, not the feature ID. The USD price bills at the end of each period:
POST /subscriptions:
Send finalized usage
Setexternal_customer_id to the external ID of the same customer used on the subscription. The event uses integration-defined properties, not a provider response:
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
- Blacksmith pricing: Ubuntu 2-vCPU card rate and included minutes.
- Blacksmith billing documentation: Monthly organization allowance in 2-vCPU x64 equivalents.
- Blacksmith usage reporting: Reporting distinguishes billable minutes and raw runtime.

