Turbopuffer

Turbopuffer Inc.·Turbopuffer.com
Technology Stack

Detected + stated stack

As of September 24, 2026, Turbopuffer's 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.
Detected on the live site · observed
Linkedin InsightNext.jsReactTailwind CSSVercelYoutube
Stated in job postings · stated, unverified
BM25
Subdomain surface · 2 crawled
www.turbopuffer.comcrawled · observed
Next.jsReactTailwind CSSVercelLinkedIn Insight
status.turbopuffer.comcrawled · observed
Next.jsReactTailwind CSSVercel
Stack Change Historydated events · values unlock with a key
Technology added: BM25
Technology removed: BM25 · high significance
Technology added: BM25
Technology removed: BM25 · high significance
Technology added: Linkedin Insight
Every stack fact on this pagekey · value · provenance · dated · sourced
FactValueProvenanceAs ofSource
stack.tech.bm25BM25company stated2026-09-24turbopuffer.com/jobs
stack.tech.linkedin-insightLinkedin Insightobserved2026-09-24turbopuffer.com
stack.tech.nextjsNext.jsobserved2026-09-24turbopuffer.com
stack.tech.reactReactobserved2026-09-24turbopuffer.com
stack.tech.tailwindcssTailwind CSSobserved2026-09-24turbopuffer.com
stack.tech.vercelVercelobserved2026-09-24turbopuffer.com
stack.tech.youtubeYoutubeobserved2026-08-03turbopuffer.com/customers/cursor
Stack across Vector DatabasesTurbopuffer ranked in place · tap through for each read
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 stack for turbopuffer.com via API / MCPevery field dated and sourced
RESTopen tier
GET https://api.bixel.com/v1/companies/turbopuffer.com/facts?dimension=stack

{
  "data": {
    "facts": [
      {
        "key": "stack.tech.bm25",
        "value": true,
        "provenance": "company_stated",
        "as_of": "2026-09-24",
        "source_url": "turbopuffer.com/jobs"
      },
      {
        "key": "stack.tech.linkedin-insight",
        "value": true,
        "provenance": "observed",
        "as_of": "2026-09-24",
        "source_url": "turbopuffer.com"
      },
      {
        "key": "stack.tech.nextjs",
        "value": true,
        "provenance": "observed",
        "as_of": "2026-09-24",
        "source_url": "turbopuffer.com"
      },
      {
        "key": "stack.tech.react",
        "value": true,
        "provenance": "observed",
        "as_of": "2026-09-24",
        "source_url": "turbopuffer.com"
      },
      "…"
    ]
  }
}
MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company_facts({ domain: "turbopuffer.com", dimension: "stack" })

# returns the stack 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.

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