Zilliz

Zilliz Inc.·Zilliz.com
Company Overview

As of October 20, 2026: Zilliz is a vector lakebase.

It is self-serve with a free tier, is compliance-ready, and is scaling its team.

Backed by 155 dated facts
Drawn from 10 dimensions of the record, each dated and sourced.
The record, by dimensionevery dimension is its own page →
PricingBacked by 17 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Self-serve, free tier
$0–$2k/yr across Business Critical, BYOC (Bring Your Own Cloud), Enterprise (Dedicated), and Free +3 more, contact-sales, with a free tier, plus usage-based add-ons.
Full pricing read →
Features
Hybrid search platform
42 stated capabilities incl. hybrid search and RAG, 29 integrations.
Backed by 72 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Security
Compliance-ready
Holds SOC 2 Type II, HIPAA, and ISO 27001, plus GDPR, and 10 controls incl. Audit Logs, Encryption At REST, and Encryption In Transit.
Backed by 14 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Reliability
Dependable
A 99.95% uptime SLA.
Backed by 1 dated fact
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Hiring
Scaling
11 open roles across engineering, people, and sales, remote-friendly.
Backed by 6 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Stack
Detected + stated stack
Runs Angular, Auth0, AWS, and Cdnfonts +15 more on the live site (observed). Job postings additionally state Milvus, the backend stack fingerprinting can't see (company stated).
Backed by 23 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Positioning
Vector Lakebase
Leads with "The Vector Lakebase for AI". Frames itself for enterprise ai, against Elasticsearch and Milvus.
Backed by 6 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Funding
$103M raised across 3 rounds
$103M raised across Series B, Cumulative, and Series B Extension. Most recent: Series B Extension ($60M), 2022-08-24, led by Prosperity7 Ventures.
Backed by 9 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Location
Redwood City, US · +5 offices
Headquartered in Redwood City, US; offices in Berlin, DE, London, GB, New York, US, and Shanghai, CN +1 more.
Backed by 6 dated facts
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Legal
Zilliz Inc.
The registered entity is Zilliz Inc..
Backed by 1 dated fact
Every value derives from a dated, sourced capture — open any fact for its source.
Full read →
Change History683 dated events on the record
Funding details changed: Round Cumulative Announced On
Job-posting decline: Open Roles · high significance
Technology added: Reddit
Feature added: MCP Compatible
Technology removed: Go
Legal terms changed: Arbitration · high significance
Job-posting decline: Open Roles · high significance
IdentityBixel ID · free forever
Bixel IDbxc_0mgmny0hbstfbrandID 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/zilliz.com

{
  "data": {
    "company": {
      "name": "Zilliz",
      "domain": "zilliz.com",
      "categories": [
        "vector-databases"
      ]
    },
    "dimensions": {
      "reliability": {
        "facts": [
          {
            "key": "reliability.sla_pct",
            "value": 99.95,
            "provenance": "company_stated",
            "as_of": "2026-09-24",
            "source_url": "zilliz.com/sla"
          },
          {
            "key": "security.cert.hipaa",
            "value": true,
            "provenance": "company_stated",
            "as_of": "2026-09-24",
            "source_url": "zilliz.com/trust-center"
          },
          {
            "key": "hiring.open_roles",
            "value": 11,
            "provenance": "company_stated",
            "as_of": "2026-10-20",
            "source_url": "jobs.lever.co/zilliz/02848077-ca83-461e-87cd-e8b95d7f0c51"
          }
        ]
      },
      "…": "…"
    }
  }
}
MCPfor agents
# any MCP client (Claude, agents)
const record = await bixel.get_company({ domain: "zilliz.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.