Sharetribes maskinvarukrav: RAM, CPU, lagring och marknadsplatsstack
Planera Sharetribe-hårdvara genom att först identifiera driftsmodellen: aktuell hosting av Sharetribe-frontenden eller äldre självhosting av Sharetribe Go.
Sharetribe hardware requirements at a glance
Size Sharetribe from verified upstream requirements first, then add headroom for the workload and persistent data.
- RAM
- No universal numerical official minimum published
- CPU
- No universal numerical official minimum published
- Storage
- Front-end hosting is light; legacy Go adds database, search, uploads, logs, and backups
- Database
- Current marketplace backend is Sharetribe-hosted; legacy Sharetribe Go uses MySQL
- Maintenance status
- Sharetribe Go is no longer actively maintained
- Best Zima starting point
- ZimaBoard 2 832 for the current Web Template front end
From official requirements to the right setup
First identify which Sharetribe architecture the page is about. The current Web Template is a self-hosted Node/Express front end connected to Sharetribe services; Sharetribe Go is an older, no-longer-actively-maintained full stack.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Current Web Template vs Sharetribe Go
- Node.js server requirement
- Expected concurrent users
- Image and asset strategy
- Legacy MySQL size
- Legacy Sphinx index size
- Background jobs
- Backup plan
Official minimum requirements
Sharetribe does not publish one numerical host minimum that covers both its current front-end hosting model and the legacy Sharetribe Go full stack.
Do not label a community VPS suggestion as an official minimum. The most important requirement is architectural: current Sharetribe usually self-hosts the front end only, while legacy Sharetribe Go is a separate, older stack.
| Requirement | Official minimum | What this supports |
|---|---|---|
| No numerical official minimum published | Depends on deployment model and marketplace workload. | |
| No numerical official minimum published | Current template is Node/Express; legacy Go is a larger Rails stack. | |
| Node.js/Express server | Serverless-only platforms are unsuitable for the Web Template. | |
| MySQL 8.4 in the current Sharetribe Go repository | Only MySQL is documented/tested there. | |
| Sphinx | Adds index storage and service overhead. | |
| Sharetribe Go is no longer actively maintained | Treat it as legacy software. |
When to upgrade your hardware
Front-end traffic
Legacy database/search pressure
Upload and backup growth
Plan hardware growth with confidence
SSD runtime
Keep Node/Rails runtime and any local legacy database on SSD.
SSDRAM for legacy services
Legacy Rails, MySQL, Sphinx, and workers need more headroom than the current front-end-only model.
More RAMExternal object storage
Move marketplace images and uploads away from small system disks.
S3-compatible/object storageCPU for SSR and jobs
Increase CPU when server-side rendering or legacy background jobs become latency-sensitive.
Higher-throughput CPUCan it run on ZimaOS?
Custom install Sharetribe in ZimaOS
No specific public official ZimaOS one-click page was verified. Define the Sharetribe architecture before creating a container stack.
Custom install Sharetribe in the ZimaOS app ↗Current Sharetribe Web Template
The current custom-code model runs a Node.js/Express front end while core marketplace services remain with Sharetribe.
Open Sharetribe deployment documentation ↗Legacy Sharetribe Go
The old source-available full stack remains available but is explicitly no longer actively maintained.
Open Sharetribe Go repository ↗Zima hardware for Sharetribe
Do not size “Sharetribe” until you know whether the workload is the current front-end template or the legacy full Sharetribe Go stack.
Choose by workload
A small Node/Express front end is usually light; traffic and SSR concurrency determine whether you need more CPU.
Treat Rails, MySQL, Sphinx, workers, uploads, and backups as separate resource consumers.
The Zima mapping below separates those models and does not imply that Sharetribe endorses ZimaOS or that the legacy Go stack is the preferred current deployment.
| 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 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 Sharetribe need?
There is no single numerical official minimum because current Sharetribe front-end hosting and legacy Sharetribe Go are different architectures.
How many CPU cores does Sharetribe need?
No universal official CPU minimum is published; current Web Template traffic and legacy background services drive CPU demand.
Does Sharetribe need a database on my server?
The current custom-code Web Template uses Sharetribe's marketplace backend, while legacy Sharetribe Go uses a self-managed MySQL database.
Does the current Sharetribe Web Template need a server?
Yes. Official guidance says it needs a host that can run a Node.js/Express server; serverless-only platforms are unsuitable.
Is Sharetribe Go still maintained?
The official repository states that Sharetribe Go is no longer actively maintained.
Can ZimaBoard 2 host the Sharetribe Web Template?
Yes as a practical small front-end host, assuming your marketplace backend remains on Sharetribe and traffic is modest.
Can ZimaOS run legacy Sharetribe Go?
It can be approached as a custom Linux/container workload, but it is a legacy multi-service stack and needs more operational care than the current Web Template.
When should I choose ZimaCube 2 Pro?
Use the stronger CPU tier for a legacy full stack, heavier SSR traffic, or broader server consolidation—not simply because the app name is Sharetribe.
