Skip to main content

Versalist on your own servers

A Docker Compose package in development aims to put agent evaluation on hosts you control. It is not supported for production use.

Request a security reviewCompare deployment options

Agent evaluation and evidence

The preview package is intended to support agent evaluation on your servers. Production operation and trace capture have not been verified for this package.

Explore results and traces

What runs where

This table describes the intended architecture. Details can change before release.

Web application
A container built from the Versalist Dockerfile
Sign-in, database API, and file storage
Open-source Supabase containers: GoTrue, PostgREST, and Storage
Postgres
The Supabase Postgres container, with data on a Docker volume
Background jobs
A self-hosted Inngest server
Provider credentials
Encrypted in your Postgres with a key you generate
Models
Providers you configure. Private endpoints require an explicit opt-in and outbound network restrictions.
Sandboxed code execution
Not available

What you would provide

  • A Linux host with Docker Engine and Docker Compose v2.
  • DNS names for the application and its API, and TLS termination in front of them.
  • An SMTP server, if users should confirm their email addresses.
  • Backups of the database and file storage volumes.

What Versalist plans to provide

  • The Compose package, with a script that generates local application secrets.
  • A migration job that applies schema changes and records each one.
  • A database schema baseline for each release. Not published yet.

Current limits

  • A complete install needs a schema baseline that Versalist has not published yet. Without it, the migration job stops.
  • Sandboxed code execution needs Google Cloud Run and is off.
  • Application email, such as notifications, is sent through Resend, a cloud service.
  • Private model endpoints are disabled by default. Enable them only after restricting outbound network access.
  • Protected API routes require the bundled PostgreSQL rate limiter or a configured Upstash service.
  • Some images load from a public Google Cloud Storage bucket, so networks without internet access are not supported yet.
  • There are no published images, upgrade compatibility checks, or backup jobs yet.

How to start

  1. 1Generate configurationA script in the package writes every secret and signs the API keys.
  2. 2Add the schema baselineEach release needs a database schema baseline from Versalist. None is published yet.
  3. 3Start the stackdocker compose up builds the application and starts it after the database migrations finish.
Request a security review

Other deployment options