Measure the authentik server, database and reverse proxy during peak logins; external identity-provider latency can also affect the result.
Multiple apps redirecting users at the same time.Wymagania sprzętowe authentik: pamięć RAM, procesor, pamięć masowa, PostgreSQL i obciążenie SSO
Zaplanuj sprzęt do authentik, uwzględniając oficjalne wymagania dotyczące procesora i pamięci RAM, miejsce na PostgreSQL, ruch SSO i dobór outpostów, a także praktyczne wskazówki dotyczące wdrażania na ZimaOS.
APP
authentik hardware requirements at a glance
The official authentik Docker Compose guide requires a host with at least 2 CPU cores and 2 GB RAM for test and small production setups. Whole-host planning must also cover PostgreSQL, the worker, authentication bursts, outposts, backups and other ZimaOS services.
- RAM
- Official Compose host baseline: at least 2 GB RAM. Add headroom for server/worker processes, PostgreSQL, outposts and unrelated containers; this is not a user-capacity guarantee.
- CPU
- Official Compose host baseline: at least 2 CPU cores. Login bursts, password verification, policies and synchronization jobs change practical demand.
- Storage
- No numerical official minimum published. Store PostgreSQL, uploads/configuration, certificates and recovery material durably; event retention changes database growth.
- Database
- PostgreSQL is required; current configuration documentation supports PostgreSQL 14–18. Use the version and data layout from your selected stable-release deployment.
- Outposts / network
- Plan optional proxy/LDAP outposts separately. The standard Compose web ports are 9000 and 9443; reverse-proxy ports 80/443 must have a clear owner.
- Best Zima starting point
- ZimaBoard 2 832 with SSD-backed PostgreSQL is a practical small SSO host. Choose 1664 for more shared services; scale for measured authentication load rather than registered user count alone.
From official requirements to the right setup
Plan the complete authentik workload before selecting a server.
-
Official requirements
Start with the official 2-core/2-GB Compose host baseline and the selected stable release. Use Docker Compose v2 or the documented Podman route and keep server/worker versions aligned.
-
Confirm your needs
Estimate simultaneous logins, password/MFA work, directory synchronization frequency and active outposts. A thousand mostly idle accounts is different from a synchronized login surge.
-
Leave room to grow
Persist PostgreSQL and all paths from the release-matched Compose file. Protect the secret key and database backup together; size event retention and uploaded media independently.
-
Run it on ZimaOS
In ZimaOS Install Custom App, reproduce the official multi-service topology, map unused ports for 9000/9443, and configure the reverse proxy and reachable hostname before relying on SSO for other apps.
Check every playback client
- Peak simultaneous logins
- Authentication and MFA flows
- Directory synchronization schedule
- Proxy/LDAP outpost count
- PostgreSQL version and volume layout
- Event retention and uploaded files
- HTTP 9000 / HTTPS 9443 port mapping
- Database backup and secret-key recovery
Official minimum requirements
Checked on October 23, 2026 against official documentation and the project repository. Latest stable release observed: 2026.8.5. Numerical requirements below retain their original scope.
The 2 GB / 2-core figures are official host requirements for the documented deployment scope. They do not establish production throughput, high availability or sufficient capacity for every co-hosted application. Shared memory settings in Compose are not total RAM requirements.
| Requirement | Official minimum | What this supports |
|---|---|---|
| Host RAM | At least 2 GB | Official Docker Compose requirement for test and small-scale production. |
| Host CPU | At least 2 CPU cores | This is a starting baseline, not a login-throughput or account-count guarantee. |
| Host disk | No numerical official minimum published. | Database retention, files and backup policy determine capacity. |
| Deployment runtime | Docker Compose v2 or Podman | Use the official guide and stable-release configuration. |
| Database | PostgreSQL 14–18 supported in current docs | Use release-compatible settings and perform a proper migration for database major upgrades. |
| Official container | ghcr.io/goauthentik/server | The server and worker use the same release; select the linux/amd64 image on Zima hardware. |
| Web ports | 9000 HTTP / 9443 HTTPS in the Compose template | Map to unused host ports and plan reverse proxy / TLS configuration. |
When to upgrade your hardware
Use observed authentik workload pressure to decide when an upgrade is warranted.
Login latency rises during authentication bursts
Worker jobs or PostgreSQL cause memory pressure
Events and database backups fill the disk
Check worker backlog, database connections, resident memory and swap before increasing processes or outposts.
Directory sync, complex flows and consolidated hosts.Apply an appropriate retention policy and monitor database plus backup growth, rather than sizing only the container image.
Long-running identity systems with audit history.Plan hardware growth with confidence
Address storage, memory, compute and deployment limits separately.
Use SSD-backed PostgreSQL
Low database latency helps authentication and background work; preserve durable backups before changing storage.
SATA/PCIe SSD with ZimaBoard 2.Choose more host RAM
Move to 16 GB when the identity stack and protected services are competing for memory.
ZimaBoard 2 1664; the same four-core N150 CPU remains.Plan event and backup retention
Increase storage only after measuring retained events, database files and independent backup copies.
External SSD or a storage-oriented ZimaCube 2 deployment.Scale measured compute or isolate identity
Use more CPU for persistent authentication pressure; separate critical identity services from heavy OCR/CI jobs where appropriate.
ZimaCube 2 Pro or a dedicated identity host.Can it run on ZimaOS?
No specific public official one-click ZimaOS app page was verified. Third-party store availability does not establish official support; use the official Compose deployment as a Custom Install starting point.
Custom install authentik in ZimaOS
Reproduce the PostgreSQL, server and worker services using the same stable authentik release. Preserve the secret key and persistent files; map 9000/9443 to available host ports.
Custom install authentik in the ZimaOS app ↗Use the official authentik deployment instructions
Keep the selected stable release, persistent paths and companion services aligned with upstream documentation.
Review authentik official installation ↗Verify PostgreSQL and process settings
Review supported PostgreSQL versions and configuration before scaling workers or changing database images.
Review authentik deployment details ↗Which Zima hardware fits authentik?
Start with the lowest reasonable host for the actual workload. Product specifications were checked against the current product pages.
Which workload best matches your authentik deployment?
Home lab or small-team SSO
Keep database storage fast and leave memory for the server and worker.
- Workload optionZimaBoard 2 832
- Workload optionZimaBoard 2 1664
SSO plus larger shared services
Use Pro when observed compute and memory contention warrant consolidation on a larger host.
- Workload optionZimaCube 2 Pro
These are practical workload recommendations, not official app requirements, compatibility certification, measured capacity limits or performance guarantees. Include all co-hosted services and independent backups.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 832 | Small self-hosted identity stack | authentik, worker and SSD-backed PostgreSQL with modest login traffic. |
|
An 8 GB host exceeds the official RAM baseline, but available RAM after other apps and operational availability still matter. | Get Now |
| ZimaBoard 2 1664 | SSO with other modest services | More headroom for PostgreSQL, outposts and companion applications. |
|
RAM increases while CPU stays N150; outposts and login concurrency require measurement. | Get Now |
| ZimaCube 2 Pro | Busier consolidated services | Identity plus database and wider server workloads. |
|
A single physical host is not a high-availability identity architecture. | 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
Answers to authentik RAM, CPU, storage, Docker, database and ZimaOS sizing questions.
What is the official authentik RAM minimum?
The Docker Compose guide specifies a host with at least 2 GB RAM for test and small production setups. Include the whole stack and unrelated ZimaOS services when planning a shared host.
How many CPU cores does authentik require?
The same official guide specifies at least 2 CPU cores. Authentication bursts, password hashing and policy execution determine how much capacity you need beyond that baseline.
Does authentik require PostgreSQL?
Yes. Current configuration documentation supports PostgreSQL 14–18. Keep the actual database version compatible with your chosen authentik release and use a supported major-version migration procedure.
How much storage does authentik need?
No numerical official minimum published. Plan database/events, uploaded assets, certificates, configuration and recoverable backup copies. Event retention is a sizing decision.
Does authentik need a GPU?
No dedicated GPU is needed for the normal identity-provider, SSO, policy and outpost workload. The selected container architecture must match the host; Zima hardware uses amd64.
Can ZimaBoard 2 run authentik?
Its four-core N150 and 8 GB or 16 GB RAM make it a practical small-deployment candidate with suitable database storage. This is a workload recommendation, not a measured maximum-user guarantee.
Do outposts change the hardware requirement?
Yes. Additional proxy/LDAP outposts and protected applications add processes, traffic and operational dependencies. Size their activity separately from the base SSO web interface.
When should I use ZimaCube 2 Pro?
Consider it for measured CPU or memory contention when identity runs alongside busier services. First rule out slow PostgreSQL storage, reverse-proxy problems or remote authentication delays.
What sources informed this authentik hardware guide?
Official project requirements, installation/configuration documentation, repository/release information and the current Zima product pages were checked on October 23, 2026. Practical hardware recommendations are editorial sizing guidance rather than upstream minimums.
