Questions About PostHog Self-Hosted (deploy-hobby Deployment)

Description

Hello PostHog Team,

We are currently evaluating PostHog for internal use and encountered an issue when trying to set up the environment using posthog-foss—our build attempt failed. Following the guidance in the official documentation, we are now planning to switch to the deploy-hobby method for self-hosting.

To ensure a smooth deployment and compliance with usage rules, we have 3 key questions regarding the deploy-hobby self-hosted setup, and would greatly appreciate your clarification:

Questions

1. Are there any restrictions on usage period or data traffic quota for the PostHog self-hosted environment deployed via deploy-hobby?
2. If we use the deploy-hobby self-hosted environment for production purposes (with no external distribution, no commercial resale, and for internal use only), does this introduce any legal risks (e.g., non-compliance with licenses)?
3. If the deploy-hobby deployment has functionality restrictions for production use, could you specify which features are available for free use in this scenario?

Additional Context

• We previously attempted to build the environment using posthog-foss but encountered unresolved build failures.
• Our use case is strictly internal (no external user access or commercialization), and we need to confirm compliance and feature availability before moving to production.

Thank you for your support!

Start by reviewing the official self-hosting documentation and the deploy-hobby guidance referenced in the issue. Done means the documentation clearly answers the usage limits, production and licensing implications, and free feature availability for the described internal deployment.