Apps that turn a Mac into a server

macOS Server is not the answer any more

Apple's own Server app is the thing most people are looking for, and it is gone. In macOS Server 5.7.1 Apple removed DNS, VPN, mail, Calendar, Contacts, Messages and the Wiki outright, and took the interface away from Websites, DHCP, the firewall and NetBoot. Xsan went in 5.12. Apple discontinued macOS Server altogether on 21 April 2022, and what is left for existing customers is Profile Manager and Open Directory.

Worth knowing, because it saves a search: Apple's own migration table names the replacements it expects you to use, and they are all third-party or built-in Unix software: Apache or Nginx for websites, WireGuard or OpenVPN, Postfix and Dovecot for mail. The Apache that served pages under Server is in fact still inside macOS. It just has no interface, no certificate handling and no supervision, which is most of the reason people go looking for an app in the first place.

So there is no first-party app that makes a Mac serve a website. What people mean by "a Mac server app" in 2026 is one of three quite different tools, and picking the wrong one wastes an afternoon.

Apple: about macOS Server 5.7.1 and later ↗

The three kinds, and what each one is actually for

They are not competitors. Each solves a different part of the problem, and a working setup usually needs one from more than one row.

• Container toolsDocker Desktop, OrbStack, Podman. You get a way to run packaged Linux software. What you do not get is a machine: on a Mac these all start a hidden Linux VM and run containers inside it, so you are paying for virtualisation either way and looking at it through a container-shaped window.
• Virtual machine toolsUTM, Lima, Tart, Parallels. These give you an actual Linux system with its own kernel, filesystem and services, which you can SSH into and treat like any other host. This is the shape that behaves like a server. The cost is memory: what you assign to Linux, macOS no longer has.
• Tunnels and remote accessCloudflare Tunnel, ngrok, Tailscale. These make something on your Mac reachable from elsewhere. They solve the address problem and nothing else. There is still nothing running behind the address until you have used one of the rows above.

The part none of them do

Install any of the above and you have a Linux environment, or a public address, or both. What is still missing is everything that makes it a server rather than an experiment.

A certificate that renews before it expires. A Linux server that comes back by itself when the Mac reboots or wakes, rather than the next time you remember to look. Something that tells you the machine stopped answering, and can tell the difference between a Mac you switched off deliberately and one that fell over at 3am. A record of what is published, so that in six months you can still answer "what is this port".

Assembling those is not hard, exactly. It is just a permanent, low-level job that arrives in pieces over the following year, usually on the day something breaks.

What to check before you install anything

Two of these decide the outcome before you start, and both are easier to check now than to discover later.

• Apple silicon or IntelOn an M-series Mac, Linux runs on Apple's own virtualisation framework and the overhead is small. On an Intel Mac the tooling is older, the options are narrower and the machine draws far more power to do the same work.
• Memory, not coresA VM reserves what you give it. On a 8 GiB Mac there is very little left over after a useful Linux allocation; 16 GiB is where this stops being a compromise.
• Your internet connectionIf your ISP puts you behind CGNAT, as most mobile and many fibre connections do, you have no public address to forward a port to, and no amount of router configuration will give you one. A tunnel or a relay is the only way out, so find out before you plan around port forwarding.
• SleepA laptop's default behaviour is to stop being a server the moment you close the lid. This is a settings problem rather than a hardware one, but it is the single most common reason a home server appears to be broken.

If you would rather assemble it yourself

None of this is exotic, and plenty of people run exactly this. It is worth seeing the whole list before you start, because the parts arrive one at a time and usually on the day something breaks.

1. Lima or UTM to run the Linux VM.
2. Caddy inside it, to serve the site and get certificates automatically.
3. Cloudflare Tunnel for a public address that survives CGNAT.
4. A launchd daemon so the VM starts when the Mac boots, and comes back after a reboot nobody was present for.
5. An external uptime check, so you hear about an outage from something other than a customer.