---
title: Failover
description: When Edgaze switches to a backup model, your price stays the same.
source: https://www.edgaze.ai/docs/billing/failover
section: billing
---
# Failover

> When Edgaze switches to a backup model, your price stays the same.

## Overview

When a primary model degrades, Edgaze can route the run to an equivalent model on another provider. You pay the pinned displayed price only. Any extra compute cost is absorbed by Edgaze, not added to your bill.

Creators can disable failover. When off, degradation causes the run to fail instead of switching models. You are not charged margin on that failure.

## Failover enabled

The run starts against the primary model. If degradation is detected, execution routes to a fallback provider. Your displayed price does not change. Edgaze covers the cost difference internally.

On success after failover, the creator still earns 80% of their margin. You pay the same pinned price as a run that never failed over.

## Failover disabled

If the creator opted out in publish settings, degradation causes run failure. Margin is not charged. Compute absorption follows the standard failure policy.

## Special cases

- **Failover then failure:** No margin charge. Absorbed compute includes the failover segment.
- **BYOK graphs:** Provider keys bill tokens to your account. The orchestration fee still applies per BYOK policy.
- **API and bundle paths:** Same failover billing rules as UI wallet runs.

## What you see in Edgaze

- Publish settings: failover toggle for creators
- Buyer UI: no visible price change when failover occurs internally
- Failure with failover off: standard failure message, no margin charge

## Related policies

- [Publish and Price](/docs/billing/publish-and-price)
- [When Runs Fail](/docs/billing/when-runs-fail)
- [What You Pay For](/docs/billing/what-you-pay-for)
- [Infrastructure Cost Estimation](/docs/infrastructure-cost-estimation)