Talk about your next project
Pinecone landing page

The lesson

Make a competitor comparison credible by publishing your benchmark setup and stating the cases where the competitor beats you.

The move

The hero reads "Pinecone vs pgvector" and frames the decision as where vector search runs: pgvector's index, the pg_pinecone extension, or Pinecone Database. It names three places pgvector falls short, then a section nav and a summary line say when to stay on pgvector, when to add pg_pinecone, and when to choose Pinecone Database. "What we measured" shows benchmark cards such as "136 MB vs 2.0 GB" index size and "0.981 vs 0.924" recall at a 1 percent filter, followed by the dataset, hardware and versions, and a "Where pgvector did better" paragraph. "When to pick which" and "Feature by feature" follow, then sections on index memory, filtering, clusters and drift, concurrency, operating cost, moving from pgvector, FAQ and sources.

Why it works

  • Our readOpening with a choice of where search runs, instead of a verdict, tells a Postgres team its rows stay put whichever option it picks.
  • Our readListing the dataset, hardware, versions and settings next to the numbers, with a note to test your own workload, lets an engineer check the claims instead of taking them on trust.
  • Our readSaying plainly that HNSW was faster at a 10 percent filter and that Postgres has operational maturity Pinecone lacks makes the remaining claims easier to believe.

What not to copy

Don't copy the three-way framing unless you also ship a product that lives inside the competitor's ecosystem, and don't publish benchmark numbers you can't share commands to rerun. Keep the order: decision summary, reproducible benchmark with losses admitted, fit lists for each option, then feature-by-feature detail and migration notes.

More from Pinecone

More landing pages

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.