Docker hosting on your own server
Deploy a container image, a Dockerfile or a Compose file to your own server. Zefily routes your domain to the container, keeps the previous release for rollback, and can update a tagged image on a schedule.
- Image, Dockerfile or Compose file as the source
- Blue-green releases with health checks and rollback
- Scheduled updates for the images you tag
On your own server
You keep the server and its cost. Zefily runs the container runtime, routing, certificates and image updates on it. Your containers keep running on the server if you stop using Zefily.
Runs the stacks you already use
- WordPress
- PHP
- Laravel
- Node.js
- Python
- Docker
- Supabase
- Ghost
- Nextcloud
- n8n
- Uptime Kuma
- Grafana
- Gitea
- Metabase
- PocketBase
- Meilisearch
- Vaultwarden
- Adminer
- Joomla
- Moodle
- PrestaShop
- Mautic
- Craft CMS
- Statamic
- Static sites
- CakePHP
- CodeIgniter
- Symfony
- Yii
- Drupal
- WooCommerce
- Express
- NestJS
- Nuxt
- Next.js
- Strapi
- Django
- Flask
- FastAPI
- Hetzner
- DigitalOcean
- Vultr
- Linode
What you get
Image deploys
Point a site at an image and tag. Each deploy pulls it and restarts the container, and the tag tells you what runs.
Dockerfile from Git
Every deploy builds the image from the Dockerfile or Containerfile at the root of your repository.
Without a Dockerfile
Railpack reads the repository and detects Node.js, Python, Go, PHP, Ruby, Java, Rust, Deno or a static site.
Compose files
Start a Compose file on the server. Its other ports are removed, so only the published service is reached, on 127.0.0.1 behind the web server.
Blue-green releases
The new release runs beside the live one and must answer on its own. A release that does not answer never takes traffic, and the live one keeps running.
Shell in a running container
Open a shell inside a running container from the panel. The session is recorded and ends after 30 minutes.
How it works
-
1
Connect a server
Connect a server with the one-line installer, or create one at a cloud provider from the panel.
-
2
Add a container site
Choose an image, a Dockerfile in a Git repository, or a Compose file, and set the domain.
-
3
Deploy
The first deploy starts the container. Later pushes or image changes roll out a new release and roll back if it fails.
Pricing
Plans, limits and prices are on the pricing page. Start with the plan that fits your sites and change it later.
See plans →Questions
Should I use the latest tag?
Avoid it. The latest tag moves on its own schedule and can bring a new major version. Pin a major version such as 16 to take only compatible updates.
Can I pull images from a private registry?
Yes. Add the registry credentials to the site, and the next deploy pulls the image with them.
What happens when a release fails its health check?
The previous release comes back, and the deploy log ends with the last lines the containers printed.
Can I run ready-made stacks like Supabase or Nextcloud?
Yes. Stack sites such as Supabase, Nextcloud and Ghost are offered as app stacks, with their long-running services listed for shell access.
Why would an image update be rolled back?
An update only stays when the new container becomes healthy. If it does not, the previous image comes back and you get a notice.