Skip to content

Documentation

Self-hosted deployment

Run EvenTier on your own servers with Docker Compose, Kubernetes or a Linux server.

Where
Account console (/account) · oci://ghcr.io/eventierio/charts/eventier · eventier-server-<version>-linux-x64.tar.gz
Permission
Account member (bundles, license) · owner (billing) · admin of the host, cluster or server
Updated
October 2026

Before you start

Self-hosting starts with a self-hosted account: choose Self-hosted when you sign up.

You get a 14-day evaluation license for 20 agents, with no card needed. The account console holds your license, deployment bundles, billing, members and support.

A paid cloud workspace can add self-hosting from its own Billing page instead.

There are three ways to run it: Docker Compose on one Linux host, the Helm chart on Kubernetes or OpenShift, or a Linux server with systemd. Requirements compares what each needs.

Each bundle comes with generated secrets, a setup token, your license file and the current release.

PostgreSQL 16 is included on every path, or you can use your own.

Back up SECRET_ENCRYPTION_KEY with your database. Without it, stored integration credentials can't be decrypted.

An install runs one organization and the product only: no signup and no operator console. The website, docs and account console stay on eventier.io.

Step by step

  1. 01

    Create a self-hosted account

    Choose Self-hosted when you sign up, confirm your email and name the account.

    • Invite colleagues from Members in the account console
  2. 02

    Download a bundle

    In the account console, open Deploy and pick how you will run EvenTier.

    • Docker Compose: one Linux host
    • Kubernetes: the Helm chart on your cluster
    • Server: a Linux server, run by systemd
  3. 03

    Set your web address

    Open the bundle's settings file and set the address people will open. That is the only required setting; everything else already has a working default.

    • Docker Compose: EVENTIER_DOMAIN in .env
    • Kubernetes: app.url in values.yaml
    • Server: NEXT_PUBLIC_APP_URL in eventier.env
    • Database: the bundled PostgreSQL by default, or set EVENTIER_BUNDLED_POSTGRES=false and DATABASE_URL to your own
    • Keep the settings file private: it holds your secrets
    .env (Docker Compose): the Required sectionbash
    EVENTIER_DOMAIN=help.yourcompany.com
    EVENTIER_BUNDLED_POSTGRES=true
  4. 04

    Choose notifications

    In-app notifications are always on. The Notifications section of the settings file decides what else is sent, and its defaults work without changes.

    • In-app only: EMAIL_DELIVERY_MODE=off
    • In-app and email: fill in SMTP_HOST and SMTP_FROM. The default, EMAIL_DELIVERY_MODE=auto, starts sending once SMTP_HOST is set
    • Refuse to start without a relay: EMAIL_DELIVERY_MODE=smtp
    • Sign-in codes by text message: SMS_PROVIDER=sns (Amazon SNS) or SMS_PROVIDER=webhook (your own gateway). The default is off
    • With email off, people sign in with passwords an administrator sets, or through SSO
    .env (Docker Compose) or eventier.env (server): the Notifications sectionbash
    EMAIL_DELIVERY_MODE=auto
    SMTP_HOST=smtp.yourcompany.com
    SMTP_PORT=587
    SMTP_USER=
    SMTP_PASS=
    SMTP_FROM="EvenTier <no-reply@yourcompany.com>"
    
    SMS_PROVIDER=off
  5. 05

    Start it: Docker Compose

    On a Linux host with Docker Engine 24 or later and the Compose plugin, set up the database and start the stack. Caddy, included in the bundle, handles HTTPS.

    In the unzipped bundle folderbash
    chmod 600 .env
    docker compose run --rm migrate
    docker compose up -d
  6. 06

    Start it: Kubernetes

    Check the image signature, create the bundle's Secret, then install the published chart with its values.yaml. Each pod sets up the database before it starts.

    • secrets.yaml is a Kubernetes Secret with the generated secrets; values.yaml names it, so they never pass through Helm
    • The chart creates the Ingress, the volumes and the bundled PostgreSQL and ClamAV
    • global.storageClass picks the StorageClass for every volume; blank uses the cluster default
    • The chart version and image digest come from the release notes
    Verify and installbash
    cosign verify ghcr.io/eventierio/eventier@sha256:<digest> \
      --certificate-identity-regexp '^https://github.com/eventierio/eventier/' \
      --certificate-oidc-issuer https://token.actions.githubusercontent.com
    
    kubectl create namespace eventier
    kubectl config set-context --current --namespace=eventier
    kubectl apply -f secrets.yaml
    helm install eventier oci://ghcr.io/eventierio/charts/eventier --version <x.y.z> -f values.yaml --wait --timeout 15m
  7. 07

    Start it: OpenShift

    Use the Kubernetes bundle with two settings changed. The chart then serves your address through a Route and grants the pods the security context constraints (SCCs) they need.

    • Set openshift.enabled: true and ingress.enabled: false in values.yaml
    • The Route ends TLS at the router, with its default certificate or yours under openshift.route.tls
    • The app, worker, PostgreSQL and Redis get the built-in nonroot-v2 SCC; the bundled ClamAV gets an SCC of its own
    • Creating those grants needs a cluster administrator once. Otherwise set openshift.scc.create: false and an administrator runs the command the install notes print
    • OpenShift 4.11 or later
    Install on OpenShiftbash
    oc new-project eventier
    oc apply -f secrets.yaml
    helm install eventier oci://ghcr.io/eventierio/charts/eventier --version <x.y.z> -f values.yaml --wait --timeout 15m
  8. 08

    Start it: a Linux server

    install.sh checks your settings, installs EvenTier under /opt/eventier and starts it on 127.0.0.1:3000, behind your reverse proxy.

    • Malware scanning needs clamd listening on 127.0.0.1:3310, or set ATTACHMENT_MALWARE_SCANNER=off
    • It installs PostgreSQL 16 unless you bring your own
    • It sets up the database and starts the systemd service
    In the unzipped server bundle, with the release tarball next to itbash
    ./install.sh --check
    sudo ./install.sh eventier-server-<x.y.z>-linux-x64.tar.gz
    systemctl status eventier
  9. 09

    Create the organization and add your license

    Open /get-started, enter the setup token from your settings file, and create the first administrator and organization.

    • The setup token is EVENTIER_SETUP_TOKEN
    • Everyone else joins by invitation, single sign-on (SSO) or SCIM
    • Upload the license file at Admin > Billing
    • Without a valid license, the install refuses new requests and new agents
  10. 10

    Turn optional features on or off

    Each feature is one setting with a working default. Configuration reference lists every one.

    • On by default: in-app notifications, malware scanning and the EvenTier support link
    • On once you fill them in: email (SMTP_HOST)
    • Off until you set them: Evee, semantic search, S3 attachments, requests by email, text-message codes and metrics
    • Docker Compose also stops the clamav service when scanning is off
    • Kubernetes: clamav.enabled: false turns scanning off; other settings go under env.config, and passwords and keys in secrets.yaml
    .env (Docker Compose) or eventier.env (server)bash
    # Store uploads without a malware scan
    ATTACHMENT_MALWARE_SCANNER=off
  11. 11

    Back up and upgrade

    Back up PostgreSQL, the attachment store and SECRET_ENCRYPTION_KEY on your normal schedule.

    • Upgrading a self-hosted install covers each path
    • Audit logs are kept forever on an install until you choose a limit. See Data retention
    • No internet on the host? Air-gapped installs covers images, HTTPS and malware signatures

Examples

Minimal values fileyaml
app:
  edition: self-hosted
  # The ingress host and its TLS follow this URL.
  url: https://eventier.internal.example.com

ingress:
  enabled: true
  className: nginx
  tlsSecretName: eventier-tls

global:
  storageClass: ""

postgresql:
  enabled: true

env:
  # The Secret from secrets.yaml.
  existingSecret: eventier-secrets
  config:
    # In-app notifications, plus email once SMTP_HOST is set.
    EMAIL_DELIVERY_MODE: "auto"
    SMTP_HOST: smtp.internal.example.com
    SMTP_FROM: "EvenTier <no-reply@example.com>"
    SMS_PROVIDER: "off"
secrets.yamlyaml
apiVersion: v1
kind: Secret
metadata:
  name: eventier-secrets
type: Opaque
stringData:
  NEXTAUTH_SECRET: "<openssl rand -hex 32>"
  ORG_AUTH_SECRET: "<openssl rand -hex 32>"
  AUTH_SECURITY_SECRET: "<openssl rand -hex 32>"
  AUTH_MFA_SECRET: "<openssl rand -hex 32>"
  SECRET_ENCRYPTION_KEY: "<openssl rand -hex 32>"
  EVENTIER_SETUP_TOKEN: "<openssl rand -hex 24>"
  # Only with your own PostgreSQL (postgresql.enabled: false):
  # DATABASE_URL: "postgresql://eventier:<password>@db.internal:5432/eventier"
  # Only if your SMTP relay needs a login:
  # SMTP_USER: ""
  # SMTP_PASS: ""

Good to know

  • Every bundle download generates new secrets. Keep the first bundle's settings file (and on Kubernetes its secrets.yaml) for the life of the install.
  • One license covers one production instance plus a staging install. Run upgrades on staging first.
  • Licenses EvenTier issues for your account appear under License in the console, and the owner gets the file by email.
  • If EvenTier revokes a license, the install keeps working until its next upgrade. The new release carries the revocation list, and new requests and new agents pause until an administrator installs a valid license at Admin > Billing.