Deploy pgvector through the Linode Marketplace

Pgvector is an open-source PostgreSQL extension that enables vector similarity search directly inside a relational database. It allows you to store embeddings alongside structured data and perform nearest-neighbor searches using cosine similarity, inner product, or Euclidean distance—making it well-suited for AI, semantic search, and retrieval-augmented generation (RAG) workloads.

Deploying a Marketplace App

The Linode Marketplace lets you easily deploy software on a Compute Instance using Cloud Manager. See Get Started with Marketplace Apps for complete steps.

1. Log in to Cloud Manager and select the Marketplace link from the left navigation menu. This displays the Linode Create page with the Marketplace tab pre-selected.

2. Under the Select App section, select the app you would like to deploy.

3. Complete the form by following the steps and advice within the Creating a Compute Instance guide. Depending on the Marketplace App you selected, there may be additional configuration options available. See the Configuration Options section below for compatible distributions, recommended plans, and any additional configuration options available for this Marketplace App.

4. Click the Create Linode button. Once the Compute Instance has been provisioned and has fully powered on, wait for the software installation to complete. If the instance is powered off or restarted before this time, the software installation will likely fail.

To verify that the app has been fully installed, see Get Started with Marketplace Apps > Verify Installation. Once installed, follow the instructions within the Getting Started After Deployment section to access the application and start using it.

Configuration Options

• Supported distributions: Ubuntu 24.04 LTS
• Suggested plan: Dedicated 16GB instance or higher for baseline development and testing with support for GPU instances. Larger plans are recommended for compute

Pgvector Options

Limited Sudo User

You need to fill out the following fields to automatically create a limited sudo user, with a strong generated password for your new Compute Instance. This account will be assigned to the sudo group, which provides elevated permissions when running commands with the sudo prefix.

• Limited sudo user: Enter your preferred username for the limited user. No Capital Letters, Spaces, or Special Characters.

  Locating The Generated Sudo Password

  A password is generated for the limited user and stored in a .credentials file in their home directory, along with application specific passwords. This can be viewed by running: cat /home/$USERNAME/.credentials

  For best results, add an account SSH key for the Cloud Manager user that is deploying the instance, and select that user as an authorized_user in the API or by selecting that option in Cloud Manager. Their SSH pubkey will be assigned to both root and the limited user.

• Disable root access over SSH: To block the root user from logging in over SSH, select Yes. You can still switch to the root user once logged in, and you can also log in as root through Lish.

  Accessing The Instance Without SSH

  If you disable root access for your deployment and do not provide a valid Account SSH Key assigned to the authorized_user, you will need to login as the root user via the Lish console and run cat /home/$USERNAME/.credentials to view the generated password for the limited user.

Custom Domain (Optional)

If you wish to automatically configure a custom domain, you first need to configure your domain to use Linode’s name servers. This is typically accomplished directly through your registrar. See Use Linode’s Name Servers with Your Domain. Once that is finished, you can fill out the following fields for the Marketplace App:

• Linode API Token: If you wish to use the Linode’s DNS Manager to manage DNS records for your custom domain, create a Linode API Personal Access Token on your account with Read/Write access to Domains. If this is provided along with the subdomain and domain fields (outlined below), the installation attempts to create DNS records via the Linode API. See Get an API Access Token. If you do not provide this field, you need to manually configure your DNS records through your DNS provider and point them to the IP address of the new instance.
• Subdomain: The subdomain you wish to use, such as www for www.example.com.
• Domain: The domain name you wish to use, such as example.com.

Obtain the Credentials

When deployment completes, the system automatically generates credentials to administer your Pgvector instance. These are stored in the limited user’s credentials file.

1. Log in to your Compute Instance using one of the methods below:

   • Lish Console: Log in to Cloud Manager, click Linodes, select your instance, and click Launch LISH Console. Log in as root. To learn more, see Using the Lish Console.
   • SSH: Log in to your instance over SSH using the root user. To learn how, see Connecting to a Remote Server Over SSH.

2. Run the following command to access the credentials file:

cat /home/$USERNAME/.credentials

Getting Started after Deployment

You can start by connecting to your Postgresql database

psql -h localhost -U $POSTGRES_USER -d $POSTGRES_DB

The connection credentials can be found in the credentials file located at /home/$USERNAME/.credentials.

You can then define vector columns and run similarity queries directly in SQL.

pgvector works with standard PostgreSQL clients and integrates easily with popular AI frameworks and ORMs:

- **[psycopg](https://www.psycopg.org/)**: PostgreSQL adapter for Python
- **[SQLAlchemy](https://www.sqlalchemy.org/)**: Python ORM with pgvector support
- **[pgvector-node](https://github.com/pgvector/pgvector-node)**: Node.js client helpers
- **[pgvector-go](https://github.com/pgvector/pgvector-go)**: Go utilities for pgvector

If you want to learn more about pgvector, check out the official Pgvector documentation to explore indexing strategies, performance tuning, and advanced query patterns.

More Information

You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.

• pgvector GitHub
• pgvector Documentation
• PostgreSQL Documentation