AutonomyOps — Evaluation Agreement Overview

INTERNAL — SALES USE ONLY For use in active pilot conversations (Stage 3 onward in the commercial motion). Send to prospects after technical validation. Do not share publicly.

The standard pilot offer

Term

Value

Duration

90 days

Node scale

Up to 10 orchestrator-enrolled nodes

Cost

$0 under signed Evaluation Agreement

What the EA includes

Usage rights, NDA, mutual IP protection, no publicity rights

Conversion trigger

Day 75 — commercial discussion initiated by AutonomyOps

What is not included

Provider rights, third-party use, sub-licensing

The pilot is a commitment device, not a free tier. It has a defined end date, a bounded scope, and a structured conversion path. The EA is a 3-page agreement. It protects both parties and unlocks orchestrator access for the evaluation period.

What the pilot covers

During the 90-day evaluation, the enrolled nodes have full access to the orchestrator tier:

  • Fleet rollout — phased policy propagation across enrolled nodes with per-node acknowledgment tracking and blast-radius control

  • Centralized audit — tamper-evident event log aggregated across all enrolled nodes; queryable and exportable for compliance review

  • Policy versioning and rollback — last-known-good rollback across the fleet; per-node activation state tracking

  • Relay-aware propagation — policy delivery to nodes operating in degraded or intermittently-connected environments

  • RBAC — role-based access control for operator teams managing the fleet

CE remains active on each node throughout the pilot and provides the same per-call enforcement and local WAL it always has. The orchestrator extends that enforcement with coordination, centralized state, and fleet-level visibility.

What the pilot does not cover

The pilot is scoped to validate the enforcement capability and orchestrator relationship — not to simulate a full production deployment at zero cost.

  • Node count beyond 10 — additional nodes are commercial, not pilot; the scope boundary is a commitment test, not a technical limitation

  • Provider or partner rights — using the orchestrator as the governance layer for a product or managed service offered to third parties requires a separate commercial agreement

  • Indefinite extension — the pilot does not convert to a free tier; Day 75 is the commercial trigger; Day 90 is the end date

Success criteria for the evaluation

The pilot is designed to produce two concrete outcomes:

  1. One fleet rollout completed — policy update propagated to all enrolled nodes; per-node activation states confirmed; rollout record written to centralized audit

  2. One centralized audit export — tamper-evident event log covering all enrolled nodes for the evaluation period; exportable for any internal or third-party review

These two outcomes create the evidence a team needs to justify production expansion internally. By Day 75, the conversation is about production node count, not about whether the system works.

Day 75 — the commercial conversation

At Day 75, the pilot data anchors the production discussion:

  • How many rollouts completed; how many nodes enrolled

  • Centralized audit volume — governed events recorded during the evaluation

  • Any rollback events or policy updates during the pilot — these are proof points

The production commercial terms are scoped to the team’s actual deployment — enrolled node count, annual commitment. Pricing is per enrolled node, minimum annual commitment. The pilot nodes roll into the first commercial tier at conversion.

The pilot cannot be extended as a substitute for this conversation.

How to get started

  1. If you have installed CE and run autonomy demo validate: You have established the enforcement baseline. The next step is a 45-minute technical validation call to confirm the orchestrator tier is the right path for your production use case.

  2. If you are ready for the pilot proposal: Email info@autonomyops.ai with the subject line “Fleet deployment inquiry.” We will send the EA within one business day. The pilot begins at EA signature.

  3. If you have questions about scope: The bounded scope is a structural decision, not a negotiating position. If your evaluation requires more than 10 nodes, that is a production deployment — and we can discuss commercial terms directly.

AutonomyOps · autonomyops.ai · Technical Alpha See also: Customer Explainer · customer-explainer.md See also: Fleet Boundary Diagnostic · fleet-boundary-handout.md