A local LLM/embedding model can become the dominant RAM/CPU/VRAM workload.
Privacy-focused AI note search.Blinko-Hardwareanforderungen: RAM, CPU, Speicher & Bereitstellung
Planen Sie die Blinko-Hardware für RAM, CPU, PostgreSQL, Anhänge und optionale KI-Funktionen – mit direkter Anleitung zur Bereitstellung über den ZimaOS App Store.
Blinko requirements at a glance
Blinko is a self-hosted note app backed by PostgreSQL. Upstream publishes no numerical whole-host CPU/RAM minimum; the current ZimaOS package lists 768 MB minimum memory, while optional local AI can require far more.
- Upstream RAM minimum
- No numerical whole-host minimum published by Blinko upstream.
- ZimaOS package memory
- Current official ZimaOS App Store listing: 768 MB minimum memory.
- Database
- Current upstream Compose files use PostgreSQL 14.
- Port
- Blinko runs on port 1111 in current upstream and ZimaOS documentation.
- AI features
- Optional. Remote AI providers add little local compute; a local Ollama model must be sized separately for model RAM/VRAM.
- Best Zima starting point
- ZimaBoard 2 832 is ample for notes plus PostgreSQL when AI inference is remote or on another server.
From official requirements to the right setup
Size Blinko from the real workload and deployment topology rather than generic server assumptions.
-
Official requirements
Install Blinko from the official ZimaOS App Store and keep its app-data location on durable storage.
-
Confirm your needs
Treat the ZimaOS 768 MB figure as package metadata rather than an upstream universal server requirement.
-
Leave room to grow
Back up PostgreSQL and Blinko app data; note/attachment growth matters more than raw application compute.
-
Run it on ZimaOS
If enabling local Ollama, size that model separately because local AI can dominate RAM/VRAM far beyond Blinko itself.
Check every playback client
- 768 MB package memory
- PostgreSQL 14
- Port 1111
- Note/attachment growth
- AI provider choice
- Local Ollama model
- App-data backup
- Other ZimaOS apps
Official minimum requirements
Blinko upstream defines its PostgreSQL/container topology but does not publish a numerical whole-host minimum; ZimaOS provides package-level memory metadata.
Use 768 MB only as the current ZimaOS package minimum-memory value, not as an upstream Blinko hardware guarantee. Local AI requirements are separate.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Upstream host RAM minimum | No numerical minimum published | Current upstream Compose does not define a whole-host floor. |
| ZimaOS package minimum memory | 768 MB | Current public App Store metadata. |
| Database | PostgreSQL 14 | Current upstream Compose example. |
| App port | 1111 | Current upstream/ZimaOS deployment. |
| AI | Optional | Remote or local providers are configurable. |
| Local model resources | Model-dependent | Ollama/model RAM/VRAM must be sized separately. |
When to upgrade your hardware
Scale Blinko when these workload signals appear.
Local AI is enabled
Attachments and notes grow
More users or other apps share the host
PostgreSQL and app-data backups become the long-term storage driver.
Heavy personal knowledge bases.Whole-host database/cache pressure can exceed Blinko's own needs.
Multi-app ZimaOS servers.Plan hardware growth with confidence
Scale Blinko only where the workload justifies additional resources.
Keep standard Blinko on ZimaBoard 2 832
8 GB is far above the current package memory value.
ZimaBoard 2 832.Use SSD-backed PostgreSQL/app storage
Durable low-latency storage improves database reliability and backups.
Use SATA/NVMe with ZimaBoard 2.Use 16 GB for many co-hosted apps
Extra RAM benefits the broader server, not a remote-AI Blinko instance alone.
ZimaBoard 2 1664.Size local AI separately
Choose AI hardware from the actual Ollama model rather than from Blinko's app requirements.
Use a separate local-AI sizing guide when running models locally.Can it run on ZimaOS?
Blinko deployment on ZimaOS should follow the verified route below.
Install Blinko from the ZimaOS App Store
Install the current Blinko package directly; ZimaOS stores note data in the app-data location and exposes Blinko on port 1111.
Install Blinko from the ZimaOS App Store ↗Review Blinko upstream deployment
Use upstream documentation to understand ports, persistence and feature-specific requirements.
Review Blinko installation docs ↗Keep persistent data outside disposable containers
Map configuration, database or uploaded-file paths to durable ZimaOS storage where the app uses persistent state.
Review ZimaOS download and app platform ↗Choose Zima hardware for Blinko
Blinko itself is lightweight; PostgreSQL, attachments and optional local AI determine the meaningful upgrade path.
Which Blinko workload are you running?
Remote AI or no AI
Use ZimaBoard 2 832 with durable app/database storage.
- Best starting pointZimaBoard 2 832
Many apps or larger knowledge base
Add RAM/storage for the whole host; size local models separately if used.
- More host headroomZimaBoard 2 1664
- Storage-first platformZimaCube 2 Standard
The 768 MB value is ZimaOS package metadata. It is not an upstream whole-host benchmark, and local AI can require much more.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Normal Blinko note-taking with remote AI or no AI. | Blinko, PostgreSQL, attachments and backups. |
|
Do not expect it to run large local LLMs just because Blinko fits easily. | Get Now |
| ZimaBoard 2 1664 | Larger multi-app knowledge server. | Blinko plus more database/cache and co-hosted services. |
|
Local AI still depends on the exact model. | Get Now |
| ZimaCube 2 Standard | Attachment-heavy note server and broader NAS. | Blinko plus larger backup/file retention. |
|
Choose it for storage, not Blinko compute. | 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 Blinko RAM, CPU, storage and ZimaOS deployment.
How much RAM does Blinko need?
Blinko upstream does not publish a numerical whole-host minimum; the current ZimaOS package lists 768 MB minimum memory.
Which database does Blinko use?
Current upstream Compose examples use PostgreSQL 14.
Which port does Blinko use?
Port 1111 in current upstream and ZimaOS deployment examples.
Does Blinko require AI?
No. AI features are optional.
Does local AI change the hardware requirement?
Yes. A local Ollama model can require far more RAM/VRAM than Blinko itself and must be sized separately.
Does Blinko need a GPU?
Not for normal note-taking; only optional local AI models may benefit from a GPU.
Can ZimaBoard 2 run Blinko?
Yes. The 8 GB model is ample for Blinko plus PostgreSQL when model inference is remote or separate.
Is Blinko available in the ZimaOS App Store?
Yes. A current public official ZimaOS App Store page is available.
What sources informed this Blinko hardware guide?
Current Blinko ZimaOS listing, upstream Compose files and Zima product pages.
