What apps can I bring? What won't work?

Our bring-your-own app feature lets you paste any Docker image or docker-compose file. Here's what works — and what doesn't.

What we accept

Single containers with a web UI

• Uptime Kuma, Vaultwarden, Immich, Nextcloud, any app with a browser interface
• One public port (HTTP/HTTPS), served through our reverse proxy
• Persistent storage via volumes (we preserve your data on stop/start)

Compose stacks (multiple services together)

• An app plus its database (Ghost + MySQL, Nextcloud + PostgreSQL)
• An app with Redis cache or worker services, all on a private network
• One service is public (your web UI); the rest stay private and unreachable from outside
• Up to 4 GB compressed for all images combined

Environment-based configuration

• Custom environment variables and command overrides
• Generated credentials (we create random admin passwords)
• First-run setup (you create the first account after deploy)
• No authentication (for apps that intentionally have no login)

What we don't accept

Security boundary: no host access

We can't give any app access to the host machine or kernel-level features, because shared hosting means other customers' apps live on the same server.

• VPN servers and clients (WireGuard, OpenVPN, Gluetun, etc.) — need /dev/net/tun and NET_ADMIN capability
• Container managers (Portainer, Docker CLI, etc.) — need access to Docker socket or daemon
• Anything requiring elevated privileges — SYS_ADMIN, NET_RAW, host networking, privileged mode, raw devices

If your image mentions these in its README, we refuse it immediately with a specific reason. If it doesn't document them but tries to use them at boot, the sandbox test catches it, we attempt one AI-powered repair (which can't grant kernel privileges), and then block it.

Technical limits

• Oversized images — over 2 GB compressed
• ARM-only builds — we run linux/amd64 only
• Non-Linux — Windows and macOS images don't work here
• UDP-only apps — if it speaks only UDP with no TCP port, there's nowhere to route it
• Bare database servers with no UI — Postgres, MySQL, Redis by themselves (but pgAdmin, Adminer, and database management UIs are fine)
• CLI tools and base images — only web-facing applications

Access model

• Apps that generate passwords at startup — if it prints a one-time admin password to logs on first boot, we can't reuse that secret on redeploy. Bring apps that let you preset credentials via environment variables instead.
• Apps requiring external services — if it can't boot without a separate PostgreSQL or Redis server already running, that's not something we can set up for you (but apps with embedded databases, or ones that work standalone, are fine)

How we test

1. We read your image metadata and README
2. Our AI reviews it for compatibility
3. We boot it for real on our infrastructure in a sandbox
4. If it fails, an AI repair pass fixes the configuration and tests again
5. Only apps that actually run get a Deploy button

So if you're not sure whether something will work, paste the link — we'll tell you exactly what's wrong before you deploy.

Still not sure?

Ask us directly — we can usually tell you in minutes whether your app is compatible.