Pinevale indexes, kept in sync.
Map a view's vector column to a Pinevale index. Inserts and updates upsert within seconds, and deletes remove the vector.
How it works.
Basalt reads the view's change feed and upserts vectors by row key into the namespace you choose. Other columns are sent as metadata for filtering. Deletes in the view become deletes in the index.
Set it up in three steps.
Connect the tool
Paste a Pinevale API key and name an existing serverless index. Basalt checks that dimensions match before the first upsert.
# sync product embeddings to Pinevale basalt sink add catalog --pinecone products-prod --view product_vectors --namespace live ✓ index products-prod · 1536 dims · cosine ✓ 1.2M vectors upserted · lag 1.8 s
Shape it with a view
Write plain SQL over the source. Basalt keeps the view current with every record and tracks lineage back to the topic, partition and offset.
CREATE MATERIALIZED VIEW revenue_by_min AS SELECT date_trunc('minute', ts) AS minute, currency, sum(amount) AS revenue, count(*) AS payments FROM payments WHERE status = 'captured' GROUP BY 1, 2;
Read it from anywhere
Every view is an endpoint the moment it exists. Call it over REST, connect with any Postgres client, or use the SDK from your app.
curl https://api.basalt.dev/v1/views/revenue_by_min?limit=5 \ -H "Authorization: Bearer $BASALT_TOKEN"
What you get.
Idempotent upserts
Vectors are keyed by row ID, so retries overwrite instead of duplicating.
Metadata filters
Pick columns to send as metadata for filtered queries in Pinevale.
Deletes follow
Rows removed from the view are deleted from the index within seconds.
Namespace routing
Route tenants or environments to separate namespaces from one view.
Set your data in stone.
Free up to 10M events a month. No card, no sales call. Your first pipeline is live in about four minutes.