Workflow Run Policy
Per-run hosted workflow execution, BYOK behavior, funding sources, and abnormal usage controls.
Overview#
Workflow runs use Edgaze orchestration. Each successful run settles at its displayed price. Buyers fund current runs from a wallet or a matching workflow bundle; the app and API are trigger channels, not separate funding sources.
This policy covers execution rules, BYOK behavior, and abuse controls. For funding, pricing, failure billing, and refunds, read the Billing guides.
Hosted Runs#
What counts as a run#
A hosted run is a workflow execution through Edgaze runtime infrastructure or orchestration. A run may include multiple nodes, prompts, model calls, tool calls, file operations, API calls, retries, validations, and output generation steps.
Per-run charging#
Each successful hosted run charges the buyer's chosen funding source at the pinned displayed price for the workflow version being run. There is no included-run quota bundled with per-run purchases. Demo and builder test runs are always free.
Input envelope#
Workflows define a maximum input spec (size, pages, tokens, or equivalent). Inputs above the envelope are rejected at trigger before any charge or reservation. Within the envelope, the displayed price is fixed.
When a Run Counts for Billing#
Successful runs#
A run counts as a billable success when it completes successfully. You are charged the displayed price; the creator earns 80% of margin.
Failed, cancelled, or compute-limit-stopped runs#
Ordinary failed and cancelled runs are not charged and do not pay creator earnings. A run stopped at the compute limit may retain already-consumed compute while the margin charge is released. Read When Runs Fail.
Validation or access failures#
Validation or access failures that prevent execution from starting do not produce successful hosted runs. Edgaze may still record attempted, failed, or diagnostic events for security, debugging, or abuse prevention.
BYOK Mode#
When BYOK applies#
Plus subscribers may save provider keys in API Vault. Non-hosted runs charge creator margin plus $0.002 for Edgaze orchestration. The external provider bills the owner of the connected key.
Provider responsibility#
Edgaze handles orchestration but does not control third-party provider charges, availability, or policy decisions in BYOK mode. Read BYOK.
Provider Dependencies#
Hosted runs and BYOK runs may depend on model providers such as OpenAI, Anthropic, and Google where configured, as well as external APIs selected by creators or users. Provider errors, rate limits, safety systems, policy changes, or outages may affect execution.
Abnormal Usage#
Edgaze may limit, block, rate-limit, suspend, or require BYOK for abnormal, abusive, high-cost, fraudulent, automated, or security-sensitive usage patterns.
Changes to Run Policy#
Edgaze may change run policy, funding rules, accepted input limits, or abuse controls prospectively. Existing bundle balances and wallet entries remain subject to the terms in effect at purchase unless policy enforcement, fraud, abuse, or legal requirements require otherwise.
Related Policies#
Was this useful?
Your response helps us improve the documentation.
Related policies
Back to Legal & Trust CenterThe core platform terms that govern access to Edgaze, including product usage, publishing, marketplace transactions, hosted AI runs, platform limitations, and legal responsibilities.
How customers fund runs via wallet and bundles, how Stripe and Stripe Connect support checkout and creator payouts, and how legacy unlock purchases coexist with per-run billing.
How the hosted compute estimate affects the price buyers see, without reducing creator margin earnings.