turbovec tutorial

turbovec tutorial path with production handoff

A tutorial should end with a decision record. Use the planner to connect package install, index shape, bit width, search filters, and the next paid implementation step.

Input
Vector count, dimensions, bit width, framework, and filter policy.
Output
Memory estimate, migration risks, receipt JSON, and paid handoff path.
Boundary
Independent vector search planning workspace for teams evaluating turbovec and TurboQuant-compatible workflows. Not affiliated with Ryan Codrai, Google Research, FAISS, or the turbovec project.

turbovec tutorial

Index footprint planner

86
Float32 vectors TurboQuant packed index Filtered search receipt
Checkout Team annual
Float32 baseline57.22 GB

Raw embedding storage before index overhead.

Packed estimate7.45 GB

Estimated packed index with norms and id overhead.

Receipt

Workflow fit

For users who want to learn turbovec but also need a production-minded path.

Use it after a demo works locally and before the team chooses a compressed index for private RAG data.

  1. Pick Python or Rust and record the current vector store.
  2. Run the footprint estimate for the planned corpus.
  3. Export the receipt when the workflow needs saved notes or review.
Migration receiptPreview
  • Treating a benchmark claim as proof for a private corpus
  • Skipping recall checks after lowering bit width
  • Ignoring tenant or ACL filtering inside retrieval
  • Confusing an independent planner with the upstream open-source project

Capabilities

Built around real vector search migration decisions

The planner packages turbovec and TurboQuant-adjacent decisions into a commercial workflow instead of repeating an open-source README.

memory-sizing

Vector memory sizing

Input: Corpus size, embedding dimension, bit width, id policy, and filter mode

Process: Estimates float32 baseline, TurboQuant packed vectors, norm/correction overhead, and id map cost

Output: Memory delta, compression ratio, readiness score, and paid receipt

migration-receipt

FAISS to turbovec migration receipt

Input: Current vector store, framework, dataset shape, latency concern, and privacy boundary

Process: Maps the workload to Python or Rust turbovec paths, persistence files, and benchmark checks

Output: Migration review steps, risk notes, and checkout-gated team export

filtered-search-policy

Filtered search policy

Input: Tenant, ACL, SQL/BM25 candidate set, time window, or slot bitmask needs

Process: Captures where filtering happens and whether selective filters reduce wasted scan work

Output: Policy brief for engineering, security, and retrieval owners

framework-handoff

Framework handoff

Input: LangChain, LlamaIndex, Haystack, Agno, Python, or Rust target

Process: Converts the selected path into install, import, persistence, and validation notes

Output: Implementation receipt with exact package path and next step

Intent pages

Focused paths for turbovec and vector search questions

Each page answers a specific search intent and routes the visitor back to the planner, pricing, or hosted checkout.

Pricing

Public monthly pricing with yearly savings

Yearly billing is selected by default and shows the annual total divided by 12. Each checkout request preserves plan, billing, period, and planId.

Starter

Solo builders validating one vector search workload

$9.50/mo USD

Due today: $114 for one year. Annual billing is 50% less than monthly. No automatic renewal.

  • Browser memory sizing calculator
  • Three saved migration receipts
  • turbovec Python or Rust setup notes
  • Email support for checkout and activation
Checkout Starter annual

Scale

Platform teams standardizing compressed retrieval

$74.50/mo USD

Due today: $894 for one year. Annual billing is 50% less than monthly. No automatic renewal.

  • Multi-corpus planning and rollout scorecards
  • Private benchmark intake and review notes
  • Migration runbooks for Linux and VPC environments
  • Priority setup for paid implementation handoff
Checkout Scale annual