Melbourne, Australia · Hosted Mac mini
A dedicated Mac mini in Melbourne, kept online and ready for Claude. Skip the desk hardware, the home upload link and the machine you have to restart from another country.
From $299 / month · Claude Max seats optional · No free tier
Hosted Mac mini plans
Every plan includes a dedicated Mac mini, power, network and remote access. Add a Claude Max seat when you want one invoice and one workspace. There is no free tier.
A dedicated Mac mini in Melbourne for your own Claude account and workflow.
Billed monthly through Stripe.
Inside the Base plan
The Mac mini plus a Claude Max 5x seat for daily coding, research and agent work.
Billed monthly through Stripe.
Everything in Base, plus
More Claude headroom for heavier agent runs, long sessions and larger daily throughput.
Billed monthly through Stripe.
Everything in Max 5x, plus
Checkout opens directly on Stripe. Prices are in USD, renew automatically until cancelled and exclude local taxes. Claude plan availability is confirmed before onboarding.
What sits inside the monthly price
Hosting should feel like a utility, not a pile of adapters. Every plan includes the physical machine, power, network and a human path back in when something breaks.
One monthly price covers electricity, connectivity and the machine staying online in Melbourne.
HDMI video and USB keyboard/mouse control operate outside macOS, so access does not depend on a background agent.
The machine sits on an Australian network with a route chosen for stable remote work from Asia-Pacific.
If the remote path drops, we help diagnose the capture, power and network layers before touching your files.
Infrastructure notes
The useful part of remote hardware is not a screenshot of a Mac. It is reliable access, clear tenant boundaries and a recovery path that still works when the operating system does not.
Each Mac mini has a dedicated capture appliance connected to HDMI and USB. Control is available from outside the operating system.
Tenants are separated at the network layer. Direct east-west access between customer machines is blocked by default.
Your working network and the capture appliance management path are separated, preserving an independent recovery route.
Machines live in a dust-controlled, temperature-managed rack instead of a shelf beside someone’s router.
Administrative access is limited, logged and allocated per device. Customers do not share a root management path.
Melbourne hosting with routing tuned for mainland China, Hong Kong and wider APAC access. Carrier conditions still apply.
The capture appliance is a separate physical layer. If the operating system freezes, video, keyboard and mouse control can remain available through the management network.
Procurement and deployment
New hardware is received, logged, imaged and mounted before it reaches a customer. These are the stages we standardise so every allocation starts from the same baseline.
From subscription to first connection
We confirm the workload and access path before provisioning. The first session is a handover, not a login screen and a guess.
Choose a Mac mini plan or add Claude Max. We confirm the intended workload before accepting the allocation.
Sign in with Google, complete the Stripe subscription and confirm the remote-access method for your network.
The Mac mini is imaged, assigned to your account, connected to capture hardware and placed on its isolated VLAN.
Complete a guided first connection, verify video and keyboard control, then keep the workspace online from anywhere.
Before you commit
Still unsure about a network path, data boundary or Claude seat? Ask before subscribing. We prefer a clear fit over a rushed allocation.
hello@claude-mac-mini.homesIncluded from day one
Use the same machine from a laptop in Shanghai, a studio in Singapore or a desk in Sydney. Your environment stays put.
Your account receives the device assignment. Administrative access is not shared between tenants.
Keep local projects, browser sessions and Claude context on the same always-on machine.
Choose the base machine or add a higher Claude usage tier when your workflow needs it.
Hardware control and network isolation are part of the design, not an afterthought.
