What's already configured
After the one-click install finishes, the full PostHog hobby stack is already running: the PostHog application itself alongside PostgreSQL for account and configuration data, ClickHouse for event storage, and Redis for caching and background jobs, all wired together and started automatically. Everything restarts automatically if the server reboots, so there's no need to start the stack manually after a maintenance window.
First login
Open your server's domain or IP address in a browser — PostHog doesn't ship with a default admin password to look up, because the first visit takes you straight into a setup wizard where you create your organization, project, and first admin account yourself. Use a domain with SSL already attached before this step, since the credentials you set travel over that connection.
Hobby deployment specifics
The self-hosted build isn't a separate stable release — PostHog pushes the same commits to Cloud and self-hosted through one CI/CD pipeline, so there's no tagged version to pin your instance to. PostHog's own documentation states this deployment path is meant to comfortably handle up to roughly 100,000 events a month; past that, expect to either resize the VPS or consider PostHog Cloud for the ingestion layer.
PostHog also states plainly that it offers no official support or uptime guarantees for self-hosted installs — Leneex's own engineers and root access become the practical safety net instead. One more detail worth knowing: the domain PostHog uses to build links inside emails and webhook payloads gets set during install, so moving to a different domain later means updating that setting rather than expecting it to update itself.