Mac Studio 24/7 Server
Configured a Mac Studio (192GB RAM, Apple Silicon) as a dedicated always-on server for the client, giving the team shared, secure infrastructure for bots, AI agents, and automation scripts
Mac Studio 24/7 Server Setup
One-Line Summary: Configured a Mac Studio (192GB RAM, Apple Silicon) as a dedicated always-on server for the client, giving the team shared, secure infrastructure for bots, AI agents, and automation scripts.
--
Problem Statement
The client's development team runs multiple long-lived processes. Twilio campaign bots, Hunter AI sync scripts, automation monitoring, and calls processing workloads. These were running on individual developer laptops, which meant:
- Scripts died when laptops went to sleep, rebooted, or lost network connectivity
- No shared infrastructure for collaborative automation work
- No process management. crashed scripts stayed down until someone noticed
- Developers could not reach each other's running services
- No isolation between developer environments (dependency conflicts)
The team needed a dedicated, always-on machine that several developers could use securely, with process supervision that survives crashes and reboots.
Solution
Designed and documented a complete server setup for a Mac Studio (192GB RAM, Apple Silicon) running headless around the clock. The project covers every layer from physical setup through security:
- Always-On Operation. The machine runs without a monitor or anyone at the desk, and comes back on its own after a reboot or power failure.
- Secure Team Access. Every developer can reach the server securely from wherever they work, with access controlled centrally.
- Isolated Developer Environments. Each developer has a private environment, plus a shared space for collaborative scripts.
- Process Management. pm2 for Node.js and Python process supervision, with each developer managing their own processes. Services start at boot and logs rotate automatically.
- Container Support. OrbStack (lightweight Docker runtime, native Apple Silicon) for workloads needing isolation, chosen over Docker Desktop for dramatically lower RAM usage and faster startup.
- Security Hardening. Access and update policies hardened and reviewed as part of the go-live checklist.
The project is documentation-focused: three comprehensive guides (setup overview, step-by-step script, and AI-assisted setup instructions) that enable repeatable, verified deployment.
Tech Stack
| Layer | Technology |
|---|---|
| Hardware | Mac Studio, Apple Silicon, 192GB RAM |
| OS | macOS (headless configuration) |
| Process Management | pm2 (Node.js + Python), launchd (system services) |
| Containers | OrbStack / Docker |
| Package Management | Homebrew, npm, pip/venv |
Key Features
- Zero-Touch Recovery. After a power failure, the Mac Studio restarts and pm2 restores all managed processes. No human intervention required.
- Per-Developer Process Isolation. Each developer runs their own pm2 instance with an independent process list and their own boot persistence.
- Per-Developer Python/Node Environments. Separate virtual environments and node_modules per developer. No dependency conflicts between one developer's Twilio automation and another's calls processing.
- Shared Collaboration Space. A shared scripts area where the team can work on common automation while keeping private work isolated.
- Comprehensive Go-Live Checklist. 25-item checklist covering physical setup, initial configuration, team setup, process management, and validation (including a power-pull test).
- Step-by-Step Setup Script. 19-phase guide with exact commands, verification steps, and expected outputs, designed to be followed linearly.
- AI-Assisted Setup Guide. An AI-assisted setup guide enables phase-by-phase verification and automated troubleshooting.
- Onboarding for Every Platform. Short instructions so team members on Windows or Mac can connect and start working.
Impact / Metrics
- Always-on infrastructure for the client's automation stack. bots and scripts no longer die when laptops sleep
- Isolated environments for each developer (private workspace, separate pm2 instances, independent virtual environments)
- 192GB RAM available for AI workloads, calls processing, and concurrent bot execution. no hypervisor overhead
- Minutes, not hours, to get a new team member connected
- Automatic recovery from power failures validated via power-pull testing
- Scripts targeted for migration: Twilio campaign bot, Hunter AI sync, automation monitoring, and additional automation scripts from developer laptops
Status
Documentation Complete / Deployment In Progress. All three setup guides are finalized. The Mac Studio hardware is available. Setup is being executed following the documented phases, with script migration (Twilio bot, Hunter AI sync, automation monitoring) planned as the final step.