Installing Team

1. Download from your Licenses page: revoyse-team-<version>-amd64.tar (or -arm64), docker-compose.yml and .env.example. Check each file against its .sha256.

2. Load the image on your server:

   docker load -i revoyse-team-1.0.0-amd64.tar

3. Settings: in the folder with docker-compose.yml, copy .env.example to .env and fill in the two that are needed:

   REVOYSE_LICENSE_KEY=RV1-…            # from your Licenses page
   POSTGRES_PASSWORD=a-long-random-one  # any long random text; keep it

   If people won’t open it at http://localhost:8000, set PUBLIC_URL to the address they use (e.g. https://revoyse.yourcompany.com).

4. Start it:

   docker compose up -d

   Revoyse waits for its database, sets it up, and checks your licence with revoyse.com. It’s ready within a minute.

5. Open http://<your server>:8000 (or your own address) and create the first account: it becomes the team’s admin. See The admin.

Note

The image isn’t on any public registry: it’s only on your Licenses page. docker-compose.yml names an exact version, never latest.

Checking it’s running

docker compose ps        # both should be "running", Revoyse "healthy"
docker compose logs -f revoyse

A healthy start ends with api listening and license: checked with revoyse.com status=ok.

All the settings

Every setting is in .env.example, with what it does: the port (REVOYSE_PORT), the server’s name on your Licenses page (REVOYSE_SERVER_NAME), the encryption key for AI keys (KEYS_SECRET), mail (Email), S3 storage, and how many exports run at once (REVOYSE_RENDER_WORKERS). After changing .env, run docker compose up -d.

Storing files in S3

To keep the projects’ files in S3-compatible storage (AWS S3, Cloudflare R2, MinIO…) instead of the server’s disk, set AWS_BUCKET_NAME, AWS_REGION, AWS_ENDPOINT_URL, AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY (and AWS_S3_FORCE_PATH_STYLE=true for MinIO). Revoyse checks the bucket when it starts and says plainly if it can’t reach it.