​

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.

​

Stage the rollout

​

Review the public evidence

Before each expansion, review:

• Feature status for the authoritative maturity label;
• Current-behavior manuals for permissions, limits, failure states, and recovery paths;
• Security and data handling for implemented controls and explicit certification boundaries;
• Model providers and BYOK for the separate provider billing, retention, training, and residency contract; and
• Rate limits 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

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. 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 records timestamped public observations. It is hosted separately from the application, displays stale evidence as Unknown and establishes no SLA. Approved spend controls distinguish result admission from provider charges and source-candidate acceptance.