Infrastructure Cost Estimation
How Edgaze estimates hosted compute at the input envelope maximum to set buyer displayed price, without deducting compute from creator earnings.
Overview#
Edgaze estimates hosted compute at the input envelope maximum for each workflow version. That estimate feeds the compute displayed portion of the buyer's per-run price. It is pricing guidance for creators, not a separate fee deducted from creator margin earnings.
Read Publish and Price and the Billing guides for how estimates combine with creator margin at checkout.
What the Estimate Is#
Compute at envelope max#
During publishing, Edgaze analyzes the workflow graph and the creator's maximum input spec (file size, pages, tokens, or equivalent). The estimate reflects likely model, API, compute, and orchestration cost at that maximum allowed input, not at every possible smaller input.
Buyer displayed price component#
Displayed price = creator margin + compute displayed. Compute displayed is derived from the envelope-max estimate. Within the envelope, the buyer sees one fixed price; Edgaze absorbs small within-envelope variance.
BYOK adjustment#
For BYOK (Plus) runs, compute displayed is replaced by a flat orchestration fee. Provider token cost is on the user's API key. Read BYOK.
What the Estimate Is Not#
The infrastructure estimate is not:
- A second platform fee on creator margin.
- An automatic deduction from creator earnings (creators earn 80% of margin only).
- A Stripe fee.
- A guarantee of actual runtime cost on every input size within the envelope.
- A guarantee that a workflow will remain profitable at a selected margin.
Relationship to Marketplace Fees#
The standard marketplace fee is 20% of creator margin, not 20% of compute. Compute is included in what the buyer pays as part of the displayed price. Infrastructure estimates help creators decide whether their margin is sustainable given hosted compute at envelope max.
Why Estimates Matter#
Hosted workflow economics#
AI workflows can involve multiple model calls, image generation, embeddings, tool calls, and third-party APIs. A low margin may be commercially unhealthy if envelope-max compute is expensive to serve.
Pricing decisions#
Creators should set margin using the envelope-max compute estimate alongside product value, likely demand, refund risk, support burden, and the 80/20 margin split.
Changes and Accuracy#
Estimates may change when provider pricing, model routing, retry behavior, workflow structure, failover policy, usage patterns, or platform infrastructure change. Edgaze may update estimation logic without changing what you were charged for past runs.
Related Policies#
Related policies
Back to Legal & Trust CenterPer-run hosted workflow execution, BYOK behavior, funding sources, and abnormal usage controls.
How Edgaze platform fees apply to creator margin on successful per-run sales, separate from compute recovery.
Minimum and maximum price rules for prompt products and per-run workflow margin on Edgaze.