Repository navigation
Nextcloud AIO comparison
Gibran Khan edited this page Nov 18, 2026
·
1 revision
Similar goal, different approach. Both projects simplify setting up Nextcloud and its supporting services. NextcloudOnFreeBSD builds around FreeBSD jails, ZFS and PF; official Nextcloud AIO builds around Docker and includes ongoing update and backup management.
NextcloudOnFreeBSD is an independent project—not official Nextcloud AIO or a FreeBSD port of it. Its default is Nextcloud 35.
| Area | NextcloudOnFreeBSD v1.0.1 | Official Nextcloud AIO |
|---|---|---|
| Platform | FreeBSD 15+ (amd64), using an existing ZFS pool | Linux containers through Docker; also documented on Windows and macOS |
| Setup interface | Terminal wizard or JSON recipe | Start the mastercontainer, then use its web interface |
| Nextcloud runtime | Native FreeBSD jail with Apache, PHP-FPM, MariaDB and Redis | Coordinated Docker containers, including PostgreSQL and Redis |
| Storage | Creates per-instance ZFS datasets; mounts application data separately from jail roots | Docker volumes and configurable data-directory location |
| Office integration | Native ONLYOFFICE by default; optional Euro-Office or Collabora CODE in a dedicated Linux VM | Optional Nextcloud Office/Collabora or EuroOffice containers |
| Push and Talk | Client Push included; optional dedicated Talk HPB/TURN jail | Client Push included; optional Talk HPB/TURN and recording containers |
| HTTPS | Let’s Encrypt, supplied certificates or an external HTTPS proxy | Built-in automatic HTTPS or an external reverse proxy |
| Networking | Creates private bridges and manages its PF anchor; checks coexistence requirements | Creates a Docker network and publishes required ports |
| Multiple instances | Built into the installer, with separate storage and private networks | Documented using separate VMs or separate rootless Docker users, with distinct ports |
| Updates | Operator-managed; the upgrade assistant is unavailable for new deployments | Integrated updates, with optional automation |
| Backup and restore | Operator-managed; no integrated backup/restore for new deployments. Retained datasets are not backups | Integrated BorgBackup, scheduling and restoration through the AIO interface |
| Existing installations | Creates new deployments; does not adopt or migrate existing installations | Provides documented migration procedures, including manual steps |
This comparison covers new deployments. It is based on documentation reviewed on November 18, 2026—not a hands-on AIO test, an exhaustive feature list or a claim of feature parity. AIO features can change; consult its current documentation.
- Overview, included services, updates and backups
- HTTPS and reverse-proxy options
- Multiple instances
- Migration procedures
For this project's implementation, see Architecture. To get started, see the Installation guide.