Support options

Last updated:

|Edit this page

Have a question? Ask anything PostHog-related at

PostHog provides a free basic level of support to everyone via the community, with additional support options available for paying customers depending on product.

Support typeOpen SourcePostHog CloudEnterprise
Official Support✔️✔️
Dedicated SlackMinimum $2k/month spend✔️
Training sessions✔️
Configuration assistance✔️
Terms and ConditionsMIT LicenceStandardMSA
Security assessmentStandard assessment providedStandard assessment provided✔️
Bespoke pricing✔️
Payment via invoicing✔️

Official Support

There are three ways to get official support:

We are very grateful to people that do this the other way around and help answer others' questions. You may just end up with some merch for particularly good answers :)

In-app Support

Anybody using PostHog Cloud can raise a bug, submit feedback or otherwise ask for help via the help menu in the top right hand corner of the UI. Your request will be routed to the correct team and we'll get back to you via email for further help if needed.

Severity Levels

In order to prioritise our responses we ask you to indicate the impact an issue is having for you. When creating a ticket you'll be asked to choose a severity level from one of the following:

CriticalPostHog is completely unavailable or or other significant business impact
  • PostHog Cloud UI is unavailable
  • Feature Flags API not responding
  • Data loss
  • Security breach
HighKey features of the product are unavailable, causing major inconvenience or limited functionality
  • Dashboards not loading
  • Session Replays not loading
  • Data Ingestion is delayed
  • Feature Flag targeting issues
MediumThere are issues with the product, but the impact is limited
  • Insights are slow to load
  • Session replays have missing information
LowRequests that have minimal impact on the usability of the product
  • Feature requests
  • Usage questions

Dedicated Slack

For certain paid customers we support you through a private Slack channel. This helps us all get on the same side - and it's just more fun for everyone.

We will select the right team for you at PostHog. This typically includes the Customer Success and Engineering teams.

These are the kinds of people you'd be working with!

We do not have non-technical support people who triage issues. We directly connect you to people who are building PostHog. This has scaled to support thousands of companies very effectively, and we always aim to productize solutions to problems.

From your side, it's important you bring your A team. We recommend you add:

  • A stakeholder from engineering
  • A stakeholder from data engineering / data analysis
  • A stakeholder from product management
  • 2-3 power users
  • A stakeholder from customer success (if relevant)
  • A stakeholder from sales (if relevant)

It's best not to let your group get much bigger as it can create a lot of noise.

Training sessions

We run a set number of group training sessions with your end users. We will walk them through how to make your product more successful.

These are useful at first for the initial adoption of PostHog. As you organically add more people to the platform, we can make sure everyone understands how to derive the most value.

Configuration assistance

We help you define meaningful dashboards for your company and regularly check in that the configuration of PostHog is helping you improve your product.

We ask to be a user in your PostHog team so we can suggest ways to get more value out of the product. These are some of the ways we can help you:

  • Build basic dashboards that cover Acquisition, Activation, Retention, Referral and Revenue
  • Build deep dive dashboards to help you understand changes in the above
  • Give guidance on using Session Recording, Heatmaps and Paths, depending on your product
  • Help you understand the impact on your core metrics of changes deployed behind Feature Flags
  • Help you run Experiments

Terms and Conditions

PostHog Open Source is MIT-licensed.

PostHog Cloud Editions have standard terms.

Master Services Agreement (MSA)

If you need non-standard terms or Service Level Agreements (SLAs), for example, we offer MSAs to Enterprise customers only. These cover things like:

  • Bespoke pricing
  • Custom Service Level Agreements
  • Custom legal changes if you have special requirements
  • Custom information security requirements

While we do not automatically accept all product changes and requests, we are willing to review these for our Enterprise product only. For Open Source, Cloud and Scale, we do not make contractual commitments to make product changes.

Security assessment

We have an extensive range of robust internal security policies that apply to all products and cover several requirements around GDPR, SOC 2, HIPAA and CCPA.

For Paid customers, we are happy to complete your own security assessment. This can take the form of us enabling your team internally (who are responsible for information security since they are hosting the data), or it can mean us just answering questions and adapting our policies if needed.

Bespoke pricing

We can offer bespoke pricing for Enterprise customers only.

For example, we have been asked if we can offer a set fee with a large usage cap rather than usage-based pricing, in order to make budget approval simpler.

Payment via invoicing

We only take payments via credit or debit card, processed via Stripe.

For companies with invoices over $2,000/month, we are able to support manual invoicing if needed. Just email and we'll set this up.


Was this page useful?

Next article


PostHog is an incredibly broad platform, with many distinct features and tools. As a result, it's hugely powerful -- but can be overwhelming if you're new to product analytics. So, we've created a glossary to explain many of the most common terms and acronyms. If a term is specific to PostHog then it's marked with a hedgehog 🦔 to help reduce confusion. A • B • C • D • E • F • G • H • I • J • K • L • M • N • O • P • Q • R • S • T • U • V • W • X…

Read next article