Mount Thor's $45 million raise backs Mac cloud capacity for AI agents

Mount Thor has announced $45 million in equity funding across its seed and Series A rounds to expand cloud infrastructure built on Apple hardware. For teams developing computer-use agents or Apple software, the proposition is access to macOS environments without assembling and operating a local fleet.

The company's funding announcement and the originating 9to5Mac report are both dated November 12, 2026. The company also says it raised separate non-dilutive capital for hardware purchases; that amount is not included in the stated $45 million equity figure. Funding supports expansion, but does not establish the service's performance for a particular workload.

Decide who will operate the Mac

The compute documentation describes two operating models. With Mount Thor-managed compute, customers provision dedicated physical Macs or isolated macOS virtual machines through the portal, CLI, Kubernetes or API. With customer-managed compute, an organization manages its own Macs at a Mount Thor site, typically using its own device-management system.

That distinction determines which operational responsibilities a team takes on. In the customer-managed model, inventory, problem reporting and event notifications depend on the capabilities enabled for the account. It should not be assumed to expose the same lifecycle controls as an on-demand managed instance.

There is also a permissions distinction within managed compute. The bare-metal guide describes access as a permissive, non-root user, while the VM guide gives the guest administrator access. Teams needing system-setting changes or launch daemons should check the documented VM path rather than assuming a dedicated physical machine grants unrestricted administration.

Give the trial a defined end

Mount Thor's quickstart requires access approval and billing setup before allocation. That makes a small, representative trial a more concrete next step than designing around an assumed fleet size.

A useful trial should follow one complete job: create the environment, apply the required software and permissions, run the agent or build task, export its results, then remove the environment. These are our suggested evaluation steps, not a report of TechKili testing the service.

Cleanup needs particular attention. The documentation says releasing a physical Mac wipes it, and deleting a VM removes its disk permanently. Work that must survive therefore needs an explicit export step before teardown. A desktop session that succeeds once is only part of an automated workflow.

For teams also considering how agents divide work, our coverage of Gemini's /swarm preview examines coordination and shared workspace permissions. Compute allocation and authority to act remain separate decisions.

The funding announcement makes more Mac capacity a stated business priority. Whether renting that capacity is worthwhile depends on the actual task, access controls, full job cost and recovery process; the announcement supplies no independent comparison that settles those questions.