Evaluate one project, roll out across production teams, or deploy under an enterprise agreement with private infrastructure and review support.
Prove one Jira project can use AI without creating a public-AI exception.
Run production writeback with schema validation and audit export.
Add SSO planning, SIEM integration, onboarding, and priority support.
Private deployment, security requirements, SLA, support level, and contract terms.
You buy fewer blank tickets, fewer manual field cleanups, and a security review path that does not ask for a public-AI exception.
Filled against your project schema. Invalid values are dropped with a reason.
Use a customer-approved model route; no public consumer-AI workflow is required.
Every deployment exposes GET /egress so security teams can verify the boundary.
Live egress proof, boundaries, and deployment facts live on security.html.
Self-service checkout is for Evaluation and Team. Business is a guided production pilot. Enterprise is a signed annual agreement with deployment, support, capacity, and security scope defined up front.
Platform lead validating policy fit with one Jira project and measurable review output.
Engineering or compliance owner reducing issue-writing drag across multiple Jira teams.
CISO or procurement owner needing security review, rollout support, and SLA coverage.
One evaluator project for validating policy fit and schema behavior.
Production writeback, schema validation, audit export, and standard model routes.
For teams that need advanced policies, SSO planning, onboarding, and architecture review.
For buyers that need offline licensing, security-review support, named onboarding, and private deployment.
Self-service billing sends content-free license metadata only. The data plane never contacts the vendor.
| Capability | Evaluation | Team | Business | Enterprise |
|---|---|---|---|---|
| Projects | 1 | Up to 10 | Scoped | Custom |
| Drafts / month | 500 | 10,000 | Higher allowance | Contracted |
| Production writeback | - | ✓ | ✓ | ✓ |
| SSO / SIEM / onboarding | - | Standard | Advanced | Custom |
| Air-gap / offline license | - | - | Review | ✓ |
| Support | Priority | Priority + onboarding | Contractual terms |
| Model route | Evaluation | Team | Business | Enterprise |
|---|---|---|---|---|
| Workers AI | ✓ | ✓ | Optional | Optional |
| Amazon Bedrock | Review | ✓ | ✓ | ✓ |
| Azure OpenAI via gateway | - | Review | ✓ | ✓ |
| Private OpenAI-compatible endpoint | Limited | ✓ | ✓ | ✓ |
| Air-gapped local model | - | - | - | ✓ |
Fixed scope: one Jira project, schema mapping, deployment assistance, shadow drafting, pilot analytics, security review, and final rollout recommendation. Fees can be credited toward an annual agreement.
Infrastructure and model-provider usage are billed by the customer's cloud/provider unless stated otherwise. Additional policy packs, private deployment work, and substantial customization are scoped separately.
Banks, EMIs, crypto with a hard no-public-LLM policy.
Where inference location is a control, not a preference.
Teams bridging Data Center through 2029 with customer-run inference and schema validation.
Where issue text itself cannot leave the perimeter.
No clone required: live egress, playground draft, and before/after on the public site.