Docker installation
Install self-hosted analytics with Docker Compose
Vectr4 is delivered as a Docker Compose stack for a Linux VPS. This guide covers the operational sequence around the licensed deployment package without publishing customer secrets or pretending one command replaces DNS, HTTPS, backups, and monitoring.
Published Technical guide by Vectr4
Category
Self-hosted analytics
Product focus
Events, funnels, sessions, journeys
Deployment
Your VPS with Docker Compose
01
1. Prepare the server and domain
Provision a supported Linux VPS, install current Docker Engine and the Docker Compose plugin, create a DNS record for the analytics hostname, and allow the required HTTP and HTTPS traffic through the server firewall.
- Confirm SSH access using a non-root administrative account.
- Run
docker compose versionbefore uploading the package. - Point a dedicated hostname such as
analytics.example.comto the VPS. - Decide where encrypted backups will be stored before collecting production events.
02
2. Configure the licensed deployment package
Download the deployment ZIP from your Vectr4 account, extract it on the server, and review every generated file before starting services. Keep the included .env file private and never commit it to source control.
- Set the public analytics domain.
- Replace all placeholder application login values before first use.
- Keep generated database, session, ClickHouse, and Redis secrets intact unless rotating them deliberately.
- Confirm the license file belongs to the purchasing account and deployment.
03
3. Start and inspect the stack
From the deployment directory, start the services with docker compose up -d. Then inspect state with docker compose ps and follow service output with docker compose logs --tail=100. A running container is not sufficient proof that the public route or ingestion path works.
04
4. Verify before sending production traffic
For DNS, reverse proxy, maintenance, and security context, continue with the guide to self-hosting web analytics. For the analytics category itself, see self-hosted product analytics.
- Open the HTTPS dashboard through the public hostname.
- Sign in using the application administrator account you configured.
- Send a test event from a non-production project.
- Confirm that the event appears in the dashboard and expected session or funnel views.
- Test a backup and restore procedure, then add monitoring for disk, memory, certificates, and unhealthy containers.
FAQ
Frequently asked questions
Is Docker Compose enough for production?
Docker Compose can be practical for a small VPS deployment, but production readiness also requires DNS, HTTPS, secrets, backups, monitoring, upgrades, capacity planning, and access control.
Which Vectr4 values are public?
The analytics hostname and browser ingestion configuration may be public. Database passwords, session secrets, signer credentials, administrator passwords, and private environment files must remain secret.
How do I update Vectr4?
Follow the release-specific update instructions included with your licensed package. Back up data and configuration before changing images or running migrations.