Our Story

We run the index so you do not

One retrieval layer, one number to hold us to, and nobody on your team paged at 3am.

Talk to an engineer

Nodeform started in 2023, after the two founders spent a year running a vector index nobody had budgeted for. It worked at ten million embeddings and fell over at two hundred. The fix was never clever — it was sharding, recall harnesses and a rebuild schedule, week after week. We decided that work should belong to one team, not every team. So we run it, we publish the latency, and we put a number in the contract.

[ core values ]

Our Values

01

Reliability First

A retrieval layer should be boring. Boring is the whole product.

[ Uptime · 30 days ]
99.99%
[ from the team ]

We don't ship
what we wouldn't use.

— 47 engineers · nodeform 2026
[ Composable graph ] STORAGE SOURCES STACK FORMATS TOOLS LANGS
[ Interop matrix ]
JSON
PARQUET
AVRO
PROTOBUF
ARROW
OPENAPI
GRPC
OTLP
OPENMETRICS
0 + open formats · zero lock-in
Open standards
[ our journey ]

Our Journey

Today we hold 12 billion vectors across nine regions and answer roughly 40,000 queries a second at peak. The index has never been the interesting part. That is the point.

12B+ Vectors Indexed
24ms p99 Latency
99.9% Uptime SLA
9 Regions
[ get started ]

Ready to stop running your own vector index?

Read the quickstart, or talk to the engineer who will run your index.