---
title: Workflow Run Policy
description: Per-run hosted workflow execution, BYOK behavior, funding sources, and abnormal usage controls.
source: https://www.edgaze.ai/docs/workflow-run-policy
last_updated: 2026-03-15
section: legal
---
# Workflow Run Policy

> Per-run hosted workflow execution, BYOK behavior, funding sources, and abnormal usage controls.

## Overview

Hosted workflow runs execute through Edgaze runtime infrastructure. Each run is billed **per successful completion** at the workflow's displayed price (creator margin plus compute displayed at the input envelope maximum). Buyers fund runs from a **wallet**, a **locked bundle**, or the **API** path.

This policy covers execution rules, BYOK behavior, and abuse controls. For funding, pricing, failure billing, and refunds, read the [Billing guides](/docs/billing).

## 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 killed runs

Failed runs do not charge margin and do not pay creator earnings. Cancelled runs before start do not charge. If a run is stopped because it exceeded the compute limit, partial compute charges may still apply while the margin charge is released. Read [When Runs Fail](/docs/billing/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 configure provider API keys in API Vault. BYOK runs charge **creator margin plus a $0.002 orchestration fee** per run. Provider token cost is billed to the user's API key, not Edgaze compute recovery.

### Provider responsibility

Edgaze handles orchestration but does not control third-party provider charges, availability, or policy decisions in BYOK mode. Read [BYOK](/docs/billing/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 doors, envelope rules, or abuse controls for future purchases, future products, creator tiers, or product categories. 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

- [Run a Workflow](/docs/billing/run-a-workflow)
- [Funding Runs](/docs/billing/funding-runs)
- [What You Pay For](/docs/billing/what-you-pay-for)
- [Terms of Service](/docs/terms-of-service)
- [Platform Status and Beta Disclaimer](/docs/platform-status-beta-disclaimer)