FAQ
Does Vhostly replace MAMP or Valet?
It overlaps with both. MAMP ships its own Apache, PHP and MySQL; Vhostly drives the ones Homebrew already installed and bundles no runtime of its own. Valet does something similar through nginx and dnsmasq, from the terminal — Vhostly is the same idea with a window, on Apache.
Does it work on an Intel Mac?
Not today. The app ships an arm64 server binary and reads Homebrew from /opt/homebrew,
which is the Apple silicon prefix. An Intel Mac would need both a second binary and support
for the /usr/local prefix.
Do I have to use Homebrew's Apache?
Yes. Every path the app manages is under /opt/homebrew. The httpd that ships with macOS
lives elsewhere and is not what Vhostly configures. brew install httpd first.
Does it install PHP or Apache for me?
It can. The first-run checks and the Health panel offer to brew install anything
missing, and always show the command before running it. Homebrew itself is the exception —
it comes from a shell script you have to run yourself.
Does Vhostly keep PHP up to date?
No. PHP comes from Homebrew, so you update it with brew upgrade and restart Apache. Keep PHP on
the latest release, because security fixes only reach you that way. Critical PHP notices appear
in the app's News panel and on the news page.
Can I run two PHP versions at the same time?
Not for two Apache-served sites. Apache loads one PHP module, and it applies to every static site on the machine. The way around it is a proxy site: run the odd project under its own PHP and point a proxy vhost at it. See PHP versions.
Do I need to keep the app open?
No. What Vhostly writes is ordinary Apache configuration, and Apache keeps serving after you quit. Open the app when you want to change something. Sites shared on your network keep working too.
The exception is a public link. It runs while the app is open and closes when you quit.
Can I open my sites on my phone?
Yes. Share the site on the Network panel and scan the QR code with a phone on the same Wi-Fi. To open it from anywhere, create a temporary public link instead. See phones and public links.
Why does it want my password on first launch?
To install the one thing that needs root: a small helper that writes Vhostly's block of
/etc/hosts and accepts nothing but .test and .localhost names. Apache runs as you and
needs no password. The details are in
installation and on the
security page, and undoing it is in
what Vhostly writes.
Can I use nginx?
Not today. The generated configuration is Apache's.
Does it handle databases?
It starts and stops them. The Services panel wraps brew services, so MySQL,
PostgreSQL, Redis and the rest can be controlled without a second window. It does not
configure them, create databases or manage their data.
Is anything sent anywhere?
When the app starts, and every few hours while it stays open, it reports its version, the macOS release and a random identifier generated on your machine, to Google Analytics and to vhostly.app. vhostly.app also works out your country and city from your IP address and keeps those, not the address itself. Nothing about your sites, folders or ports is sent. It exists because a download count says nothing about whether the app was ever opened.
Turn it off under Settings → Privacy and those reports stop. The app also fetches its news
feed, vhostly.app/news.json, so it can show releases and critical security notices. That is a
plain download that sends none of the details above, and it is not covered by the Privacy
switch. Activating a Pro license contacts the license server. There is no account and no update
check: the app talks to a server it runs on your
own machine, on a random local port. The only other traffic it causes is Homebrew's when you
ask it to install something, and a Cloudflare tunnel when you ask for a
public link. That tunnel carries visitors' requests to the
site you shared.
A build you compile yourself reports nothing either way — where to report is baked in when the release is built, and only those builds carry it.
This website is a separate thing and uses Google Analytics, so visits to these pages are counted. Each download through the site is also recorded with its country and city, without the IP address.
Where are my sites stored?
In Apache's own config files, not in a database of the app's own — see
what Vhostly writes. Reading them without the app is cat.
Is it really free?
The core is, for personal use — up to five sites, PHP versions, Apache, local HTTPS, Health and Backups, with no time limit. Every install also gets every Vhostly Pro feature for 14 days: unlimited sites, start commands, Force HTTPS, network mode and public URLs, and the Ports, Services and Logs panels. After the trial your sites keep running exactly as they are; only the Pro features lock.
Using Vhostly for or within a business, freelance and client work included, needs a Pro licence — $19 a year, or $59 once for life. The line is the purpose rather than the money: a hobby project that earns nothing needs nothing, a client site you are paid to build needs a licence.
Is Vhostly open source?
No. The app is free for personal use under the Vhostly End User License, and Vhostly Pro is the licence for work. What matters for trust is public: every file it changes is listed in what Vhostly writes, and the one script that runs as root is printed in full on the security page.
Can I contribute?
Yes, with bug reports and ideas. Open an issue in the public tracker on GitHub, or send us a message.