HipChat Data Center FAQs

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

On this page:

Architecture and requirements

What changed 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.

See the Deployment options and sizing guidelines for Hipchat Data Center for more details.

Do I really need to deploy three nodes? Why not just two?

If you have enough users in your deployment that you need more than one node, you need a total of three nodes.

If you were to only deploy two nodes for a medium or large deployment, it would give you a false sense of security. If a single node in a two-node cluster fails, the remaining node would immediately be overwhelmed with traffic.

With a three-node cluster one node can fail and the remaining two can continue operating, even if their performance is reduced.

Do I really need a load balancer in my deployment? What if I only have one HipChat node?

HipChat Data Center assumes that it is installed on a secure private network, such as a VPC. Clients access HipChat node(s) through a service which terminates SSL, regardless of deployment scale.

In an Enterprise-scale deployment this service is a load balancer, which distributes client connections among the HipChat nodes. In a small-scale deployment all connections go to a single HipChat node, so this service can be just a reverse proxy.

Several services (such as NGINX or Apache) can function as both a load balancer and a reverse proxy. If you use one of these for your small-scale deployment, you can quickly scale it up later by adding more HipChat nodes.

Which AWS regions do you support?

We currently publish our AWS AMIs to the following regions:

  • eu-west-1 (Ireland)
  • us-east-1 (N. Virginia)
  • us-west-2 (Oregon)
  • ap-southeast-2 (Sydney)

Additional regions may be added later as support for EFS grows.

Why are there so few supported AWS regions?

For high-availability purposes, we limit Hipchat Data Center to only regions with three Availability Zones (or AZs) that also support all of the components required by the cluster. At this time, EFS is often the missing component.

When you use our AWS CloudFormation template to deploy an Enterprise scale Hipchat Data Center cluster, AWS deploys one Hipchat node to each AZ. This ensures high availability within your AWS region.

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.

Support and timelines

Is Hipchat going away?!

Nope, we're not going away! We know with the launch of Atlassian Stride this can be a bit confusing, but rest assured: Hipchat Data Center will continue to provide an option for self-hosted enterprise team communications.

Hipchat Cloud customers will be upgraded to Stride over time, and similarly Hipchat Server customers will need to upgrade to Hipchat Data Center - still self-hosted, but now better than ever.

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 22 Jun 2017 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 03 May 2017 . 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 03 May 2017 . 


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 22 Jun 2017 , 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).
Last modified on Sep 26, 2017

Was this helpful?

Provide feedback about this article

Not finding the help you need?

Ask the community

Powered by Confluence and Scroll Viewport.