SFTPGo Community Editionのハードウェア要件：RAM、CPU、ストレージ、ファイル転送スループット
RAM、CPU、ファイルストレージ、転送同時実行数、データプロバイダー、実用的なZimaOSデプロイ向けに、SFTPGo Community Editionのハードウェアを計画する。
SFTPGo Community Edition hardware requirements at a glance
Size SFTPGo Community Edition from verified upstream requirements first, then add headroom for the workload and persistent data.
- RAM
- No numerical official minimum published
- CPU
- No numerical official minimum published
- Storage
- Size for user data, temporary transfer behavior, logs, and backups
- Data provider
- SQLite is the default configuration in the Community repository
- Networking
- Throughput and simultaneous transfers are first-class sizing variables
- Best Zima starting point
- ZimaBoard 2 832 for a small file endpoint
From official requirements to the right setup
Treat SFTPGo as a protocol and storage gateway: size transfer concurrency, encryption work, network throughput, data-provider behavior, and the actual file repository separately.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Concurrent transfers
- Protocol mix
- Local vs object storage
- Data-provider choice
- User data capacity
- Upload/download throughput
- TLS/encryption load
- Backup retention
Official minimum requirements
The Community project documents supported protocols, storage backends, and configuration, but does not publish a single numerical host CPU/RAM minimum.
Do not invent a 1 GB or 2 GB host minimum. For a small deployment, SFTPGo itself is usually light; file capacity, network throughput, permissions, and concurrency are the practical sizing variables.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Size for encryption, TLS, checksums, hooks, and transfer concurrency. | |
| No numerical official minimum published | Depends on active sessions and enabled services. | |
| SQLite in the default Community configuration | Other providers can be used for different deployment topologies. | |
| SFTP, HTTP/S, FTP/S, WebDAV | Enable only what the deployment needs. | |
| Local/encrypted local, S3-compatible, GCS, Azure Blob, other SFTP servers | Backend choice changes local-capacity requirements. | |
| Not required | SFTPGo has no GPU sizing requirement. |
When to upgrade your hardware
Transfer concurrency
Metadata/database growth
Local file growth
Plan hardware growth with confidence
Fast metadata storage
Keep SFTPGo configuration, provider data, and active logs on reliable SSD storage.
SSDMore memory
Add RAM when many sessions, hooks, or co-located containers compete for memory.
Higher-RAM hostLarger file pool
Use a multi-bay storage platform when SFTPGo is the gateway to a growing local repository.
ZimaCube-class storageFaster network path
Upgrade network and disk throughput when transfer speed, not application logic, becomes the bottleneck.
2.5GbE/10GbE plus adequate disksCan it run on ZimaOS?
Custom install SFTPGo Community Edition in ZimaOS
A specific public official ZimaOS App Store page was not verified, so this page uses the required Custom Install route even though community users report installing SFTPGo from the visual app library.
Custom install SFTPGo Community Edition in the ZimaOS app ↗Use the Community project documentation
The Community Edition is AGPLv3, community supported, and includes the core protocols, storage backends, and Web UIs.
Open SFTPGo Community documentation ↗Preserve storage permissions
When mapping ZimaOS storage into the container, verify UID/GID, bind mounts, and write permissions before exposing the service.
Open SFTPGo repository ↗Zima hardware for SFTPGo Community Edition
For small SFTP endpoints, CPU and RAM are modest; local file capacity and network throughput are usually the first reasons to move beyond ZimaBoard.
Choose by workload
Use a low-power host and size disks for the files rather than overbuying CPU.
Storage topology and network bandwidth become more important than baseline app memory.
This mapping is not an upstream certification. Community-edition resource demand varies with protocols, transfers, hooks, backend choice, and co-located services.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Light self-hosted services and small persistent workloads | Single-app or small multi-app home-server deployments |
|
8 GB RAM and N150 CPU limit heavy databases, large observability stacks, and compute-heavy jobs | Get Now |
| ZimaBoard 2 1664 | Apps that benefit from more memory while retaining a low-power 4-core CPU | Larger database cache, more containers, and moderate background services |
|
The CPU is still the same 4-core N150; 16 GB RAM does not raise compute throughput | Get Now |
| ZimaCube 2 Standard | Storage-heavy services, archives, and growing file libraries | Large persistent data sets where drive bays matter more than CPU throughput |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy applications | Get Now |
| ZimaCube 2 Pro | CPU-heavy, higher-concurrency, database-heavy, and consolidated workloads | More background workers, indexing, reports, or concurrent users |
|
16 GB RAM can still be the limiting factor for software that needs substantially more memory | 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
How much RAM does SFTPGo Community Edition need?
Upstream does not publish a universal numerical host-RAM minimum for the Community Edition.
How many CPU cores does SFTPGo need?
No numerical official CPU minimum is published; encryption, TLS, checksums, hooks, and concurrent transfers drive CPU demand.
Which database does SFTPGo use?
The default Community configuration uses SQLite, while SFTPGo also supports other data-provider choices for different deployment needs.
How much storage does SFTPGo need?
Application storage is small compared with the files you serve. Size local disks for user data, temporary transfer behavior, logs, snapshots, and backups.
Does SFTPGo need a GPU?
No GPU requirement is published.
Can ZimaBoard 2 run SFTPGo?
Yes as a practical small-deployment starting point; the 832 model is usually enough unless other containers, many transfers, or large local storage change the requirement.
What usually becomes the bottleneck?
For many deployments it is network throughput, disk I/O, or storage capacity before raw application RAM.
When should I choose ZimaCube 2?
Choose it when SFTPGo fronts a large local repository, needs multiple drive bays, or higher network/storage throughput.
