Bixel

Turbopuffer

Turbopuffer Inc.·Turbopuffer.com
Company Overview

As of October 20, 2026: Turbopuffer is a vector and full-text search database built on object storage that holds SOC 2 Type II and supports indexes up to 256 TB, making it a credible option for teams with serious scale requirements.

Pricing runs from $16/month (Launch) to $256/month (Scale), with enterprise on contact-sales and usage-based add-ons like Log Streams at $128/month. The platform carries SOC 2 Type II, CCPA, and GDPR coverage alongside seven stated security controls including encryption at rest and in transit, which clears most enterprise procurement checklists without negotiation.

Backed by 44 dated facts
Drawn from 8 dimensions of the record, each dated and sourced.
integrations
2
Sep 2026
technologies
7
observed
dated changes
101
Sep 2026
The record, by dimensionevery dimension is its own page →
PricingBacked by 8 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Hybrid
Launch at $16/month and Scale at $256/month put the annual range at roughly $192 to $3,000 before usage add-ons; a team that needs audit Log Streams adds $128/month on top of their base tier, so costs can climb faster than the headline tiers suggest.
Full pricing read →
Features
Multi-tenancy platform
Six stated capabilities including multi-tenancy and two integrations, with a maximum index size of 256 TB; multi-tenancy support matters most to SaaS builders who need to isolate customer data within a single deployment rather than managing separate indexes per tenant.
Backed by 9 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Security
Compliance-ready
SOC 2 and SOC 2 Type II certifications, CCPA and GDPR privacy coverage, and seven controls including audit logs and encryption at rest and in transit are all stated; data residency is listed as global, so buyers with strict regional data requirements should confirm specifics before signing.
Backed by 12 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Reliability
Operational
A public status page exists and shows operational at time of observation; no public uptime history or SLA percentage is visible, so buyers cannot independently verify historical availability before committing.
Backed by 2 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Stack
Detected + stated stack
Next.js, React, and Tailwind CSS were observed on the live site; BM25 full-text search support is stated in job postings but not independently verifiable from the outside, which is relevant for buyers evaluating hybrid vector-plus-keyword search use cases.
Backed by 7 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Positioning
Vector And Full Text Search Database
The homepage headline "search every byte" and the claim of being "10x cheaper" built on object storage are company-stated; no independent benchmark is cited, so buyers should run their own cost comparison against current infrastructure before taking the figure at face value.
Backed by 3 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Location
1 office stated
One US office is listed but headquarters is not specifically stated; buyers requiring a named legal address for vendor registration may need to request that detail directly.
Backed by 1 dated fact
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Legal
turbopuffer Inc.
The registered entity is turbopuffer Inc. under Delaware, US law; arbitration terms, class-action waiver, and auto-renewal clauses are not stated publicly, so enterprise legal teams should request the full contract before assuming standard SaaS terms apply.
Backed by 2 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.Full read →
Change History101 dated events on the record
Positioning changed: Category
Positioning changed: Category
Feature added: Namespace Sharding
Feature removed: Full Text Search · high significance
Feature removed: Sharding · high significance
Pricing changed: Enterprise Usage Premium usage rate · high significance
Feature removed: Hybrid Search · high significance
IdentityBixel ID · free forever
Bixel IDbxc_ywdsctsc82hfbrandID in service · identity is free forever · permalink
Operated by

No registered company joined yet. Would resolve with: a registry identifier for the entity; a legal page on the site naming the registered company.

Registry identifiers

None on record.

Published identifiers

None read from the company's own pages yet.

Get this record via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/turbopuffer.com

{
  "data": {
    "company": {
      "name": "Turbopuffer",
      "domain": "turbopuffer.com",
      "categories": [
        "vector-databases"
      ]
    },
    "dimensions": {
      "security": {
        "facts": [
          {
            "key": "security.cert.soc2",
            "value": true,
            "provenance": "company_stated",
            "as_of": "2026-09-24",
            "source_url": "turbopuffer.com/pricing"
          },
          {
            "key": "stack.tech.bm25",
            "value": true,
            "provenance": "company_stated",
            "as_of": "2026-09-24",
            "source_url": "turbopuffer.com/jobs"
          }
        ]
      },
      "…": "…"
    }
  }
}
MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company({ domain: "turbopuffer.com" })

# returns the whole record above,
# each value with its source_url + as_of,
# ready to reason over
Build on the company record. One key, REST + MCP, every signal dated and sourced back to the page it came from.
How Bixel reads this

Every read above is derived from public signals, each sourced and dated, and kept honest about provenance: what the company states on its own pages and job posts (pricing, security, careers, positioning, its backend stack) versus what Bixel independently detects (technologies, infrastructure). Where a stated claim is also detected we mark it verified; where we only have the claim, we say so. Bixel infers posture: how it monetizes, how mature it is, where it's heading. It does notclaim private financials it can't observe. Where signals are thin, the record says so.

Public record, read from companies' own pages and boards. Every fact dated and sourced; provenance (observed vs company stated) shown inline.