PILOT PROGRAM
Scoped pricing for design partners
Aegisora is validating enterprise runtime-control workflows with design partners. We do not currently offer self-service paid plans or online checkout.
Test workspace
Early access
No paid plan, no checkout
For evaluating your first agent action in a test workspace.
- DECISIONS
- Allow, Block, Escalate
- DEFAULT
- BLOCK
- EVIDENCE
- Hash per decision
Design partner pilot
Scoped
Agreed in writing before data is connected
For teams testing a policy decision before a consequential tool action.
- WORKFLOW
- Agreed
- ENVIRONMENT
- Agreed
- TERM
- Agreed
Production
Not available yet
Hosting and service levels not verified
Production hosting, customer SSO and full audit operations are not yet verified.
- HOSTING
- Not verified
- SSO
- Planned
- AUDIT OPS
- Not verified
Pilot commercial scope
Any paid pilot must be scoped and agreed in writing before customer data or production systems are connected. The proposal should specify workflow, environment, term, support boundaries, retention, security prerequisites, success criteria, and rollback.
Price, tax treatment, hosting, service levels, and production availability are not published or represented as established offers. There is no Stripe checkout or automated subscription billing today.
What a pilot proposal specifies
Workflow
Agreed in writing
Environment
Agreed in writing
Term
Agreed in writing
Support boundaries
Agreed in writing
Retention
Agreed in writing
Security prerequisites
Agreed in writing
Success criteria
Agreed in writing
Rollback
Agreed in writing
Compare plans
Statuses reflect what is built and tested today. Planned means not yet verified, and no complete audit-ledger claim is made.
Runtime decisions
Access and identity
Evidence
Commercial terms
Questions about pricing?
Talk to the team about pilot scope, security prerequisites and success criteria.
FAQ
Can I try Aegisora today?
Yes. You can create a test workspace and evaluate your first agent action. There is no paid plan and no online checkout today.
Is pricing published?
No. Price, tax treatment, hosting, service levels, and production availability are not published or represented as established offers.
How does a paid pilot work?
Any paid pilot must be scoped and agreed in writing before customer data or production systems are connected. The proposal specifies workflow, environment, term, support boundaries, retention, security prerequisites, success criteria, and rollback.
Is customer SSO available?
Not yet. A provider boundary is documented, but customer SAML/OIDC and automated provisioning are not configured or verified.
Is production hosting available?
Not yet. Production hosting, customer SSO, and full audit operations are not yet verified.
Ready to get started?
Create a test workspace, or talk to us about a scoped enterprise pilot.