2AYE
Plans for your team

Find the right starting point.

From a first integration to an enterprise rollout, we will help you agree the right scope and support.

Pricing is agreed per customer. Talk to us.

Plan your evaluation

Start with one workflow.

We will agree which systems to connect, what an agent may do, who approves sensitive actions and how your team will evaluate the result.

Your integration

Choose the test resources, identity requirements and support your team needs.

Your rollout

Review security, integration responsibilities and acceptance results before production use. Every action still needs valid authorization at its destination.

Explore the product family
BEFORE AN ENGAGEMENT BEGINS

Know what you will evaluate.

Use these items to agree a statement of work. Deliverables, access, timing and price are confirmed during scoping.

Bring one workflow

  • Name its owner, agent, exact action and protected system.
  • Identify a test environment, permitted test data and the receiver owner.
  • Confirm source access and identity or device participation where needed.

Agree the evidence

  • A scoped integration and responsibility map.
  • Observed permitted and refused actions, with applicable replay, expiry and recovery checks.
  • A review of destination evidence, unresolved outcomes and the next-stage decision.

Set commercial boundaries

  • Agree integration effort, environment, support and evidence handling.
  • Confirm the pricing basis and exclusions in the statement of work.
  • Live payments, managed key custody, physical-device acceptance and independent validation need separate scope.

A request does not provision a trial, guarantee a delivery date or establish production availability.

Find your starting point

Choose the boundary you need to govern first.

Choose the workload and adoption stage. 2AYE separates identity scale from consequential actions so teams can evaluate the right commercial unit.

What are you governing?
Where are you today?
Recommended starting point

Developer evaluation

Run one synthetic protected action and inspect execution and refusal evidence before discussing commercial scope.

Start with the quickstart

Guidance only. Plan names are confirmed. Fees, capacity and entitlements require agreement until deployment scope and currently available capabilities are confirmed.

From evaluation to purchase

Choose a clear next step.

These are engagement paths, not confirmed production plan entitlements.

Developer evaluation

Run the developer quickstart with synthetic data. Verify an allowed action, parameter mismatch, and replay refusal.

Run the quickstart

Paid pilot

Agree one protected workflow, integration responsibilities, fees, and measurable acceptance criteria before work begins.

Scope a pilot

Production review

Review enforcement, recovery, capacity, key custody, and operating ownership. Production availability requires deployment verification.

Review production requirements

Enterprise review

Bring deployment, procurement, retention, support, and data-boundary requirements. Confirm offered capabilities in writing.

Discuss enterprise scope

What determines a quote?

Identity scope: monthly active users, customer organizations, applications, and federation requirements. Authorization scope: governed agents, protected tools, evaluation volume, environments, and evidence retention. Billing units, included usage, overages, and support terms must be agreed before purchase.

What stays protected?

Parameter binding, single-use authority, tenant isolation, and required audit evidence remain authorization requirements at every commercial tier.

Prepare your enterprise review

Bring your identity provider, protected services, expected usage, deployment boundaries, retention needs, and operational owner. We will agree an acceptance checklist and document available capabilities before contracting.

Review security controlsDeployment guidanceCapability statusContact 2AYE

Startup pricing enquiries · Nonprofit pricing enquiries