Skip to main content
OSSAlt

Self-Host Nextcloud: Google Drive Alternative 2026

·OSSAlt Team
nextcloudgoogle-drivefile-synccollaborationself-hostingdocker2026
Share:

TL;DR

Nextcloud (AGPL 3.0, ~27K GitHub stars, PHP) is a complete self-hosted productivity suite — file sync and share, document editing (Collabora/OnlyOffice), calendar and contacts sync (CalDAV/CardDAV), video conferencing (Nextcloud Talk), and 200+ apps. Replace Google Drive ($3/month), Google Docs, Google Calendar, and Google Meet with one self-hosted stack. The All-in-One (AIO) Docker image makes setup significantly easier than the traditional method.

Key Takeaways

  • Nextcloud: AGPL 3.0, ~27K stars, PHP — complete Google Workspace replacement
  • AIO image: Official all-in-one Docker image handles Nextcloud, Postgres, Redis, and reverse proxy
  • Office editing: Collabora Online (LibreOffice) or OnlyOffice for .docx/.xlsx/.pptx in the browser
  • Sync clients: Desktop (Windows/macOS/Linux) and mobile (iOS/Android) — bidirectional sync
  • CalDAV/CardDAV: Sync calendar and contacts with iOS, Android, and Thunderbird
  • Talk: Encrypted video/audio calls without third-party servers (requires TURN server for external access)

Nextcloud vs Google Workspace

FeatureNextcloud (self-hosted)Google Workspace
CostFree (hosting)$6–$18/user/mo
File storageUnlimited (your disk)30GB–5TB/user
Office suiteCollabora / OnlyOfficeGoogle Docs
CalendarYes (CalDAV)Google Calendar
ContactsYes (CardDAV)Google Contacts
Video callsNextcloud TalkGoogle Meet
EmailNo (separate)Gmail
Mobile appsYesYes
Data ownershipYoursGoogle

Part 1: Nextcloud All-in-One (AIO) Setup

The AIO image is the recommended installation method — it manages all components automatically.

# docker-compose.yml
services:
  nextcloud-aio-mastercontainer:
    image: nextcloud/all-in-one:latest
    container_name: nextcloud-aio-mastercontainer
    restart: always
    ports:
      - "8080:8080"    # AIO management interface
    volumes:
      - nextcloud_aio_mastercontainer:/mnt/docker-aio-config
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      APACHE_PORT: "11000"          # Port for reverse proxy to forward to
      APACHE_IP_BINDING: "127.0.0.1"
      NEXTCLOUD_DATADIR: "/mnt/ncdata"    # Where files are stored (use external drive)
      NEXTCLOUD_MAX_TIME: "3600"
      NEXTCLOUD_MEMORY_LIMIT: "512M"

volumes:
  nextcloud_aio_mastercontainer:
    name: nextcloud_aio_mastercontainer

docker compose up -d

Visit https://your-server-ip:8080 → AIO management interface.

Part 2: HTTPS with Caddy

AIO requires a reverse proxy that handles TLS. Configure Caddy:

cloud.yourdomain.com {
    reverse_proxy localhost:11000
}

In the AIO management interface:

  1. Enter your domain: cloud.yourdomain.com
  2. Click Submit → AIO validates DNS
  3. Start containers → AIO pulls and starts all services (10–15 minutes first run)
  4. Get your Nextcloud admin password from the AIO interface

Part 3: Traditional Docker Setup (Alternative)

If you prefer manual control:

services:
  db:
    image: postgres:16-alpine
    restart: unless-stopped
    volumes:
      - db_data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: nextcloud
      POSTGRES_USER: nextcloud
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"

  redis:
    image: redis:alpine
    restart: unless-stopped

  nextcloud:
    image: nextcloud:stable-apache
    restart: unless-stopped
    ports:
      - "8080:80"
    volumes:
      - nextcloud_data:/var/www/html
      - /mnt/ncdata:/var/www/html/data    # External storage for files
    depends_on:
      - db
      - redis
    environment:
      POSTGRES_HOST: db
      POSTGRES_DB: nextcloud
      POSTGRES_USER: nextcloud
      POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}"
      REDIS_HOST: redis
      NEXTCLOUD_ADMIN_USER: admin
      NEXTCLOUD_ADMIN_PASSWORD: "${ADMIN_PASSWORD}"
      NEXTCLOUD_TRUSTED_DOMAINS: "cloud.yourdomain.com"
      OVERWRITEPROTOCOL: "https"
      OVERWRITECLIURL: "https://cloud.yourdomain.com"

volumes:
  db_data:
  nextcloud_data:

Part 4: Desktop Sync Client

  1. Download Nextcloud Desktop (Windows/macOS/Linux)
  2. Add account → Server: https://cloud.yourdomain.com
  3. Log in → Configure sync folders
  4. Files sync automatically in the background

Selective sync: Right-click tray icon → Settings → choose which folders to sync locally.

Part 5: Mobile Apps

Features:

  • Auto-upload photos: Camera roll automatically backed up
  • Offline access: Mark files for offline viewing
  • Talk: Video calls from mobile
  • Files: Browse and edit documents

Part 6: Office Document Editing (Collabora)

Edit .docx, .xlsx, .pptx directly in the browser via Collabora Online:

With AIO

Collabora is included in AIO — enable it in the AIO interface under Optional containers.

Manual Collabora Setup

services:
  collabora:
    image: collabora/code:latest
    container_name: collabora
    restart: unless-stopped
    ports:
      - "9980:9980"
    environment:
      domain: "cloud\\.yourdomain\\.com"    # Escape dots
      username: "admin"
      password: "${COLLABORA_ADMIN_PASSWORD}"
      aliasgroup1: "https://cloud.yourdomain.com:443"
    cap_add:
      - MKNOD

office.yourdomain.com {
    reverse_proxy https://localhost:9980 {
        transport http {
            tls_insecure_skip_verify
        }
    }
}

In Nextcloud → Apps → Install Nextcloud Office → Settings → enter https://office.yourdomain.com.

Part 7: Calendar and Contacts Sync

iOS Setup

Calendar (CalDAV):

  1. Settings → Calendar → Accounts → Add Account → Other → Add CalDAV Account
  2. Server: https://cloud.yourdomain.com/remote.php/dav
  3. Username + password → Save

Contacts (CardDAV):

  1. Settings → Contacts → Accounts → Add Account → Other → Add CardDAV Account
  2. Server: https://cloud.yourdomain.com/remote.php/dav
  3. Username + password → Save

Android (via DAVx5)

  1. Install DAVx5 (open source CalDAV/CardDAV client)
  2. Add account → Login with URL
  3. Base URL: https://cloud.yourdomain.com
  4. Login → Select calendars and address books to sync

Thunderbird

  1. Thunderbird → Calendar → New Calendar → Network
  2. Format: CalDAV
  3. Location: https://cloud.yourdomain.com/remote.php/dav/calendars/username/personal/

Part 8: Nextcloud Talk (Video Calls)

Nextcloud Talk provides end-to-end encrypted video and audio calls:

  1. Apps → Install Nextcloud Talk
  2. For internal calls (LAN): works immediately
  3. For external access: requires a TURN server

TURN Server for External Video Calls

services:
  coturn:
    image: coturn/coturn:latest
    restart: unless-stopped
    network_mode: host
    command: >
      -n --log-file=stdout
      --min-port=49160 --max-port=49200
      --realm=cloud.yourdomain.com
      --static-auth-secret="${TURN_SECRET}"

In Nextcloud → Settings → Talk → TURN server:

  • URL: turn:turn.yourdomain.com:3478
  • Secret: your TURN_SECRET

Part 9: External Storage

Mount S3, SFTP, or other cloud storage as a Nextcloud folder:

  1. Apps → Install External Storage Support
  2. Settings → External Storages → Add Storage
  3. Type: Amazon S3
    • Bucket: my-nextcloud-bucket
    • Region: us-east-1
    • Key + Secret
  4. Folder appears in your Nextcloud Files

Performance Tuning

# /var/www/html/config/config.php additions:

'memcache.local' => '\OC\Memcache\APCu',
'memcache.distributed' => '\OC\Memcache\Redis',
'memcache.locking' => '\OC\Memcache\Redis',
'redis' => [
    'host' => 'redis',
    'port' => 6379,
],
'default_phone_region' => 'US',
'maintenance_window_start' => 1,    # Run maintenance at 1am UTC

Maintenance

# Update (AIO):
# AIO management interface → Update

# Update (manual):
docker compose pull
docker compose up -d

# Run occ commands (Nextcloud CLI):
docker exec --user www-data nextcloud php occ status
docker exec --user www-data nextcloud php occ upgrade
docker exec --user www-data nextcloud php occ files:scan --all

# Backup:
docker exec --user www-data nextcloud php occ maintenance:mode --on
tar -czf nextcloud-backup-$(date +%Y%m%d).tar.gz /mnt/ncdata
# Backup database:
docker exec db pg_dump -U nextcloud nextcloud > nextcloud-db-$(date +%Y%m%d).sql
docker exec --user www-data nextcloud php occ maintenance:mode --off

Why Self-Host Nextcloud?

The case for self-hosting Nextcloud comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Nextcloud means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Nextcloud, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Nextcloud headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Nextcloud data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Nextcloud without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Nextcloud's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Nextcloud backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Nextcloud's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Nextcloud's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Nextcloud's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Nextcloud's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f nextcloud

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Nextcloud's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

  1. Confirm the container is running: docker compose ps
  2. Test locally on the server: curl -I http://localhost:PORT
  3. If local access works but external doesn't, check your firewall: ufw status
  4. If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats nextcloud. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Nextcloud Updated

Nextcloud follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Nextcloud is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source collaboration and file sync tools at OSSAlt.com/alternatives/google-drive.

See open source alternatives to Nextcloud on OSSAlt.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)

Step-by-step: infrastructure setup, data migration, backups, and security for 15+ common SaaS replacements. Used by 300+ developers.

Join 300+ self-hosters. Unsubscribe in one click.