BitBucket Server Hardware Requirements: RAM, CPU, Storage & Git Operations
Plan legacy BitBucket Server hardware for RAM, CPU, Git operations, repository storage, database, and a safe migration-aware deployment.
BitBucket Server hardware requirements at a glance
Size BitBucket Server from verified upstream requirements first, then add headroom for the actual workload and persistent data.
- RAM
- Historical official baseline: 3 GB+ available memory
- CPU
- Historical production baseline: 2+ cores
- Storage
- Repositories, shared/home data, search/indexes, DB, logs, backups
- Lifecycle
- Server support ended February 15, 2024
- Architecture
- x86-64 in historical Server supported-platform docs
- Best Zima action
- Migration/test-only legacy host; prefer Bitbucket Data Center or Cloud for supported deployments
From official requirements to the right setup
Start with current upstream facts for BitBucket Server, then size the workload rather than copying generic container or catalog labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Repository count
- Repository size
- Git LFS
- Active users
- Clone/fetch/push concurrency
- Database
- Backup retention
- Migration plan
Official minimum requirements
Historical Bitbucket Server documentation published numerical hardware guidance, but the Server product itself is no longer supported.
Use the 2+ core / 3 GB+ memory figures only as historical Server baseline references. For a new supported deployment, Atlassian recommends Cloud or Data Center instead of Bitbucket Server.
| Requirement | Official minimum | What this supports |
|---|---|---|
| 2+ cores | From Bitbucket Server supported-platform documentation. | |
| 3 GB+ available | 1 GB for Bitbucket plus 2 GB for Git operations. | |
| x86-64 | Server-era supported platform. | |
| Server support ended February 15, 2024 | No ongoing Server support or bug fixes. | |
| Bitbucket Server 8.14 | 8.15+ is Data Center only. | |
| Repositories, LFS, indexes, database and backups | No single Server disk minimum captures repository growth. | |
| Not required | Git hosting does not require GPU. |
When to upgrade your hardware
Security/support risk
Git concurrency
Repository growth
Plan hardware growth with confidence
SSD Git storage
Use SSD for active repositories, indexes and database.
SSD/NVMeMore RAM
Useful for larger Git concurrency during a temporary legacy/migration host.
ZimaBoard 2 1664Repository capacity
Use larger storage for repositories, LFS and migration snapshots.
ZimaCube 2 StandardSupported-platform migration
Spend scale effort on Bitbucket Data Center/Cloud rather than an EOL Server instance.
Supported Bitbucket targetCan it run on ZimaOS?
Custom install BitBucket Server in ZimaOS is legacy/unsupported
No specific official ZimaOS one-click page was verified, and Atlassian Server support ended in 2024. Use this only for migration/testing, not as a recommended new production topology.
Custom install BitBucket Server in the ZimaOS app ↗Prefer Bitbucket Data Center or Cloud
Atlassian explicitly recommends migration to remain secure and supported.
Open Atlassian Server end-of-support guidance ↗Use historical Server sizing only as legacy reference
The old 2+ core / 3 GB+ figures describe Server-era support and should not be presented as current Data Center sizing.
Open historical Bitbucket Server platform guidance ↗Zima hardware for BitBucket Server
Bitbucket Server should be treated as a migration/legacy workload, not a new supported self-hosted product.
Choose by workload
Use enough RAM/SSD for repository and Git operations while prioritizing migration.
Move to a supported Bitbucket Data Center or Cloud design instead of scaling Server.
The hardware mapping below is useful for temporary legacy operation or migration capacity planning and does not endorse continued unsupported production use.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaBoard 2 1664 | Memory-heavier web, database, CI controller, and collaboration workloads | Moderate multi-container workloads |
|
CPU is still a 4-core N150; more RAM does not raise build or browser-execution throughput | Get Now |
| ZimaCube 2 Standard | Storage-heavy mail, repositories, attachments, and media | Large persistent datasets where drive bays matter most |
|
8 GB RAM can be less suitable than ZimaBoard 2 1664 for memory-heavy services | 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
Is Bitbucket Server still supported?
No. Atlassian Server support ended on February 15, 2024.
What was the historical Bitbucket Server memory baseline?
Historical supported-platform documentation listed at least 3 GB available memory.
What was the historical production CPU baseline?
Historical Server guidance listed 2 or more CPU cores for production.
Which release was the last Bitbucket Server feature release?
Bitbucket Server 8.14 was the last feature release supporting Server licenses.
What should a current deployment use?
Atlassian recommends migrating to Bitbucket Cloud or Data Center.
Can ZimaBoard 2 1664 run a temporary legacy instance?
It can be a practical temporary migration/test host for modest workloads, but that does not make the unsupported Server product recommended for new production.
Does Bitbucket Server need a GPU?
No.
What drives storage growth?
Repositories, Git LFS, indexes, database data, logs and backups.
