The current docs position Compose for 0–50 users. More users and heavier database activity can justify stronger hardware or a more scalable deployment model.
Growing teams and shared operational databases.متطلبات أجهزة Teable: ذاكرة الوصول العشوائي، ووحدة المعالجة المركزية، والتخزين، والاستضافة الذاتية
خطط للاستضافة الذاتية لـ Teable مع مراعاة متطلبات ذاكرة RAM ووحدة المعالجة المركزية ومساحة القرص وPostgreSQL وRedis وأحمال تشغيل الذكاء الاصطناعي، مع إرشادات النشر الرسمية عبر متجر تطبيقات ZimaOS.
Teable requirements at a glance
Teable's current Docker Compose documentation gives a concrete small-team baseline of 4 GB RAM, at least 2 CPU cores and 40 GB available disk. The newer full-featured self-hosted platform can add PostgreSQL, Redis plus an AI/App Builder runtime plane with sandboxes, object storage and app deployment services.
- RAM
- Official basic Docker Compose minimum: 4 GB RAM.
- CPU
- Official basic Docker Compose minimum: at least 2 CPU cores.
- Storage
- Official basic Docker Compose minimum: 40 GB available disk.
- Recommended scale
- Current basic Docker Compose documentation recommends this path for small teams/evaluation, around 0–50 users.
- Full-featured AI stack
- AI chat/App Builder adds a separate runtime plane with sandbox engine, Infra Service, Git registry, object storage and preview gateway.
- Best Zima starting point
- ZimaBoard 2 832 exceeds the basic 4 GB/2-core requirement; use 16 GB or ZimaCube 2 Pro if running the newer full-featured AI/App Builder stack or many companion services.
From official requirements to the right setup
Choose basic Teable versus the full-featured AI/App Builder deployment first, because the second adds several infrastructure services beyond the core app, PostgreSQL and Redis.
-
Official requirements
For basic Docker Compose, start with Teable's published baseline: 4 GB RAM, 2 CPU cores and 40 GB available disk.
-
Confirm your needs
Estimate users, records, attachments and database activity. The current basic Docker Compose path is positioned for small teams/evaluation rather than large production scaling.
-
Leave room to grow
If enabling AI/App Builder features, account for the additional sandbox engine, Infra Service, Git registry, MinIO/object storage and preview gateway.
-
Run it on ZimaOS
Use the ZimaOS App Store for the packaged Teable app, persist PostgreSQL/Redis/application data, and only add the full-featured runtime plane when its extra services are actually needed.
Check every playback client
- Basic Teable or full-featured AI/App Builder
- Expected user count
- Database/record growth
- Attachment/object-storage growth
- PostgreSQL persistence
- Redis persistence
- AI sandbox/app deployment needs
- Other ZimaOS services
Official minimum requirements
Teable publishes a concrete Docker Compose baseline for the normal small-team deployment.
The 4 GB RAM, 2-core and 40 GB disk figures are valid official basic-deployment minimums. Do not apply them unchanged to the newer full-featured AI runtime, which adds multiple infrastructure services.
| Requirement | Official minimum | What this supports |
|---|---|---|
| RAM | Minimum 4 GB | Current basic Docker Compose server requirement. |
| CPU | At least 2 cores | Current basic Docker Compose server requirement. |
| Disk | Minimum 40 GB available | Current basic Docker Compose server requirement. |
| Recommended basic scale | 0–50 users | Current docs position Docker Compose for small teams and evaluation. |
| Core services | Teable app + PostgreSQL + Redis | The basic deployment uses a multi-service application stack. |
| Full-featured runtime | Additional AI/App Builder infrastructure | Adds sandbox runtime, Infra Service, Git registry, object storage and preview gateway. |
When to upgrade your hardware
Teable should scale when database workload, stored attachments or the optional AI/App Builder runtime moves beyond the basic small-team profile.
The team outgrows the basic Docker Compose profile
Records, attachments and PostgreSQL activity increase
You enable AI and App Builder self-hosting
Teable is a database-centric application, so PostgreSQL memory and storage I/O can become the practical bottleneck.
Large bases, attachment-heavy workflows and automation.The full-featured runtime adds sandboxes, object storage, Git registry and app deployment services, materially increasing whole-host resource demand.
Teams self-hosting Teable's newer AI/runtime features.Plan hardware growth with confidence
Scale Teable by keeping PostgreSQL and application data on fast persistent storage, then add memory/CPU as the database and optional runtime grow.
Use SSD-backed PostgreSQL storage
Database-heavy table operations benefit from predictable low-latency storage.
Use SATA/NVMe on ZimaBoard 2 or SSD tiers on ZimaCube 2.Move to 16 GB for heavier multi-service use
Extra RAM helps PostgreSQL, Redis, Teable and other ZimaOS services coexist with more headroom.
ZimaBoard 2 1664 is a compact 16 GB step-up.Use ZimaCube when attachments and object storage grow
The six-bay platform is useful when Teable becomes part of a broader data-management server.
ZimaCube 2 Standard or Pro.Treat the AI runtime as a separate capacity tier
Sandboxes, app deployments and object storage can consume resources independently from the core Teable app.
Use ZimaCube 2 Pro or dedicated infrastructure when the full-featured runtime is active.Can it run on ZimaOS?
Teable is currently available in the official ZimaOS App Store, so the normal basic deployment can use the one-click installation path rather than a custom Docker import.
Install Teable from the ZimaOS App Store
Use the official one-click Teable listing for the packaged deployment, then configure persistent application/database storage and your public-access settings as needed.
Open Teable in the ZimaOS App Store ↗Use Teable's Docker guidance for capacity planning
The current Docker Compose documentation specifies the 4 GB RAM, 2-core and 40 GB disk baseline for small-team/evaluation deployments.
Review Teable Docker deployment ↗Treat AI/App Builder self-hosting as an advanced extension
The newer full-featured deployment adds an AI runtime plane and several additional services beyond the core Teable package.
Review Teable self-host deployment ↗Choose Zima hardware for Teable
Teable's basic hardware floor is clear enough to map directly to Zima hardware; the full-featured AI runtime belongs in a higher capacity tier.
Are you running basic Teable for a small team, or the newer full-featured AI/App Builder stack?
Basic Teable / small team
ZimaBoard 2 832 exceeds the official 2-core/4-GB baseline; add SSD-backed persistent data storage.
- Best starting pointZimaBoard 2 832
- More database/app headroomZimaBoard 2 1664
Full-featured AI/App Builder or broader consolidation
Use stronger CPU, 16 GB RAM and expandable storage because the runtime plane adds several services beyond Teable itself.
- Higher-headroom platformZimaCube 2 Pro
These recommendations do not guarantee a user count or record throughput. Database size, automation, attachments, AI sandboxes and other ZimaOS services can change resource use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Basic Teable for a small team. | Teable app, PostgreSQL, Redis, normal table workflows and light attachments. |
|
The official minimum calls for 40 GB disk, so add persistent SSD storage rather than relying only on the 32 GB eMMC. | Get Now |
| ZimaBoard 2 1664 | Basic Teable with larger PostgreSQL cache, more users or more co-hosted apps. | Teable, PostgreSQL, Redis and broader self-hosted productivity services. |
|
16 GB gives headroom but does not automatically make the basic single-machine deployment appropriate for large-scale production. | Get Now |
| ZimaCube 2 Pro | Full-featured Teable AI/App Builder or heavier data-service consolidation. | Core Teable plus AI runtime plane, sandboxes, object storage, Git registry and other services. |
|
Resource demand of the full-featured runtime is release/workload dependent; monitor and separate services when the single host becomes constrained. | 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
These answers cover Teable RAM, CPU, disk, PostgreSQL, Docker, AI runtime and ZimaOS one-click deployment.
How much RAM does Teable need?
The current Teable Docker Compose documentation lists 4 GB RAM as the minimum for the basic self-hosted deployment.
How many CPU cores does Teable need?
The current basic Docker Compose server requirement is at least 2 CPU cores.
How much storage does Teable need?
The current basic Docker Compose guidance lists at least 40 GB available disk.
How many users is Teable Docker Compose designed for?
Current documentation positions the basic Docker Compose path for small teams/evaluation, approximately 0–50 users.
Does Teable require PostgreSQL and Redis?
Yes. The normal self-hosted stack includes the Teable application with PostgreSQL and Redis.
Does Teable need a GPU?
No dedicated GPU is required for normal table/database workflows. AI features can use external model providers, while the self-hosted AI runtime has separate infrastructure needs.
Can ZimaBoard 2 run Teable?
Yes. The 8 GB ZimaBoard 2 exceeds the official basic 4 GB RAM and 2-core baseline; add at least 40 GB of suitable persistent storage.
What changes when I self-host Teable AI/App Builder features?
The full-featured platform adds a sandbox engine, Infra Service, Git registry, object storage and preview/app deployment services, so whole-host requirements increase beyond the basic Teable stack.
What sources informed this Teable hardware guide?
The guide uses current Teable Docker and self-host-deployment documentation, the official ZimaOS Teable page, and current Zima product pages for hardware matching.
