Can I use 1x Jira Data Center license for multiple individual Jira server each for a project ?

[passive 49]

May i know : If I need to create a Jira server for each project (now i use a Jira server license for each server set up. ie 10 projects , i have 10 jira server with 50 users each), does 1 x Jira Data Center license allow me do this moving forward since Jira server license is not offered anymore ?

Many thanks.

[Walter Buggenhout]

Hi @passive 49,

A license (data center or server) is related to the number of users for that instance, not to the number of projects.

The lowest user tier (number of users) for a Data Center instance is 500 users. If you are going to set up a separate data center instance for every project you want to run, that will become a very expensive situation.

Do have a look at the data center pricing faq to learn more. 

[passive 49]

so if i have 10 jira servers running now with 20 user license each , does it mean that i need 10 Jira data center licenses in future ? 

my jira server now has different issues type implemented to support specific workflows with different custom fields and screens. Each Jira server serves different project teams that are only allowed to CRUD their own jira server setup.

Then it would be very expensive and i would need to look for alternative now. 

thanks in advance.

[Ioana]

Hi,

You can either buy a Data Center license for each one, which will be very expensive or merge all of them into only one Jira instance and use only 1 license.

[Nic Brough -Adaptavist-]

Almost.  If you want to run a separate instance for each project, then yes, it's going to cost you an absolute fortune.  For 10 projects of 20 users, you will need 10 DC licences, which currently start at 500 users.

Jira simply isn't built to work in the way you're using it.  It would be cheaper and easier for you to merge all your projects on to a single platform (and that's on server, not even looking at DC).  Server/DC don't do multi-tenancy, but they can be made to look very close (done well, you can get it down to accidental discovery of the name of people who aren't in your silo, and knowing the field names in use in projects in other silos)

In fact "lots of totally independent systems with maintenance all over the place" is exactly what Cloud is built for.  I don't usually recommend a shift to Cloud without a lot more detail about people need from their Atlassian systems, but in this case, it would be ideal for your usage pattern.