fshy / Databases and KV

Weaviate Cloud

weaviate.io · Databases and KV · 1 record · JSON

Weaviate Cloud Databases and KV

caveatemailno cardDper-object-cap

weaviate.io/pricing · vector database · databases-kv/weaviate-cloud · JSON · compare

Free tier	1 cluster per user, 100,000 objects, 1 GB memory, 10 GB disk, 1 collection, up to 3 tenants, always free unit objects; metered on object-count
Price	none stated
Per-object cap	100,000 objects per cluster; 1 collection
Retention	always free, with no deletion clock published
Egress	not published on the pricing page; recorded as a gap
Identity	email email signup; no card on Free
Limits	per-object-cap 100,000 objects and one collection source request-rate one cluster per user; three tenants source request-rate no connection limit is published for the sandbox; recorded as a gap source
Binding	per-object-cap
Interface	rest, cli a REST API and GraphQL; Python, TypeScript, Java and Go clients
Tooling	the weaviate-client libraries; GraphQL for queries
Composes with	the only free vector tier that caps objects rather than bytes, so it is the right shape for many small records and the wrong shape for a few large ones
Reliability	no reliability event recorded
Notes	One collection is the constraint that decides it. A multi-tenant design that needs a collection per tenant stops at one, and a single collection with 100,000 objects is a small index.
Evidence rung	documented the pricing page was read today.
Checked	2026-10-23 (live); stale on 2026-11-22

Evidence (1)

date	source	what it proved
2026-10-22	weaviate.io/pricing	Free: 'Always free - 1 cluster per user'; '100,000 objects - 1 GB memory - 10 GB disk'; '1 collection, up to 3 tenants'; the comparison table repeats object limit 100,000 and collection limit 1

Unknown or withheld values (2)

$.egress.metered egress-unknown
$.reliability_note none-observed

Built from commit 872967ae41, data as of 2026-10-27. Every value links to its source; freshness badges are computed in your browser. How to read this.