Self-host pgvector Postgres with Levelrail

PostgreSQL 17 with the pgvector extension preinstalled, for embeddings next to your relational data.

  • Authorpgvector
  • LicencePostgreSQL
  • Memory512 MiB
  • Archarm64
  • Services1

How to self-host pgvector Postgres

  1. Pull the images

    One image is pulled on your server.

    Show images
    • pgvector/pgvector:0.8.6-pg17-trixie
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 5432.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

pgvector Postgres requirements

Memory
About 512 MiB
Architectures
amd64 image published, arm64 image published
Ports
5432
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
PostgreSQL, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 5432 on the host, so open them in the VPS firewall only if you want that.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then pgvector Postgres. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the pgvector Postgres docs page.

Deploy pgvector Postgres your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy pgvector Postgres from the CLI

levelrail-cli templates deploy pgvector --name my-pgvector

Deploy pgvector Postgres with the API

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/pgvector/deploy

pgvector Postgres configuration

pgvector Postgres services

ServiceImagePortsVolumes
pgvector pgvector/pgvector:0.8.6-pg17-trixie 5432 pgvector_data -> /var/lib/postgresql/data

pgvector Postgres environment variables

VariableServiceValue
POSTGRES_DB pgvector Preset by the template
POSTGRES_PASSWORD pgvector Generated at deploy
POSTGRES_USER pgvector Preset by the template

Ports and volumes

Ports
5432
Volumes
1 named mount: pgvector_data -> /var/lib/postgresql/data

pgvector Postgres FAQ

How much memory does pgvector Postgres need?

The catalog lists about 512 MiB of memory for pgvector Postgres.

Does pgvector Postgres run on arm64?

For pgvector Postgres, an arm64 image is published; amd64 is image published.

What licence is pgvector Postgres under?

pgvector Postgres is licensed under PostgreSQL, which is permissive, with few conditions on reuse.

Does pgvector Postgres need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which ports does pgvector Postgres use?

pgvector Postgres listens on port 5432 inside the stack.

Where does pgvector Postgres keep its data?

In a named volume: pgvector_data mounted at /var/lib/postgresql/data.

Can I deploy pgvector Postgres on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for pgvector Postgres, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image pgvector/pgvector:0.8.6-pg17-trixie is what you deploy there.

levelrail-cli templates deploy pgvector --name my-pgvector