---
type: "post"
id: "on-demand-mode-for-pinecone-byoc-analysis-e48587"
slug: "on-demand-mode-for-pinecone-byoc-analysis-e48587"
title: "On-demand mode for Pinecone BYOC"
description: "Pinecone’s on-demand BYOC mode replaces per-index upfront sizing with a shared capacity pool."
retrieval_nugget: "Pinecone’s on-demand BYOC mode replaces per-index upfront sizing with a shared capacity pool."
published_at: "2026-10-15"
updated_at: "2026-10-15"
record_date: "2026-10-15"
date_kind: "published_at"
topics: ["retrieval","ai-infrastructure"]
source_urls: ["https://www.pinecone.io/blog/byoc-on-demand"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:on-demand-mode-for-pinecone-byoc-analysis-e48587"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:e46b60b46e1253de973c50baf417dada0c6f3cb200ac84de90b2da791c61b106","reviewed_at":"2026-10-15T23:07:15.668Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Pinecone’s on-demand BYOC mode replaces per-index upfront sizing with a shared capacity pool.","observed_facts":[{"text":"The announcement says on-demand mode is available now to every BYOC customer.","source_urls":["https://www.pinecone.io/blog/byoc-on-demand"]},{"text":"The post says indexes share a capacity pool and dynamic sharding directs new writes to shards with more room.","source_urls":["https://www.pinecone.io/blog/byoc-on-demand"]},{"text":"Pinecone says adding a shard leaves existing data in place and that a hot namespace can be moved to dedicated read nodes.","source_urls":["https://www.pinecone.io/blog/byoc-on-demand"]}],"mechanism":"Pinecone says dynamic sharding routes new writes to shards with more room; adding a shard does not require moving existing data.","why_now":"The feature is available now to every BYOC customer, and the post frames it around workloads with many namespaces, including one per tenant or agent user.","implications":["BYOC teams can treat capacity as a pool-level decision rather than sizing every index separately.","A hot namespace can be moved to an index with dedicated read nodes in the same environment."],"evidence_boundary":"The evidence boundary is Pinecone’s product description: it gives no pricing, comparative benchmark, or independent validation of scaling behavior.","watch_conditions":["Watch whether customers can operate mixed shared and dedicated workloads predictably as query concentration changes."],"related_records":[],"new_branch_reason":"No prior New Runtime record is supplied; this product-capacity mode creates a distinct record about BYOC scaling mechanics."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/on-demand-mode-for-pinecone-byoc-analysis-e48587/","markdown":"https://newruntime.com/posts/on-demand-mode-for-pinecone-byoc-analysis-e48587.md","json":"https://newruntime.com/posts/on-demand-mode-for-pinecone-byoc-analysis-e48587.json"}
---

# On-demand mode for Pinecone BYOC

## Retrieval answer

Pinecone’s on-demand BYOC mode replaces per-index upfront sizing with a shared capacity pool.

Pinecone’s on-demand BYOC mode replaces per-index upfront sizing with a shared capacity pool. The mechanism is the important change. Pinecone says dynamic sharding routes new writes to shards with more room; adding a shard does not require moving existing data. This is the operational mechanism described in the announcement, not an independently tested performance result.

Why now: The feature is available now to every BYOC customer, and the post frames it around workloads with many namespaces, including one per tenant or agent user. The company says the pool can hold millions of namespaces and that customers can add capacity as data grows. This could reduce the need to forecast each index’s capacity independently; it does not establish lower total cost or eliminate capacity planning.

The first implication is that BYOC teams can treat capacity as a pool-level decision rather than sizing every index separately. A second operational option remains for a hot namespace: Pinecone says it can be moved to an index with dedicated read nodes in the same environment. The evidence boundary is Pinecone’s product description: it gives no pricing, comparative benchmark, or independent validation of scaling behavior. Watch whether customers can operate mixed shared and dedicated workloads predictably as query concentration changes.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Retrieval](https://newruntime.com/topics/retrieval.md): Explore the retrieval topic hub.
- topic hub: [Ai Infrastructure](https://newruntime.com/topics/ai-infrastructure.md): Explore the ai-infrastructure topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)