Hi everyone,
We've changed the Marketplace prices of our two apps, Cost Slasher for Jira and Sentinel Vault for Confluence, and the new tables show on both listings from 27 October 2026. The price table on each listing has the amounts. What I'd like to do here is describe the shape of the change, including the part that goes the other way, and then walk through what Atlassian's billing rules mean for anyone whose app price changes, since those rules decide more of your bill than any table does.
Disclosure: I work at LeanZero, which built both apps.
What changed, in shape
Cost Slasher used to have three rate bands that stepped down as a site grew, and it now has one flat rate for each user at every size. For a site with up to roughly 22,700 Jira users the new rate works out lower than the old bands did. Very large sites should check the new table, though, because the old bands kept dropping at the top end and the flat rate doesn't, so above that size it can come out higher than before. I'd rather say that here than have someone find it on a renewal quote, so if your Jira site is that big, please read the new table before your next renewal and look at the price override I describe in the next section.
Sentinel Vault went from four bands to two: one rate up to 250 users and a lower one above that. Its new rate is lower than the old one at every size, so there's no crossover to watch for on the Confluence side.
What to check when an app's price changes
The first thing I'd check is which user count your app is actually billed on, because it's often not the one people expect. Atlassian's Marketplace licensing page says to "purchase the license tier that matches the number of users you have licensed for your host product", and that cloud apps "naturally match the tier of the host product within the cloud site" and "are unable to exceed the host product tier". So Cost Slasher's tier follows your licensed Jira users and Sentinel Vault's follows your licensed Confluence users, and how many people open the app day to day doesn't change it. If you run Jira Service Management on the same site, the same page says "If you have both Jira and Jira Service Management licenses, you must purchase the app license that matches the highest user tier." If you're comparing the old and new tables, compare them at that tier.
The second is timing. The same page says Marketplace partners "are able to change prices for their apps every 30 days", and that Atlassian "highly recommends" partners tell their existing customers about a change, which is part of why I'm writing this. When a price goes up, the page says "you will have a 60-day price override you can use to pay the lower price when you renew or purchase", as long as you're on the same product edition and the quote is created before the override date, which is 60 days from the price change. Atlassian's partner documentation words the condition as staying on the same user tier. As I read it, that's the window that matters for a large Cost Slasher site, so if an annual renewal is coming up, I'd ask for the renewal quote early rather than wait for the renewal date.
The third is how monthly and annual subscriptions are counted, since they no longer behave the same way. Atlassian's announcement on maximum quantity billing moved monthly subscriptions for Jira, Confluence, Jira Service Management and Marketplace apps to billing on the maximum number of seats active in the billing period, with the transition done by October 2025. The same post says "annual subscriptions are currently unaffected." The support article How maximum quantity billing works puts it as "Your bill is based on the maximum amount of users you have throughout your billing period." In practice, if your Jira or Confluence user count went up and came back down inside one month, a monthly app bill follows the peak, while an annual one doesn't work that way today. You can see where you stand before the invoice arrives: in admin.atlassian.com, go to Billing, find the subscription and select Manage, and the subscription details page shows the billed user quantity and the next bill estimate.
Putting those together, my suggestion before any renewal is to open the price table on the listing, find your own host product tier, and read both the monthly and the annual figure there, rather than relying on an older quote. The tables are on the Cost Slasher listing and the Sentinel Vault listing.
If you'd like to see the Confluence app first
For anyone who'd like to see the app before reading its table, I'd point you to two short episodes we've made, presented by Elzi, who is a cartoon presenter with a synthetic voice. They're recorded in the real apps on a demo site, and each one shows Confluence's own behaviour before the app comes in. The first episode is about approvals, and it shows an approval pinned to the exact version that was approved and, with the space set to Revert, an unapproved edit to an approved page being discarded. The second episode is about deleted pages, and it shows that after a page is purged, the Activity tab in the space settings still lists who asked for approval and who approved which version. I should be clear that the app isn't a backup, though, and it doesn't bring the page back.
I'm curious how you handle this on your own sites. When an app you rely on changes its price, do you check the new table at your host product's tier before the renewal, or is the invoice usually where you first notice it?
