Servoke

Servoke vs Coolify

Coolify is a self-hosted platform for deploying apps and containers. Servoke is a hosting panel: accounts for customers, websites, mailboxes, DNS zones and databases, with a reseller model and per-account limits. Many teams will want both, on different servers.

Push to deploy from Git
Databases and hundreds of one click services
Open source and free to self-host

Servoke and Coolify, area by area

Pricing. Servoke: $4.99 a server a month. $3.99 each from 100 servers. A quote from 500 servers. Coolify: Free to self-host. Coolify Cloud is $5 a month for 2 servers, then $3 a month for each extra server.
Accounts per licence. Servoke: Unlimited on every server. No fee per account, ever. Coolify: Projects, apps and teams, not hosting accounts.
Licence. Servoke: Commercial licence per server, checked on the server from a signed document. Coolify: Open source under the Apache 2.0 license.
Websites, PHP and certificates. Servoke: nginx with PHP-FPM, Apache and OpenLiteSpeed engines, certificates issued and renewed for you. Coolify: Deploys sites and apps from Git or container images, with automatic Let's Encrypt certificates.
Email hosting. Servoke: Postfix, Dovecot and Rspamd, with SPF, DKIM and DMARC written for you, and webmail. Coolify: A mail server such as Stalwart can run as a one click service, managed in its own interface.
DNS hosting. Servoke: PowerDNS zones created with each domain. Coolify: No DNS hosting listed.
Databases. Servoke: MariaDB and PostgreSQL. Coolify: One click PostgreSQL, MySQL, MariaDB, MongoDB, Redis and more.
Resellers. Servoke: Reseller accounts with their own packages and limits. Coolify: Not included. Teams share projects with roles.
Per-account resource limits. Servoke: CPU, memory and IO limits per account on cgroup v2, with no add-on. Coolify: CPU and memory limits for each app and database container.
Firewall and brute force guard. Servoke: Firewall, brute force guard, web application firewall and a security advisor. Every change in the audit log. Coolify: The firewall is set up by you or your provider. A brute force guard is not listed.
AI that reads the server. Servoke: Michael reads the real server and proposes each step for you to approve. Paid with JagAI credits. Coolify: An MCP server lets AI assistants list, deploy and read logs. No built in assistant.
API, CLI and MCP. Servoke: Every console action is an /api/v1 call in OpenAPI. The CLI mirrors it, and an MCP server is built in. Coolify: A REST API, an official CLI and an MCP server.
Updates. Servoke: Checks hourly, verifies the signature, saves its state and puts the last build back if a new one is unhealthy. Coolify: Updates itself automatically on a schedule you set, daily by default.
Moving from cPanel. Servoke: Installs beside cPanel and imports its accounts. Take over stops cPanel and WHM in one click while every site, mailbox and zone keeps running, and Bring cPanel back is one click. Coolify: No cPanel importer listed.
Core runtime. Servoke: One Rust daemon with the consoles built in. Privileged changes are typed operations, never shell strings. Coolify: A PHP (Laravel) app that runs your workloads in Docker.

When Coolify is the better fit

If you deploy containers and apps rather than host websites and mail for customers, Coolify is built for that job.

From Coolify to Servoke

Keep Coolify for your apps: App containers can stay where they are.
Install Servoke for hosting: Customer websites, mail and DNS get a server of their own.
Connect them with DNS: Point each name at the server that serves it.

Related comparisons

Compare Toolbox Terms of Service EULA Privacy Policy