...

Atlassian is pushing the majority of customers to Cloud. The 'Data Center' (DC) product line, a clustered edition for large instances, will still be available, but its price will be increasing by 15-180%.

Current/Past Pricing (2020)

We paid $17,500 in 2020 to renew Jira's license.

...

Plugins are not considered here as their costs are dwarfed by the base costs, but increases moving to Cloud can be assumed (e.g. 20% for Tempo Timesheets, 600% for JETI).

Summary: Future Pricing

The three options Atlassian make available to us are:

1. Stay with Server as long as possible, then migrate to DC (option 1).
2. Migrate to DC soon to get ourselves a 'advantaged' (grandfathered) license (option 2).
3. Migrate to Cloud (option 3). Cloud may not be possible for us due to GDPR compliance and lack of certain plugins. See discussion below.

...

Our base spend (Jira + Confluence) will thus increase 10x or 11x from its current $30,600

Recommendations

The least disruptive move would be to move to Data Center, assuming we can afford it (the 'DC, after Feb 1, 2021' column). Moving early will lock in some discounts. Just be aware that DC is an annual subscription, not a perpetual license like Server, and that DC won't last forever (see blog post Betting on Atlassian DataCenter?). As happened with Server, DC is likely to undergo constant price increases to 'squeeze' larger customers onto Cloud.

...

This "lock down and wait" approach can be realised in 4 steps:

Step 1: Pay Atlassian one more time for upgrading Jira's 2,000 user license to 10,000 users

One more upgrade buys us license slot headroom beyond 2022:
 
Do not pay for further Server renewals. Atlassian haven't added any serious feature improvements in years, and certainly won't do so now. Bug fixes are nice, but after 18 years of development there aren't many bugs left that affect us and that Atlassian are willing to fix. Atlassian support on its own isn't worth paying for.

On the other hand, we do need ongoing security patches if we are to run a public-facing instance. Which is why:

Step 2: Move customer support to an external Cloud-managed system

Implement a new public-facing system for customer support. Perhaps Jira Service Desk (JSD) Cloud where non-agents are free, or ServiceNow.

...

Moving customer support to JSD Cloud means that non-linear growth isn't a problem: we don't pay for customers, only for 'agents'. Moving our customers to a Cloud product should be a net win for security.

Step 3: Lock down Jira to just employees

Jira averages about 1 'critical' security vulnerability every 6 months (generally a CSRF). If we stop paying Atlassian maintenance fees, or run Jira beyond 2024, we need to mitigate security vulnerabilities ourselves, which we can only realistically do by locking down Jira. Either:

...

We could further lock down Jira by adding a WAF like mod_security or Cloudflare, so that security vulnerabilities we learn of can be mitigated at the HTTP layer.

Step 4: Look for alternatives

With customers out of the picture and Jira locked down to employees, we can take our time evaluating Jira Server alternatives.

...

Also, in 5 years time there may be decent competitors. I've been impressed with https://wiki.js.org and xwiki.org as Confluence alternatives. Good Jira alternatives are much scarcer, but there is Youtrack, Gitlab and a host of SaaSes (Asana, Clubhouse). Even Request Tracker is looking less 90s these days and may be an option. I and others will be keeping tabs on alternatives via https://www.goodbyeserver.org/

Future Pricing Calculations

We now show how the numbers above are derived. Note: the primary source of calculations is a spreadsheet, which I unfortunately cannot publish due to containing Partners-only information:

How many users?

Before considering costs, we need to know how many users we expect to cater for in future.

Jira

Confluence

Jira has a 2000 User license, with 1463 license slots used as of 29 Oct 2020. License use is increasing each year (despite automatic deactivation after 6 months' inactivity).   This shows that if current growth continues we will hit our 2000-user license limit in early-2022, and will be forced into Jira's next user tier, 10,000 users. Expand title Source... jira=> -- Depends on https://github.com/redradishtech/jira-interesting-sql-queries/blob/master/active_users.sql jira=> select year, new_users, sum(new_users) over (order by year) AS total_active from (select to_char(created_date, 'YYYY') AS year ,count(*) AS new_users from queries.active_users group by 1 order by 1 asc) x;

Confluence is also on a 2000 user license, with 650 license slots used as of 29 Oct 2020. Growth appears linear. No 'deactivate inactive user' process is being run yet.

Option 1: stick with Server as long as possible, then move to Data Center

2021

We are on 'advantaged' plans, and we know price increases are coming for 'advantaged' plans on 2/Feb/2021.

...

• Renew Jira till Jul 4, 2021, for $2,600.
• Renew Confluence till Feb 2022, for $2,000.
• Renew plugins, for $2,773.

2022

Jira will be due for renewal in May 2022, and Confluence in Aug 2022.

...

• $50,400 for Jira (2 x the $25,200 annual price for the 2000-10,000 user tier)
• $30,200 for Confluence (2x the $15,100 annual price for the 502-2000 user tier)

2023

No costs, as we paid for this year in advance.

2024+

After 2/Feb/2024 all support ends, and we'd have to purchase Data Center licenses annually, at the 'New Atlassian list price' from the future DC pricing tables:

...

For Jira this means $210,000+. For Confluence it means $84,000+.

Future Server Summary - 2021-2025+

The total costs of staying with Server as long as possible will be:

...

The cost from 2021-2023 is $111,200 (17500+50400+13100+30200) and $294,000 (210000+84000) per year thereafter (while under 4000 users).

Option 2: Move to Data Center early (before 2/Feb/2021)

If we upgrade our licenses to Data Center before 2/Feb/2021, then:

...

Comparing Option 1 (Server for 3 years, then DC) and Option 2 (DC only)

...

Will Atlassian keep us 'advantaged' till at least 2025? Atlassian's stated goal with the 'advantaged' tier is to "ease users into list prices over time". I have questioned how long the easing process will go for, but have received no reply. As bets go, betting that Atlassian will keep our license status 'advantaged' for 5 years seems reasonable.

Option 3: Move to Cloud

Atlassian have 4 tiers in their Cloud products: Free, Standard, Premium and Enterprise:

...

The differences between tiers are seen in the business end of the feature table:

GDPR?

The first question to address is whether Jira and Confluence need to comply with GDPR regulations. If so, the only 'tier' of Cloud that could work is Enterprise, which offers 'Data residency'. Even with Enterprise, GDPR compliance is doubtful, as the Standard Contractual Clauses Atlassian depend on may soon be invalidated for the same reasons the EU-US-Privacy Shield was invalidated in July. Someone more versed in our GDPR needs and GDPR in general will need to make a call here.

Plugins?

Which tier?

As noted above, Jira uses 413Gb of disk space, over the 250Gb limit for Cloud 'Standard', so we'd need a 'Premium' Cloud subscription.

Atlassian Access

Atlassian Access is Atlassian's centralized user database for Cloud. It is required if we wish to sync with existing LDAP. Access also provides 2FA, SSO, SAML and other advantages.

Cloud pricing

Cloud pricing can be obtained from Atlassian's Cloud pricing calculator for Jira and Confluence. There is no equivalent pricing table that I can find (the Future cloud pricing tables 'New Price New License' column would apply, but there is no table for Cloud Premium). It is best to pick 'Annual' billing cycle, as this works out cheaper per year and also is required for 'loyalty discounts' (more on them below).

Loyalty Discounts

Atlassian is offering a Cloud loyalty discount for users migrating from Server or DC to Cloud. The discount schedule is:

...