Self-hosting
Run IForevents on your own infrastructure with one docker compose command
IForevents is built to be self-hosted. The images are public, there is no
license key and no account with us: docker compose up -d on a machine you
control gives you the whole product, and every event stays on that machine.
The install lives in its own public repository,
innovafour/iforevents-selfhosted:
one docker-compose.yml, an optional .env, and the issue tracker.
License
Self-hosting is free under the IForevents Self-Hosted License, a source-available license. Personal use and running IForevents for your own organization's products and operations are allowed, including in a for-profit business and through a contractor who runs the instance only for you. Offering it to others is not: hosting it as a service, renting or selling access to instances, projects or organizations, hosting analytics for clients, or reselling and white-labeling it all need a commercial license from [email protected]. See section 4 of the Terms of Service.
What you get
| Service | Image | Role |
|---|---|---|
dashboard | ghcr.io/innovafour/iforevents-dashboard | The web app on port 8010 |
api | ghcr.io/innovafour/iforevents-api | Ingest, analytics, sessions, migrations, on port 8000 |
clickhouse | clickhouse/clickhouse-server | Events, users, projects |
redis | redis | Project cache and rate limits |
Only the dashboard and the api publish a port. The two stores are reachable from inside the Docker network alone. There is no message broker: the api writes batches straight to ClickHouse through its ingest buffer.
Accounts live on your server: the first visit to the dashboard creates the administrator, and admins add teammates from Settings. There is no dependency on the hosted edition, no phone-home, no usage cap.
Requirements
- Docker Engine 24+ with the Compose v2 plugin (Docker Desktop on macOS and Windows works).
- Minimum 1 CPU core, 2 GB of RAM and 5 GB of disk. The whole stack idles around 250 MB of RAM (ClickHouse about 175 MB, the dashboard 45 MB, the api and Redis under 10 MB each) and the images take about 1 GB.
- Recommended for steady traffic: 2 CPU cores, 4 GB of RAM and 20 GB of disk, more once events pile up. ClickHouse is capped at 60% of the host's RAM and 2 GB per query by
clickhouse/iforevents.xml, so it shares a small box politely; give it 8 GB and fast disks when queries over months of data get slow. An event costs about 13 bytes on disk (about 9.4 in theeventstable, the rest in the daily rollups the charts read), so a GB holds roughly 76 million; large property payloads cost more.EVENTS_RETENTION_DAYScaps the events and their rollups alike. - A domain if people outside your network should reach it: the Caddy overlay handles TLS.
Where to go next
- Deployment: install, first login, a domain with HTTPS.
- Configuration: every variable of the
.env. - Operations: upgrades, backups, monitoring, recovery.
Prefer not to run servers? IForevents Cloud runs the same images for you; sign up and start on the Free plan (2,000,000 events a month).