Workflow Run Policy
Hosted workflow runs, run counting, included runs, BYOK behavior, abnormal usage controls, and future usage billing.
Overview
This policy explains how Edgaze counts hosted workflow runs, when included runs apply, when BYOK may be required, and how Edgaze may respond to abnormal usage.
Edgaze currently implements 10 included hosted runs per purchased workflow and 10 builder test runs before user-supplied keys may be required. Admin/demo flows may have separate internal rules.
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.
Included run allocation
Edgaze currently implements 10 included hosted runs per purchased workflow and 10 builder test runs before user-supplied keys may be required. Admin/demo flows may have separate internal rules.
When a Run Counts
Terminal execution states
Run tracking is based on workflow run records and terminal execution states. Runs that reach terminal states such as completed, failed, timeout, or cancelled may count against limits when the run has started and completed tracking.
Failed or blocked starts
Validation or access failures that prevent execution from starting should not be described as successful hosted runs, but Edgaze may still record attempted, failed, or diagnostic events for security, debugging, or abuse prevention.
BYOK Mode
When BYOK applies
After included hosted runs are exhausted, workflows using AI/provider nodes may require the customer or user to supply supported API keys. BYOK means the user provides provider credentials and bears provider-side costs, rate limits, account restrictions, and terms.
Provider responsibility
Edgaze handles orchestration but does not control third-party provider charges, availability, or policy decisions in BYOK mode.
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.
Usage Billing
Additional hosted runs or usage-based billing may be introduced where available or if enabled. Unless Edgaze offers such a feature for the applicable Product or account, users should not assume unlimited hosted runs are available for purchase.
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 Limits
Edgaze may change run limits for future purchases, future Products, creator tiers, product categories, or abuse controls. Existing purchases may retain their original allocation where technically and commercially feasible, unless policy enforcement, fraud, abuse, or legal requirements require otherwise.
Related Policies
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 pay, what they buy, how creator shares are attributed, and how Stripe supports Edgaze marketplace payments.
How Edgaze infrastructure cost estimates guide creator pricing without becoming a separate creator earnings deduction.