Single-Node → Multi-Node
Single-node capacity
Section titled “Single-node capacity”A single Remem node (remem-server) scales to millions of memories, bounded
primarily by RAM for the HNSW index — roughly 1GB per 500K memories at 384 dims.
For most single-product use cases, a single node on a $20–40/month VPS is sufficient.
Signals you need multi-node
Section titled “Signals you need multi-node”| Signal | Explanation |
|---|---|
| Write throughput saturated | Single node can’t keep up with ingestion rate |
| RAM pressure | HNSW index growing beyond available RAM |
| Zero-downtime requirement | You need HA failover; single node has none |
| Multi-tenant isolation | Separate data planes per customer |
What multi-node adds (Business — Coming soon)
Section titled “What multi-node adds (Business — Coming soon)”None of the following ships in the Community Edition today. Horizontal sharding, replication, HA failover, the management backoffice, and enterprise auth are all part of the planned Business Edition “Multi-Node” offering, coming soon:
- Horizontal sharding — memories are distributed across nodes by consistent hashing
- Replication — each shard has N replicas; writes are durable if any replica acknowledges
- HA failover — leader election per shard; surviving replicas elect a new leader on failure
- Centralised management — a web-based Backoffice admin UI manages all nodes, handles rebalancing
- Enterprise auth — SSO/SAML, per-team API keys, audit logs
- Observability — Prometheus/Grafana monitoring across the cluster
Upgrade path
Section titled “Upgrade path”Multi-Node is Business — Coming soon. Join the waitlist to be notified when it’s available.
When it ships, the upgrade path will be:
- Stand up N additional nodes
- Point them at the management backoffice
- Trigger a rebalance — the backoffice migrates shards automatically
- Update your clients to the cluster endpoint (the API is the same)
Your existing single-node data migrates without downtime.