Can Flexprice Handle Netlify's Pricing?

Episode 3 of Can Flexprice Handle It? recreates Netlify’s pricing in Flexprice. Netlify bills five usage dimensions on the same invoice: bandwidth, build minutes, serverless function invocations, edge functions and form submissions. Each dimension has its own included allowance, overage rate and metering cadence. The episode builds the setup through the Flexprice MCP server.

How Netlify’s pricing maps to Flexprice

Netlify’s pricing uses	Flexprice setup
Five usage dimensions on one invoice	One metered feature per dimension, each with its own usage charge on the plan
Included allowance per dimension	Entitlements with a usage limit and reset interval for each metered feature
Per-member seat price on the Pro plan	Seat-based pricing, where the subscription quantity is the member count
Overages billed at the account level	Usage charges, which add up usage for the whole customer, separate from the seat quantity

The hard part is the layering. The Pro plan bundles usage allowances into a per-member price, but overages are billed for the whole account. Keeping seats and usage as separate charges on one plan keeps each overage tied to the dimension that caused it.

Building Netlify’s pricing with the MCP server

The episode connects Claude to Flexprice through the MCP server, the same way as the Replit and Cursor episodes. Claude creates the metered features, plans and charges from a description of Netlify’s pricing.

Billing Recipes

Pricing Teardowns

Can Flexprice Handle Netlify's Pricing?

How Netlify’s pricing maps to Flexprice

Building Netlify’s pricing with the MCP server

Build Hybrid Pricing like Resend

​How Netlify’s pricing maps to Flexprice

​Building Netlify’s pricing with the MCP server

​Related recipe

Build Hybrid Pricing like Resend

How Netlify’s pricing maps to Flexprice

Building Netlify’s pricing with the MCP server

Related recipe