A clause you didn’t write, changing under you
On 17 August 2026, Atlassian began using cloud product data from Jira, Confluence and Jira Service Management to train its AI. That change reaches roughly 300,000 customers. Legal analysts have flagged two things worth your attention: a shift in the controller and processor relationship, and a data-residency gap that regulated firms need to resolve before the date.
If you run an MSP and your ticketing or docs ride someone else’s SaaS, sit with what that means. Client PII, financial detail, the messy context inside a ticket thread, all of it can feed a vendor’s model under terms you never negotiated. You didn’t opt in. A product update opted you in, and left you to work out the compliance fallout.
The blind spot is the vendor, not the AI
This is not an argument against AI. It is an argument against a third party unilaterally changing what happens to your data while it sits on their infrastructure. Channel analysts have started calling this a new compliance blind spot for MSPs, and they are right. When your book of business lives on a platform you don’t control, the platform sets the rules and can rewrite them on a date of its choosing.
Ownership is the whole point. What happens if a vendor flips a switch? On a cloud platform, plenty happens, and you find out after the fact. On a self-hosted single-tenant PSA, nothing flips. The data is on hardware you control. No vendor can mine it for training, because no vendor has it.
How Opentra treats AI
Opentra is a self-hosted, single-tenant PSA. Your tickets, contracts, time and invoices live on your infra. We do use AI, and we are precise about where: Anthropic Claude drafts the narrative in monthly client service reports, and there is an “extract from ticket” helper for scheduled tasks. Both have a deterministic fallback. You choose if and when it touches a workflow, and nothing about it feeds a training set for your data.
That is the difference between AI you invited to do one job and a clause that quietly enlists your client book.
Own the platform, own the terms
Built by a working MSP, running in production at ours. Flat pricing across every tier: Community is free to self-host forever, Pro is $149/mo, Opentra Cloud is $249/mo. No per-seat tax, unlimited techs and client orgs.
If a training clause landing on your inbox made you nervous, that is a good instinct. Read how we handle data on our security page, or run the numbers on pricing.
Your monitoring stays yours. Your client book stays yours too.