# pg_pinecone now deploys on Railway in one click

> The Railway template for pg_pinecone deploys Postgres with Pinecone's vector search built in. Its index uses less memory than pgvector, so it costs less to run.

Gavin Johnson · 2026-11-18

With pgvector, the HNSW graph index needs more memory as a table grows, which makes vector search in Postgres increasingly expensive to run. The [pg_pinecone Postgres extension](https://www.pinecone.io/blog/introducing-pg-pinecone/) has lower latency than pgvector at the same recall and uses less memory, so it costs less to run as tables grow. The new [Railway template](https://railway.com/deploy/pg-pinecone) for pg_pinecone gives developers Postgres with Pinecone's vector search built in, deployed in one click.

![Animation of two identical Postgres services on Railway filling with vectors at the same rate; the pgvector HNSW (halfvec) service's index memory fills first, while the pg_pinecone service keeps adding vectors with its index memory still low.](https://cdn.sanity.io/images/vr8gru94/production/b85edf49bc8ac920dbdb77b20e4258abd4600b72-1200x675.gif)


The Railway template runs Postgres 18 with pg_pinecone installed, preloaded, and enabled, so there's no extension to install or image to build. In our benchmarks on 1 million vectors, the pg_pinecone index was about 15 times smaller than a pgvector HNSW index using halfvec and returned results faster at the same recall. Railway bills for the memory and storage a service uses, so a smaller index lets the same Postgres service hold many more vectors for the same cost. When a table needs to scale, a Pinecone API key and one SQL call [move its search](https://docs.pinecone.io/guides/pg-pinecone/switch-to-remote) to a serverless index in Pinecone's managed service, and another call moves it back. Wherever the vectors are stored, queries don't change.

The pg_pinecone template is available now in Railway's template marketplace, and the pg_pinecone extension is [open source](https://github.com/pinecone-io/pg_pinecone) under Apache 2.0. The `native` engine, pg_pinecone's default, runs inside Postgres and needs no Pinecone account.

To get started, deploy the [template](https://railway.com/deploy/pg-pinecone) on Railway, or read the [pg_pinecone quickstart](https://docs.pinecone.io/guides/pg-pinecone/quickstart#hosting-platform).