> ## Documentation Index
> Fetch the complete documentation index at: https://evalgate.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Production adoption

> A staged, evidence-based path for piloting EvalGate without assuming unverified availability or compliance guarantees.

# Production adoption

EvalGate's hosted platform is **Beta**. This guide helps a team
adopt the live parts of the platform without treating an unfinished
surface as a general-availability promise.

> [!WARNING]
>
> EvalGate does not publish a default uptime SLA, SOC 2 certification, universal
> data-residency commitment, or guaranteed support-response time today.
> Governance templates are product controls, not certifications. Any negotiated
> enterprise term must appear in the customer's signed agreement.

## Stage the rollout

| Stage | Scope | Exit evidence |
| - | - | - |
| Repository setup | One repository, non-production organization, scoped API key | Correct repository/branch/root, key owner, revocation test, no cross-org access |
| Deterministic gate | One existing test command and reviewed baseline | Passing baseline, deliberate regression failure, CI artifact tied to an exact commit |
| Trace and evaluation pilot | One bounded staging workflow | Successful and failed traces, reviewed cases, explicit provider/parser/budget failures |
| Runtime controls | One governed model or agent action path | Allowed and denied policy tests, approval proof, policy snapshot, audit evidence |
| Release use | One non-critical release decision with a human owner | Rollback plan, feature-status review, incident path, signed or retained report evidence |
| Broader adoption | Additional teams and repositories | Tenant/access review, data-flow review, load evidence, named owners, commercial agreement |

## Review the public evidence

Before each expansion, review:

* [Feature status](https://evalgate.com/docs/platform/feature-status.md) for the authoritative maturity label;
* [Current-behavior manuals](https://evalgate.com/docs/platform/feature-manuals.md) for permissions, limits,
  failure states, and recovery paths;
* [Security and data handling](https://www.evalgate.com/security) for implemented
  controls and explicit certification boundaries;
* [Model providers and BYOK](https://evalgate.com/docs/platform/model-providers-byok.md) for the separate
  provider billing, retention, training, and residency contract; and
* [Rate limits](https://evalgate.com/docs/platform/rate-limits.md) for client backoff and usage behavior.

Source tests, routes, or UI screens are evidence inputs, not availability by
themselves. When a public document and the runtime disagree, use the more
restrictive behavior and report the mismatch.

## Define ownership before a release gate

Assign people or teams for:

* API-key issuance, scope review, and revocation;
* repository and baseline approval;
* provider credentials, data policy, and spend limits;
* evaluator calibration and failure triage;
* CI override and production rollback decisions; and
* incident communication and evidence retention.

EvalGate records decisions and evidence; it does not replace your change
management, incident response, or provider contract.

## Large organizations

| Adoption dependency | Public availability |
| - | - |
| DPA, dated subprocessor roster, processing-region schedule | Not published; request reviewed contractual documents before sending production data |
| Service status and incident history | [Independent public availability sampling](https://evalgate.github.io/status/); timestamped checks, no SLA or retrospective incident-history claim |
| SLA, SOC 2, residency and support-response guarantees | No default commitment or certification |
| Organization SAML/OIDC | Source candidate; live Okta/Entra acceptance is not verified |
| SCIM and single logout | Unsupported |
| Result budget and judge/Copilot estimates | [Source candidate](https://evalgate.com/docs/platform/spend-controls.md): 10,000-result default and managed provider preflight; exact deployed acceptance remains required. Provider charges are separate |

An enterprise sales conversation does not make any of these dependencies
available. Keep the initial pilot deterministic and bounded while reviewing
actual deployment and contractual evidence.

The four plans share the published overage rate; an included allowance is not a
spending limit. Review the active organization result budget and separate provider
charges. Organizations
with more than 5 million monthly results, multiple business units, procurement or
invoicing requirements, or negotiated security and support terms should use the
Strategic Enterprise path on the [pricing page](https://www.evalgate.com/pricing).

Strategic Enterprise is a commercial review path, not a promise that every
requested control, certification, region, SSO configuration, SLA, or support tier
already exists. The agreed scope, volume schedule, rollout plan, and obligations
must be documented before adoption.

## Report a gap

Send security and production-adoption questions to `team@evalgate.com`. Include
the organization, surface, exact route or command, timestamp, request ID, and the
expected versus observed result. Do not include API keys or provider secrets.

[Independent service availability and probe history](https://evalgate.github.io/status/) records timestamped public observations. It is hosted separately from the application, displays stale evidence as Unknown and establishes no SLA. [Approved spend controls](https://evalgate.com/docs/platform/spend-controls.md) distinguish result admission from provider charges and source-candidate acceptance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.