Sure runs a web service, Sidekiq worker, PostgreSQL and Redis. Heavy imports, categorization, reporting and jobs can increase memory across several services at once.
For users importing large financial histories or running frequent background synchronization.Sure Hardware Requirements: RAM, CPU, Storage & Personal Finance
Learn Sure hardware requirements for RAM, CPU, PostgreSQL, Redis, Sidekiq, AI features, Docker and ZimaOS hardware.
Sure hardware requirements at a glance
Sure is the actively maintained community fork of the archived Maybe Finance project. Current upstream self-hosting uses a multi-service stackโRails web, Sidekiq worker, PostgreSQL 16 and Redisโbut does not publish one universal CPU or RAM minimum.
- CPU
- Sure upstream does not publish one universal CPU-core minimum. The current Community Scripts Proxmox profile uses 2 CPU cores, which is a useful practical small-server reference rather than an upstream requirement.
- RAM
- Sure upstream does not publish one universal system-RAM minimum. Community Scripts currently defaults to 2048 MiB RAM for its LXC deployment. By contrast, the current ZimaOS package reserves 1 GB each for web, worker, PostgreSQL and Redisโ4 GB of reservations in total. Those are deployment/package choices, not universal minimums.
- Application stack
- Current upstream Docker Compose runs a Rails web service, Sidekiq worker, PostgreSQL 16 and Redis. These services should be sized as one application stack rather than treating Sure as a single lightweight web container.
- Storage
- Persist Rails application storage, PostgreSQL data and Redis data, and keep database data on reliable SSD-backed storage. Community Scripts currently allocates a 6 GB LXC disk, but long-term capacity should also include finance data, uploads, AI/RAG state if enabled and backups.
- AI
- Sure can call OpenAI and current releases add broader AI functionality, but a local GPU is not required when the model provider is remote. GPU/VRAM becomes a separate requirement only if you deliberately run a local model backend.
- Best Zima starting point
- ZimaBoard 2 832 with 8 GB RAM is a sensible current starting point for the full Sure stack and exceeds both the 2-GB Community Scripts profile and the 4-GB aggregate ZimaOS reservations. Choose 1664 when more financial imports, AI/RAG work or other home-server apps share the host.
From official requirements to the right setup
Sure sizing starts with the full four-service Docker stack, then adds finance-data volume, background jobs, imports, optional AI features, backup retention and other ZimaOS services.
-
Official requirements
Treat Sure as web + Sidekiq + PostgreSQL + Redis, not as one Rails container. Current upstream compose uses all four services and persistent storage for the application and PostgreSQL.
-
Confirm your needs
Use third-party numeric tiers only in context. Community Scripts currently provisions 2 CPU, 2048 MiB RAM and 6 GB disk for its Sure LXC, while ZimaOS reserves 1 GB for each of four services. Neither source defines the upstream minimum.
-
Leave room to grow
Plan SSD-backed persistent data for PostgreSQL and application storage. Add backup capacity separately and allow more space if transaction imports, account history, documents or AI/RAG features expand data volume.
-
Run it on ZimaOS
Run representative account imports, categorization, reports and background jobs while monitoring Rails/Sidekiq RAM, PostgreSQL RAM/I/O and Redis usage. Upgrade the host only when the complete Sure stack or co-hosted services show sustained pressure.
Check every playback client
- Current Sure version and Docker deployment method
- Rails web and Sidekiq worker concurrency
- PostgreSQL database size and active working set
- Redis background-job/cache workload
- Transaction imports and account-sync frequency
- Optional AI/RAG/provider features
- Application/database/Redis backup retention
- Other ZimaOS apps sharing CPU, RAM and SSD
Official minimum requirements
Current Sure upstream documentation describes the required software stack but does not publish one universal production CPU/RAM/disk table. The most useful numeric evidence comes from current deployment profiles and the current ZimaOS package, which must be labeled as such.
Do not call 2 GB, 4 GB or 6 GB 'the Sure minimum.' Community Scripts shows that a 2-core/2-GB/6-GB LXC is a viable deployment profile, while ZimaOS reserves 4 GB across its four containers. For current ZimaOS hardware planning, 8 GB host RAM is the safer starting class because the OS and other services also need memory.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Upstream CPU minimum | No universal official minimum published | Current Sure README and Docker example define software dependencies rather than one hardware floor. |
| Upstream RAM minimum | No universal official minimum published | The standard upstream Compose file does not set memory reservations or hard limits. |
| Upstream services | Rails web + Sidekiq + PostgreSQL 16 + Redis | Current standard self-host Docker topology. |
| Community Scripts profile | 2 CPU, 2048 MiB RAM, 6 GB HDD | Current Proxmox LXC default profile; useful deployment evidence, not upstream minimum. |
| ZimaOS aggregate reservations | 4 GB total | Current manifest reserves 1 GB each for Sure web, Sidekiq worker, PostgreSQL and Redis; these are reservations, not hard limits. |
| ZimaOS architectures | amd64 and arm64 | Current Sure package supports both architectures and is categorized under Finance. |
When to upgrade your hardware
Sure hardware upgrades are driven by database/worker activity, imports, AI features and the rest of the home-server stack.
PostgreSQL and background jobs push the host into memory pressure
AI/RAG features add separate application and provider load
Sure becomes one service in a much larger home-server stack
Current Sure releases continue expanding AI features. Remote providers do not require a local GPU, but application-side jobs, embeddings/RAG state and longer-running requests can still add RAM, CPU and database activity.
For users enabling AI-assisted finance workflows rather than basic tracking only.Nextcloud, monitoring, media, automation and databases can consume more resources than Sure. Upgrade based on the combined host rather than the finance app alone.
For all-in-one ZimaOS systems.Plan hardware growth with confidence
Sure scales most safely by separating active database/app data, backup capacity and optional AI workloads.
Put PostgreSQL and Rails storage on SSD
The ZimaOS package persists Rails storage and PostgreSQL separately. Low-latency SSD-backed AppData is more appropriate than treating small onboard eMMC as the long-term finance database.
Use SATA/NVMe SSD for Sure AppData and PostgreSQL.Keep database and application backups outside the live data path
The upstream Compose file even includes an optional PostgreSQL backup service profile. Backups should not consume all space allocated to the active database.
Use separate HDD/SSD or NAS backup capacity.Use 16 GB when the whole four-service stack plus other apps needs it
Moving from 8 GB to 16 GB provides more room for PostgreSQL, Sidekiq, Redis and co-hosted services, but it is not an upstream Sure requirement.
Choose ZimaBoard 2 1664 for measured memory pressure.Treat local AI as a separate hardware layer
Sure can use remote AI providers without a GPU. If a local model backend is added, size its RAM/VRAM/model storage independently.
Choose GPU-capable hardware only when local inference is explicitly required.Can it run on ZimaOS?
Sure is currently available in the ZimaOS App Store under Finance. The current ZimaOS package uses Sure 0.6.5-hotfix.1 and runs four services.
Install Sure from the ZimaOS App Store
The current package uses ghcr.io/we-promise/sure:0.6.5-hotfix.1 for both web and Sidekiq worker, plus PostgreSQL 16 and Redis 8.2.1.
Open Sure in the ZimaOS App StoreInterpret the four 1-GB reservations correctly
Sure web, worker, PostgreSQL and Redis each reserve 1024 MB in the current manifest. Reservations do not mean each service always consumes 1 GB, and they are not hard limits or an upstream hardware minimum.
Review the ZimaOS Sure manifestWatch the package-to-upstream version gap
Current upstream Sure releases are newer than the ZimaOS 0.6.5-hotfix.1 image. Validate app updates and migration notes before assuming the package contains every new upstream AI or finance feature.
Check current Sure releasesChoose Zima hardware for your Sure workload
Sure is more substantial than a single lightweight web app because it includes Rails, Sidekiq, PostgreSQL and Redis. ZimaBoard 2 832 is still the natural current starting point; larger Zima hardware is justified by heavier finance data, more services or broader NAS/AI workloads.
Is Sure mainly a personal/family finance stack, or part of a larger multi-app database/AI home server?
Personal/family Sure with modest imports and services
Start with ZimaBoard 2 832. Its 8 GB RAM provides useful headroom over both the 2-GB Community Scripts LXC and the 4-GB aggregate ZimaOS reservations. Add SSD storage for PostgreSQL and application data.
- Personal/family Sure stackZimaBoard 2 832
- More imports, background jobs and co-hosted appsZimaBoard 2 1664
Broader database/NAS/AI home-server workload
Choose ZimaCube 2 when storage, backups and the wider application stack justify it. Pro provides more balanced CPU/RAM/network headroom; Creator Pack is only for a separate local-GPU workload.
- Storage-first finance/archive serverZimaCube 2 Standard
- Heavier multi-service finance/database stackZimaCube 2 Pro
- Only when local GPU inference is independently requiredZimaCube 2 Creator Pack
This is a workload guide, not a fixed account/transaction benchmark. Import volume, PostgreSQL growth, background jobs, AI features and other ZimaOS applications can materially change resource needs.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Personal/family Sure and a modest self-hosted finance stack. | Sure web, Sidekiq, PostgreSQL, Redis, imports and several light ZimaOS apps. |
|
Use added SSD for PostgreSQL and Rails storage; 32 GB eMMC is not ideal for long-term multi-container finance data. | Get Now |
| ZimaBoard 2 1664 | Sure with heavier imports, AI/RAG work and more co-hosted services. | Larger PostgreSQL data, Sidekiq jobs, Redis, monitoring and additional containers. |
|
Do not claim Sure requires 16 GB; choose it for measured system-wide memory demand. | Get Now |
| ZimaCube 2 Standard | Storage-first finance/NAS system with larger backup and document retention. | Sure plus household storage, backups and moderate services. |
|
Still 8 GB RAM; choose 1664 instead if memory is the constraint and six bays are unnecessary. | Get Now |
| ZimaCube 2 Pro | Heavier all-in-one finance/database/NAS home server. | Sure, databases, backups, many containers and broader storage/network services. |
|
Database tuning and SSD latency can remain bottlenecks; Pro is unnecessary for basic personal finance. | Get Now |
| ZimaCube 2 Creator Pack | Sure on a server independently required for local AI/GPU workloads. | Sure plus separate local AI, GPU or creator services. |
|
Extreme overkill for Sure alone. | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
โZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.โRead full review
โThe ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.โRead full review
โZimaCube 2: A modern, high-performance NAS with plenty of room to growโbuilt for users who want more than basic storage.โRead full review
โCoverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.โRead full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
โ
โ
โ
โ
โ
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
โ
โ
โ
โ
โ
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
โ
โ
โ
โ
โ
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
โ
โ
โ
โ
โ
Avaliaรงรฃo ZimaBoard 2
Construรญ um servidor de uso pessoal. O desempenho estรก muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa รฉ nรฃo dependermos de grandes estruturas para termos nosso prรณprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele รฉ simples e eficiente.
Frequently asked questions
The supplied Sure sources describe the project and two different deployment contexts. Numeric requirements are labeled by source rather than promoted into a universal upstream minimum.
How much RAM does Sure need?
Sure upstream does not publish one universal RAM minimum. Community Scripts currently deploys Sure in a 2-GB LXC, while the ZimaOS package reserves 1 GB for each of four services, or 4 GB in aggregate. For ZimaOS, an 8-GB host is a sensible starting class.
Is 2 GB RAM the official Sure minimum?
No. 2048 MiB is the current Community Scripts default LXC profile. It proves a deployment can be provisioned at that size but is not an upstream requirement.
Why does ZimaOS reserve 4 GB total?
The current package reserves 1 GB each for the Rails web service, Sidekiq worker, PostgreSQL and Redis. Docker reservations are scheduling/resource metadata; they do not mean each container always consumes 1 GB or that 4 GB is a hard minimum.
Does Sure need PostgreSQL and Redis?
Yes in the current standard self-host stack. Upstream Compose uses PostgreSQL 16 for persistent finance data and Redis for Sidekiq/background work.
Does Sure require a GPU for AI insights?
No when Sure calls OpenAI, Anthropic or another remote provider. A local GPU only becomes relevant if you separately deploy a local model backend.
What does daily.dev add to hardware sizing?
The supplied daily.dev page is essentially a summary of the Sure GitHub project and confirms that Sure is the community-maintained fork of abandoned Maybe Finance and is self-hosted through Docker. It does not publish independent CPU/RAM requirements.
What does Community Scripts recommend?
Its current default Sure LXC profile uses Debian 13, 2 CPU cores, 2048 MiB RAM and 6 GB HDD. Treat this as a practical Proxmox deployment profile.
Can ZimaBoard 2 832 run Sure?
Yes. Four N150 cores and 8 GB RAM provide a reasonable current starting configuration for Sure's web, worker, PostgreSQL and Redis stack. Use SSD-backed persistent data and move to 16 GB only when the whole host needs more memory.
What sources and further reading informed this Sure hardware guide?
The upstream Sure repository is the primary source: it confirms Sure is the actively maintained community fork of archived Maybe Finance, is self-hosted with Docker, and its current standard Compose uses Rails web, Sidekiq, PostgreSQL 16 and Redis without publishing a universal hardware minimum. The supplied daily.dev page summarizes that same project and does not add independent sizing numbers. Community Scripts provides a concrete current Proxmox profile of 2 CPU cores, 2048 MiB RAM and 6 GB disk; this is retained as deployment evidence rather than called an upstream minimum. Current ZimaOS Sure manifest data was additionally checked and shows four 1-GB memory reservations across web, worker, PostgreSQL and Redis.
