Self-host pgvector Postgres on a VPS

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

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

Specification

Status
Listed
Category
Database Tools
Services
pgvector
Ports
5432
Volumes
1
Memory
about 512 MiB
arm64
image published
amd64
image published
Settings to fill in
none

About pgvector Postgres

PostgreSQL 17 with the pgvector extension preinstalled, for embeddings next to your relational data. Runs as a single container from the pgvector image, listening on port 5432; data is kept in named volumes.

What it deploys

pgvector Postgres runs as one service in a single Compose app, listening on port 5432, with 1 named volume mount.

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

Before you install

  • CPU architecture. arm64 listed. Every image lists linux/arm64 in its registry manifest. That is a manifest fact, not proof the app runs on Arm.
  • Listed. It is in the catalog. Back up the data volume before changing an image tag.
  • Host ports. It publishes port 5432 directly on the host, so open them in the VPS firewall only if you want that.

Settings and environment

You do not have to fill in anything. 1 secret is generated at deploy and stored encrypted. Values are never shown here.

ServiceVariableValue
pgvectorPOSTGRES_DBPreset by the template
pgvectorPOSTGRES_PASSWORDGenerated at deploy
pgvectorPOSTGRES_USERPreset by the template

Install pgvector Postgres on a VPS

  1. Install Levelrail on a fresh VPS

    Run this as root on a Linux server (amd64 or arm64) with ports 80 and 443 reachable. The installer prints a setup link.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
  2. Sign in

    Open the setup link, choose a password, then log the CLI in. The CLI install command is curl -fsSL https://levelrail.com/install-cli.sh | sh if the machine does not have it. See Getting started.

    levelrail-cli login --device
  3. Read the template

    Shows the entry, including its full compose.yaml.

    levelrail-cli templates get pgvector
  4. Deploy it

    This deploys the template compose file as an app. The app name defaults to the template id; --name sets another.

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

Without a domain the app gets an sslip.io address. You can also deploy it from the dashboard: Apps, New app, Browse templates, then pgvector Postgres.

More in Database Tools

All Database Tools templates