Freelancers can live on Free with one PHP project. Agencies on one MacBook often need Bitrix + Laravel + WordPress + Next + legacy at once. Pro removes the project cap; Teams removes the seat cap.
Typical studio Mac map
| Project | Stack | MacFullStack |
|---|---|---|
| Corp Bitrix | PHP, MySQL, multisite | Native, aliases (/blog/bitrix-multisite-mac) |
| Laravel SaaS | PHP, Redis, queue | Pro workers (/blog/laravel-praktiki-mac) |
| WP storefront | PHP, hosting import | Docroot detection (/blog/wordpress-na-mac) |
| Next storefront | Node | Node proxy (/blog/nextjs-laravel-mac) |
| Django internal | Python | Python proxy (/blog/django-flask-fastapi-mac) |
| Greenfield API | Postgres | Pro PostgreSQL (/blog/postgresql-pro-mac) |
Everything under ~/MacFullStack/www/ — symlink instead of copy when repos already live in git.
Organization
- Clients — FTP and contacts on the client card, not scattered Notes.
- Tags on projects —
bitrix,support,greenfield. - Custom zone
.localdevor.testin Settings → Domains — separate from client.localhostclones. - Gatekeeper — if Docker Desktop or another stack took 3306/8080: /help/gatekeeper-ports.
Mac resources
- Native by default — one nginx/php-fpm, not ten containers.
- Stop unused workers (queue, Vite proxy) on project cards.
- One MySQL for all PHP projects — separate databases per site.
Team of two or more
Teams — 10 Macs, same Pro feature set: /blog/teams-dlya-studii. Shared .macstack.json in git aligns PHP version and runtime hints for onboarding.
When Pro pays for itself
One FTP Manager hotfix plus one Share client demo often beats a year of FileZilla + ngrok + MAMP Pro. Compare: /compare, /pricing.