Skip to content
Database ⇄ AI

Citus to Pinecone integration — real-time, two-way sync

Keep Citus and Pinecone in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Citus and Pinecone

Sync the records in Citus into Pinecone and land its embeddings, classifications, and generated fields back on the same rows, in real time and without a pipeline to maintain.

AI systems do not hold customers or invoices the way business apps do. What they hold is derived from your data: the vectors and metadata in a vector store, or the classifications, extracted fields, and generated text a model produces over records it was given. Citus is where those source records actually live. The bridge between the two is the row itself, since an item in Pinecone and the record in Citus it describes are two halves of the same thing, and they drift the moment one is updated without the other.

Stacksync syncs Reference tables, Local tables, Schemas, Views in Citus with Index statistics, Indexes, Vectors (records), Namespaces in Pinecone in real time. Rows created or changed in Citus flow into Pinecone so inference and embedding run on current data, and the scores, labels, and generated fields Pinecone produces flow back onto the matching rows in Citus, mapped field by field. A change on either side appears on the other within seconds, with no extraction job or webhook plumbing to keep alive.

Because matching is by a stable identifier, every row in Citus stays tied to its AI-side counterpart in Pinecone. Retrieval, enrichment, and generated content always resolve back to the record they came from, so there are no orphaned vectors and no labels describing a version of a row that no longer exists.

Common use cases

  • 01 Back up a namespace by exporting its vector ids, values, and metadata to object storage or a database on a schedule using the list and fetch operations.
  • 02 Write embeddings and their metadata into a Pinecone index from a Postgres or warehouse table so a semantic-search or RAG feature always queries fresh vectors.
  • 03 Use a Citus cluster as the scalable operational store behind a customer-facing app while syncing summaries back to internal tools.
  • 04 Consolidate per-tenant rows from distributed tables into per-customer reporting databases.

Common sync patterns

Run the AI on current data

Rows created or changed in Citus flow into Pinecone as they happen, so embeddings, classifications, and prompts run on the latest records instead of a nightly snapshot.

Write results back onto the record

Scores, labels, extracted fields, or generated text produced in Pinecone land on the matching row in Citus, next to the source data your applications already query.

Keep derived data fresh as sources change

When a row in Citus is updated or removed, its counterpart in Pinecone is updated or removed too, so nothing in Pinecone describes a record that has since changed or gone.

What you can sync between Citus and Pinecone

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Citus objects Pinecone objects How this pairing syncs
Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Collections Immutable snapshots of a pod-based index that store its data but not its definition; created, listed, and deleted on the control plane and used to recreate a pod-based index. Serverless indexes use Backups instead. Distributed tables is specific to Citus and Collections to Pinecone — each maps to any object or custom field on the other side.
Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Backups Point-in-time snapshots of a serverless index; created, listed, and restored into a new index on the control plane for recovery or cloning. Read as a recovery-asset inventory. Reference tables is specific to Citus and Backups to Pinecone — each maps to any object or custom field on the other side.
Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Index statistics Describe_index_stats returns total and per-namespace vector counts, the index dimension, and index fullness; read to size a sync and to detect drift between Pinecone and the source of truth. Local tables is specific to Citus and Index statistics to Pinecone — each maps to any object or custom field on the other side.
Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Indexes Serverless or pod-based containers holding vectors of a fixed dimension and distance metric (cosine, dotproduct, euclidean); managed on the control plane (api.pinecone.io) via create, list, describe, configure, and delete. describe_index returns the per-index data-plane host. Schemas is specific to Citus and Indexes to Pinecone — each maps to any object or custom field on the other side.
Views Curated projections over distributed data, often used as read-only sync sources. Vectors (records) The core data: an id (up to 512 chars), a dense values array, optional sparse_values, and JSON metadata (up to 40 KB filterable per record). Full CRUD on the data plane via upsert, update, fetch, query, and delete, so write is supported here. Views is specific to Citus and Vectors (records) to Pinecone — each maps to any object or custom field on the other side.
Sequences Key generators that matter when external writes must not collide with application inserts. Namespaces Partitions inside an index; every read and write targets one namespace and vectors across namespaces are isolated. Enumerated with list_namespaces and sized per namespace via describe_index_stats. Sequences is specific to Citus and Namespaces to Pinecone — each maps to any object or custom field on the other side.

How changes propagate between Citus and Pinecone

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Citus Pinecone Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

DeliveryEach detected change is written to Pinecone through its API, with automatic retries and rate-limit backoff.

Pinecone Citus Interval-based propagation

DetectionStacksync polls Pinecone for changes on an incremental schedule, reading only records changed since the previous pass. No webhooks and no native change-data-capture feed.

DeliveryEach detected change is applied to Citus as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Pinecone: Data-plane operations are capped per second: query, upsert, update, and delete at 100 req/s per namespace, fetch at 100 req/s per index, and list at 200 req/s per index; breaches return HTTP 429. Hard request limits also apply: an upsert is max 2 MB or 1000 records, metadata max 40 KB per record, and query top_k up to 10,000 with a 4 MB result cap.
What ships with Citus ⇄ Pinecone

Connect Citus and Pinecone for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Citus–Pinecone connection.

Real-time

Two-way sync

Changes in Citus or Pinecone instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Citus or Pinecone data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Citus or Pinecone record.

Observability

Monitoring

Track your Citus ⇄ Pinecone sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Citus and Pinecone.

How the Citus and Pinecone connectors work

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC

Pinecone

Integration surface
Two HTTP APIs: a control plane at api.pinecone.io (manage indexes, collections, backups, and, via the Admin API, projects and API keys) and a per-index data plane at the host returned by describe_index (upsert, query, fetch, update, delete, list). A gRPC data-plane transport is available through the official SDKs.
Authentication
API key in the Api-Key request header, scoped to one project; every request also sends an X-Pinecone-Api-Version header (date-based, e.g. 2025-10). The organization Admin API instead uses OAuth2 client-credentials (service accounts) via login.pinecone.io/oauth/token, passing a Bearer token to api.pinecone.io/admin (Enterprise).
Change detection
No webhooks and no native change-data-capture feed. Vectors carry no server-side update timestamp, so Stacksync detects changes by re-reading - paginating vector ids with the list operation (serverless indexes) and fetching by id, or by re-upserting from the source of truth. describe_index_stats bounds a resync with per-namespace counts.
Capabilities
read · write
Rate limits
Data-plane operations are capped per second: query, upsert, update, and delete at 100 req/s per namespace, fetch at 100 req/s per index, and list at 200 req/s per index; breaches return HTTP 429. Hard request limits also apply: an upsert is max 2 MB or 1000 records, metadata max 40 KB per record, and query top_k up to 10,000 with a 4 MB result cap.
How it works

How to connect Citus to Pinecone — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Citus and Pinecone with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Citus connected
    Pinecone connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Citus and Pinecone objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Citus ⇄ Pinecone
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Citus Pinecone
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Citus and Pinecone integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 405 integrations available for Citus and Pinecone.

Popular · 7 of 405
All Citus integrations All Pinecone integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own