HipChat Data Center FAQs

You've got questions, we've got answers!

On this page:

Support and timelines

Why is Atlassian no longer offering HipChat Server?

At Atlassian we want to keep licensing simple and consistent by offering a single subscription option for our self-hosted chat solution. HipChat Data Center has all the same features of HipChat Server that you know and love, plus new benefits like high availability, scalability, and improved authentication and control. However, if you want to run HipChat as a single node with externalized data stores you can continue to do so.

See the Deployment options and sizing guidelines for HipChat Data Center to learn more about when to use one, or three node deployment.

When does this change take effect?

The official change takes effect on when HipChat Data Center officially launches.

Why should I move to HipChat Data Center? Why should I move now?

By making the transition to HipChat Data Center, you'll get the new benefits of high availability, scale, and improved authentication and control, and you'll be able to take advantage of future feature updates and bug fixes. If you continue to run HipChat Server (on the existing appliance model) we will only provide critical security updates for two years after our last release according to our end of life policy.

We encourage you to migrate to HipChat Data Center as soon as it's feasible. Learn more about the resources available to help you plan your migration.

Are other Server products going to be replaced by Data Center?

We don't plan to remove other Server offerings (e.g. JIRA Software, Confluence, Bitbucket, etc.). The perpetual licensing model of our other Server products is different from the subscription model of HipChat Server and Data Center.

Are there any changes to HipChat Cloud or the HipChat Cloud pricing model with the launch of HipChat Data Center?

No, there are no changes to HipChat Cloud.

Do I have to transition to HipChat Data Center? If so, when?

You don't have to transition to HipChat Data Center right away. However, we strongly encourage you to start working to transition so you get the continued benefits that come with HipChat Data Center.

HipChat Server will continue to be supported according to our standard end-of-life policy. Our last appliance release for HipChat Server was 2.3.0 on  . The existing appliance model will only receive critical security updates during this period.

What is the HipChat Server EOL policy? Check out the Atlassian End of Life policy here.

What happens if I don't transition to HipChat Data Center?

We will support the HipChat Server appliance model according to the rules in our end of life policy. During this support period, you'll only have access to critical security releases. If you want to get new features, you need to transition to HipChat Data Center.

Is the support policy changing?

No, our support policy is not changing.

We support HipChat Data Center, and HipChat Server will continue to be supported according to our standard end-of-life policy. Our last appliance release of HipChat Server was 2.3.0 on  . 

Architecture and requirements

What is changing with the launch of HipChat Data Center? What new things do I need to deploy?

HipChat Data Center does not ship as an appliance with data stores included. Instead, HipChat Data Center ships as a VMWare image or AWS AMI with externalized data stores that you must deploy yourself. You will now bring your own database, data stores, and load balancer for both an AWS deployment and a VMWare deployment.

Check out the new HipChat Data Center architecture, the Deployment options and sizing guidelines, and read more about Migrating from HipChat Server to HipChat Data Center.

When should I run HipChat Data Center with multiple nodes?

If your HipChat instance serves 1000 or more users, we highly recommend running on a three node cluster for performance reasons. If the cluster serves 2000 or more users, you must run a three node cluster to support that scale.

How many users does HipChat Data Center support? HipChat Data Center supports up to 20,000 named users and 10,000 concurrent active users.
What happens when the 10,001 concurrent user logs in? Users can continue to login, but you may experience performance issues.
How do I migrate to HipChat Data Center if I have multiple HipChat Server instances? We do not support consolidation of instances at this time. However, you can connect to external user directories to make sure all the right users have access to HipChat Data Center.


What if I want to add more users to my license or change license tier, but stay on HipChat Server and continue using the appliance version?

If you want to upgrade your license tier, you'll receive a quote for HipChat Data Center. You can stay on the appliance model version of HipChat until the EOL period ends, but you'll only receive critical security updates during this time.
If I'm already a HipChat Server customer, do I need to get a new license key to upgrade to HipChat Data Center? No, the existing HipChat Server license key will be compatible with Data Center functionality as long you migrate to HipChat Data Center. When you renew we'll upgrade your HipChat Server license key to a HipChat Data Center license key.
Can I deploy HipChat Data Center with my current Atlassian Stack or ELA license? All existing Stack and ELA customers will receive a new license key that includes HipChat Data Center on  , along with all necessary documentation.
How many HipChat Data Center users are included if I have an Atlassian Stack or ELA license? The number of HipChat Data Center users will match the permitted users on your Stack or ELA license. (e.g. 5000 Stack License equals 5000 HipChat Data Center licenses).

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

Ask our community
Powered by Confluence and Scroll Viewport