Benchmarks
Benchmark methodology
Reproducible tests instead of vibes. Here's exactly how we measure, and what's an estimate versus a real measurement today.
How we test
- Provision the target plan on each provider in the same region.
- Deploy an identical Docker Compose stack (pinned image versions).
- For Ollama: run a fixed prompt set per model, record tokens/second and first-token latency.
- For n8n / Supabase: run a fixed workflow / query load, record throughput and p95 latency.
- Publish raw numbers (CSV) so anyone can reproduce or challenge them.
Baseline resource estimates
Conservative starting points used by the calculator until measured data replaces them:
| Workload | min vCPU | min RAM | storage |
|---|---|---|---|
| n8n (automation) | 2 | 2 GB | 20 GB |
| Supabase (self-hosted) | 4 | 8 GB | 50 GB |
| Ollama (local LLM) | 4 | 8 GB | 50 GB |
| n8n + Ollama (AI ops combo) | 4 | 12 GB | 80 GB |
| n8n + Ollama + Supabase (full stack) | 8 | 24 GB | 200 GB |
estimate — replace with measured data per provider as benchmarks complete.