# Self-hosting Weaviate on a Canadian VPS

**URL:** <https://forum.weaviate.io/t/self-hosting-weaviate-on-a-canadian-vps/22864>\
**Category:** Support\
**Created:** [November 16, 2026, 4:44pm UTC](https://forum.weaviate.io/t/self-hosting-weaviate-on-a-canadian-vps/22864 "2026-11-16T16:44:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![4GoodHosting](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/4goodhosting/32/8099_2.png) [@4GoodHosting](https://forum.weaviate.io/u/4GoodHosting)\
**Post date:** [November 16, 2026, 4:44pm UTC](https://forum.weaviate.io/t/self-hosting-weaviate-on-a-canadian-vps/22864/1 "2026-11-16T16:44:02Z")

</div>

I’m planning a self-hosted Weaviate instance for a client whose data has to stay in Canada. PIPEDA, BC public body rules and Quebec Law 25 all push us toward keeping the vectors, source documents and backups on Canadian servers, so we’re running Weaviate ourselves on a Linux VPS instead of a managed service in a US region. I’d like a sanity check from people who self-host it.

**1. Sizing.** For about 2 million objects with 768-dimension vectors, is 8 vCPU / 32 GB RAM a sensible starting point?

**2. Memory.** How do you estimate HNSW memory use, and is vector compression (PQ or BQ) worth turning on from day one?

**3. Disk.** Local NVMe vs network block storage for the data directory: how much does it matter?

**4. Deployment.** Docker Compose on a single node, or go straight to Kubernetes with the Helm chart?

**5. Vectorizer.** Run the embedding model on the same VPS, or keep it on a separate box?

**6. Backups.** Do you use the backup module to an S3-compatible bucket, or filesystem snapshots?

**7. Security.** API key auth behind an Nginx reverse proxy with TLS: anything else you’d add?

What would you change in this setup, and what surprised you the first time you self-hosted Weaviate?

---

<div class="post-metadata">

**Author:** ![oliviadavis](https://avatars.discourse-cdn.com/v4/letter/o/67e7ee/32.png) [@oliviadavis](https://forum.weaviate.io/u/oliviadavis)\
**Post date:** [November 17, 2026, 4:58pm UTC](https://forum.weaviate.io/t/self-hosting-weaviate-on-a-canadian-vps/22864/2 "2026-11-17T16:58:03Z")

</div>

8 vCPU/32 GB is a reasonable starting point for 2M×768, but memory is the constraint: raw vectors are ~6 GB (2M×768×4 bytes), and HNSW graph/link overhead can add a similar order again. Benchmark recall and memory with PQ/BQ before enabling day one; compression saves RAM but costs CPU/recall. Use local NVMe if possible—network block storage hurts latency and rebuilds. Compose on one node is fine unless you need HA; keep the embedding model separate if it’s heavy. Back up via the backup module to Canadian S3 plus periodic snapshots, and lock down ports/firewall, TLS, API keys, encrypted backups. Monitor memory first.
