Meta Gives Every Muse User a Free Ubuntu VM. It Is Not a Web Host.
Meta’s Muse agent ships with a dedicated Ubuntu machine per user. It has a shell, a package manager, a browser, and a filesystem that survives between sessions. People noticed, and the phrase “free VPS” started circulating within days.
That phrase is doing a lot of work it has not earned. A machine and a host are not the same thing, and the difference is written down — not in a marketing page, but in the document that actually governs the machine.
What Meta is actually handing out
The product is an agent. The machine exists so that the agent can run commands, install packages, write files and browse, without touching anything outside a container. Meta’s own description of the architecture is about isolation, not about serving: a “Runtime Cell” the agent works inside, a separate “Sentinel” process watching from outside, credentials held outside the cell entirely.
That is a security design for a thing that executes instructions. It is not a hosting design, and the difference matters the moment you ask the machine to be reachable at an address, on a schedule, for years.
I have not run a site on it, and I am not going to claim I have. What follows is a reading of the governing document plus the published architecture. Where a number or a capability is not documented publicly, I say so rather than filling the gap.
The word “hosting” does not appear in the terms
I searched the Muse Supplemental Terms of Service for the vocabulary a hosting contract always contains:
| Term | Occurrences in the terms |
|---|---|
hosting | 0 |
server | 0 |
uptime | 0 |
SLA | 0 |
bandwidth | 0 |
Absence is the evidence. A hosting agreement defines an uptime target, a bandwidth allowance, a backup regime, and a remedy when the target is missed — because that is what the customer is buying. This document defines none of those things, because nobody is buying them.
What it does define is the opposite: a set of explicit non-promises. Four sentences decide the question.
The four sentences that settle it
| The terms say | What it means if your site lives there |
|---|---|
| “MUSE IS PROVIDED ON AN ‘AS IS’ AND ‘AS AVAILABLE’ BASIS.” followed by “META MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED.” | There is no quality commitment of any kind. “As available” is the contractual way of saying availability is not part of the deal. |
| You do not get a guarantee that “Muse will be continuously available without interruption or that Muse will be error-free.” | Downtime is not a breach. It is the expected state of an “as available” service. |
| Meta “may suspend or terminate your access to Muse or its features, or remove, disable, or restrict access to any artifact created with Muse, at any time, for any reason, without prior notice or liability.” | Anything you build can be removed, and the reason does not have to be your fault. |
| On termination, “any pending or in-progress actions may be cancelled without completion” and Meta “is not responsible for any consequences resulting from incomplete actions.” | The exit is not graceful, and the consequences of an ungraceful exit are yours. |
Read the third one carefully, because it is the one people skip. The clause continues “including: (i) to prevent a security risk … (ii) if required by law; or (iii) for violations of these Terms.” Those three are examples attached to “including,” not a closed list. The operative grant sits before them: at any time, for any reason.
That is not unusual for a consumer AI product. It is disqualifying for a host. Every hosting contract I have read commits to something — a maintenance window, a notice period, a refund, a migration window. This one commits to nothing and reserves everything.
The port question, and why it does not save the argument
The objection is predictable: none of that says the machine cannot serve HTTP. True. Nothing in the document forbids it, and nothing in the document permits it either — the document simply never contemplates the machine as a server, which is why the word never appears.
Whether the machine accepts inbound connections at all is not documented in anything I could reach. I am not going to guess. But notice what happens to the argument even if it does: you would have an endpoint that is reachable today, governed by a contract that promises it will not necessarily be reachable tomorrow, on infrastructure whose operator may remove what you built without notice.
Technical possibility and contractual dependability are different questions. The first one decides whether you can demo something this afternoon. The second decides whether you can point a domain at it and stop thinking about it. Only the second one matters for a site.
What it is genuinely good for
Plenty, and this is not an argument against the product.
- Running a script to see whether a dependency resolves on a clean Ubuntu image.
- Learning your way around a Linux box without provisioning one.
- One-off jobs: convert a batch of files, crawl a page, test an API before you commit to it.
- Reading the filesystem of an agent to understand what it actually did — the transparency is unusual and genuinely useful.
The common thread is that nothing there needs to exist tomorrow. The moment something does, you need a contract that says it will.
The thing worth taking away
The transferable lesson is not about Muse. It is about the two words to search for in any free tier’s terms before you depend on it: “as is” and “terminate.”
Most free tiers are honest about being free — someone else is paying, and you are the product or the test case. That is a fair trade when the thing you are running is disposable. It stops being fair when the thing is your site, because the cost of the trade is not the price. It is the afternoon you spend rebuilding somewhere else.
If free hosting is the actual goal, the question to ask is not “how big is the machine” but “what happens on the day it ends.” That is a different article, and the answers are more boring and more useful: how the free static tiers actually meter you, and what deploying to one of them looks like end to end.
The judgement, stated plainly
The Muse VM is a good machine attached to a product that never promised to keep it running. Treat it as a workbench, not a foundation. If you want to host a site for free, pick a platform whose business model survives your traffic — and check the terms for those two words before you move the domain, not after.
Sources
Primary documentation only — the provider's own page, the specification, or the standard itself. Claims that rest on anything else are described in the text as a market pattern or an inference, not as documentation.
Written by Sam Wang. Spotted something out of date? Tell us.