Technical Support

We Take Technical Support Seriously

This page provides information about our technical support practices and contacting our team if you need such support.

Questions and answers

As the FusionAuth community has grown, so has the number of support requests. We thought writing technical support guidelines would help customers, FusionAuth team members, and the community understand how to get technical support for FusionAuth.

We're engineers. We’d love to help everyone with everything, but we are a team with limited resources. Sharing these guidelines will allow us to continue to move the product forward and ensure we can prioritize our limited support resources efficiently.

This document is evolving and we welcome your feedback; please contact us to share it.

Support Requests  Support Requests

Whether you have a paid edition of FusionAuth that includes engineering support, or are one of the thousands of developers in the FusionAuth community, you’ll get answers more quickly if you provide the following information about your issue:

  • What you are trying to do, specific step by step of clicks you make, APIs you’ve called, configuration you have, things you’ve changed, etc. More information is better. For example, what you are seeing, specific panels in the UI, API status codes, errors, screenshots, etc. We want all of it.
  • What you expected to see. Sometimes this is obvious, and sometimes it isn’t. Err on the side of over sharing.
  • What you've tried already. Sometimes this can help us narrow down the issue more quickly.
  • The version of FusionAuth you are using (this information is available on the admin screen in the lower left hand corner).
  • The number of FusionAuth nodes you are running in your deployment.
  • Information about supporting infrastructure such as the database and elasticsearch, including the version and architecture (is the database local, cloud managed, etc).
  • All FusionAuth log files you can provide. Please don't provide snippets because often the issue won't be in the snippet but somewhere else in the logs. Providing us with complete log files upfront helps us track down issues faster. And you'll avoid getting replies like "please send the complete log files". Of course, please remove any sensitive information from the log files.

If you don’t provide this information initially, expect the FusionAuth team to ask for it.

Customers Paying For Support  Customers Paying For Support

If you have a paid edition which includes technical support, please open a ticket via your account portal. This ensures that we will see it; slack messages or emails can unfortunately get lost.

Paid support plans have access to the engineering team.

When you open a ticket, you will get a response within the documented time window for your edition, and typically sooner.

Community Members  Community Members

If you run the community or developer edition of FusionAuth and need technical support, please search the forum, post your question to the forum, or review our extensive documentation.

With community support, we can't offer a guaranteed response time. The timeline for an answer in the forum depends on what other community members can provide as well as the demands on the FusionAuth community support team.

In most cases our community support team is able to review community requests and respond within a week.

Community Support Limitations  Community Support Limitations

There are certain classes of problems with which the FusionAuth community support team will not help. You are welcome to post these quesitons in the forums to get feedback and to educate other community members, however.

We are engineers and it pains us to not answer every question we can. We were born to solve problems. However, when it comes to architecture decisions or system performance it is just not possible for us to field these questions through the community channels.

Architecture questions require a lot of context and knowledge of your application and infrastructure. The number of variables to be accounted for when offering performance advice is not trivial.

For these reasons, we require a paid support plan to assist with these types of issues:

  1. Production issues
  2. Architectural, design and integration guidance
  3. Performance tuning or load testing

Some examples of questions the community support team won't be able to answer:

  1. I want to build my application using feature X and Y; how should I best leverage FusionAuth?
  2. I have 1M users and my FusionAuth instance is slow; can you help?
  3. I want to connect FusionAuth to [other service]. How do I do that?

If you have needs around these concerns, please consider purchasing a support plan.

GitHub Issues  GitHub Issues

GitHub issues should be used to submit feature requests or bug requests with replication steps.

Any support requests opened in GitHub issues will be closed and redirected to the forum or support tickets, as appropriate. Unfortunately we may not be able to do such redirection in a timely manner.

Roadmap  Roadmap

If you have questions about future features and directions of FusionAuth, please see our roadmap guidance.

Callout