Scoped, measurable, reversible
Start with a 6–8 week pilot on one or two projects.
We agree the success criteria with you before it starts.
Pilot terms
Scope
- 6–8 weeks
- 1–2 projects
- 1–3 AI employees
- Start at L1 · Supervised
- Success criteria agreed up front
You provide
- A server or VM, or we host a dedicated instance
- Jira users for the AI employees
- A Slack channel
- GitHub App access for the AI Developer
- A reviewer team
We measure
- Share of tickets reaching an accepted pull request
- Review time per pull request
- Access requests handled correctly
- Policy violations, target zero
- Sign-off by your security lead
Commercials: talk to us.
In the pilot
What a pilot covers.
-
AI Developer
Takes a Jira ticket assigned to its own account and posts a plan. A named person approves the plan before any code is written.
-
Atlassian access manager
Handles access requests in Jira and Confluence: groups, product access and Confluence space permissions. Changes are proposed as a list, approved by a person, then applied and verified.
-
Dedicated instance in the EU
A dedicated Polis-operated instance in the EU: one customer per server, never shared.
Book a demo
See it on your own workflow.
A 30-minute call: about 15 minutes of live product, including the pause-all switch, then your questions. Bring your CISO if you like.
What we show
- Roles that can’t overreach, with step-up for sensitive actions
- A model provider locked to a data class
- Approvals by a named person, in Slack or the panel
- The pause-all switch