Infrastructure Cost Estimation
How the hosted compute estimate affects the price buyers see, without reducing creator margin earnings.
Overview#
During publishing, Edgaze estimates hosted compute for the largest input the workflow accepts. That amount contributes to the fixed price shown to a buyer before a run. It is not deducted from creator margin earnings.
Read Publish and Price for how the estimate combines with creator margin.
What the Estimate Is#
Estimate for the largest accepted input#
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 price#
Displayed price = creator margin + applicable hosted compute. Within the accepted input limit, the buyer sees one fixed price.
BYOK adjustment#
For a non-hosted provider-key mode, hosted compute is replaced by $0.002 for Edgaze orchestration. The external provider bills the connected key owner. 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 a share of hosted compute. The estimate explains the buyer price; it does not reduce creator earnings.
Why Estimates Matter#
Hosted workflow economics#
AI workflows can involve multiple model calls, image generation, embeddings, tool calls, and third-party APIs. The estimate makes the buyer price visible before publication.
Pricing decisions#
Creators should set margin based on product value, likely demand, refund risk, and support burden. Hosted compute is priced separately.
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#
Was this useful?
Your response helps us improve the documentation.
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 per-run workflow margin on Edgaze.