Manus does the work in one task. Keeping the site online is a second job.
Manus is an agent: it researches, writes, designs and ships a site while you do something else. What it hands back is either a folder of files in its sandbox or a full-stack web app on its own cloud. Here is where people get stuck turning that into their website.
Hosting draws on your credits
Published Manus web apps are billed per request from your credit budget. Each account gets a $10 monthly allowance, shared between hosting and database use. A busy week of visitors competes with your next task.
Cold starts and one US region
By default a published app runs in a US region and scales to zero when nobody visits. The first visitor after a quiet spell waits for an instance to start, and readers far from the US wait on every request.
Your own domain needs a paid Manus plan
Manus’s help centre reserves custom domain connections for paid users. On the free plan you can ask for a code package and deploy it somewhere else yourself.
The code export isn’t a website yet
A Manus web app downloads as a React and Tailwind project, often with a server and a database behind it. Upload that folder as-is and you get a blank page or a file listing.
Files live in Manus’s sandbox
In agent mode Manus writes index.html, a stylesheet and images on its own cloud computer. Copy one file out and the styling or images go missing, sometimes because a path points at /home/ubuntu/.
Forms, a blog and stats cost more tasks
Manus can build a contact backend or a CMS, but each one is more credits to build and more usage to host. Most sites just need the form to reach an inbox and a place to post updates.
Manus behaviour as described in its own documentation: Manus publishing and hosting modes, Manus custom domains and Manus custom MCP servers (checked September 2026). Check their pages for current terms.
Where a Manus website can live
What Manus’s own Publish gives you on the free and paid plans, and what the same site gets as static files on Fylo. The last row is there because it’s true.
| What you need | Fylo.Host | Manus PublishFree plan | Manus PublishPro, from $20/mo |
|---|---|---|---|
| Hosting that doesn’t use agent creditsFlat monthly price | ✓ | $10/mo allowance | Usage from credits |
| Served from the edge, no cold startsFast for visitors outside the US | ✓ | US region, scales to zero | US region, scales to zero |
| Your own domainSSL and www handled | Starter and up | ✗ | ✓ |
| Form submissions to your inboxSpam filtering included | Pro and Business | Build it by prompt | Build it by prompt |
| Built-in blog with editor and RSS10 posts on the free plan | ✓ | ✗ | ✗ |
| One-click WebP, font subsetting, lazy load, JS delay | ✓ | In your code | In your code |
| Host code from any AI, or written by hand | ✓ | Manus projects | Manus projects |
| Ask Manus to publish and update it | ✓Over MCP | ✓ | ✓ |
| Logins, database, Stripe, background jobsApps with a backend | ✗ | ✓ | ✓ |
How to host a website made with Manus
Three steps. The quickest is to let Manus publish over MCP; if you’d rather handle the files yourself, both manual routes are below.
Connect Manus, or get the files
Add https://fylo.host/mcp as a custom MCP connector once. Or ask Manus for “the whole site as a single index.html”, or download the folder it made.
Fylo.Host · https://fylo.host/mcp
// or the files
site/ index.html · style.css · images/
Publish from Manus, or paste
Tell Manus to publish to Fylo, paste the HTML into the editor at the top, or drop the folder on the homepage. Type a subdomain or let us pick one.
Share and grow it
Live in seconds on any phone or browser. Sign up free to keep it online, then add your domain, a blog, forms and speed settings from the dashboard.
One page? Ask Manus for a single HTML file.
Landing pages, portfolios, event pages and research write-ups fit in one file. Send Manus this prompt, then paste what it returns into the editor above. No Node.js, no terminal, and the words sit in the HTML where Google reads them.
Multi-page site or web app? Ship the static build.
Plain-HTML folder from agent mode: upload it as-is on the homepage. React web app: download the code, build it once, and upload the folder that holds index.html.
npm install && npm run build
// find the folder with index.html
dist/ or dist/public/
// drop it on fylo.host
Paste the Route B prompt into Manus before you download, so the files arrive ready to host. Rather not run a build yourself? The Agent prompt tab lets Claude Code or Cursor do the build and the upload.
Six things that go wrong moving a Manus site, and the fix for each
None of these are Fylo quirks. They happen on every static host, and each one has a short fix.
White page, or raw code on screen
You pasted a .tsx component from a Manus web app. It needs React, its imports and a build step before a browser can show it.
Plain black text, no layout
Only index.html got uploaded. The stylesheet and scripts Manus wrote are separate files the page can’t find.
Images show as broken icons
The page points at a path on Manus’s computer, like /home/ubuntu/images/hero.png, which doesn’t exist anywhere else.
Home works, refreshing /about doesn’t
A React web app draws every page from one index.html. Refreshing an inner page asks the host for a file that isn’t there.
Login, data or checkout stopped working
Those parts talk to the server and database Manus hosts for your app. A static copy has the pages but not the backend.
npm install errors on the downloaded code
The project may ship a pnpm-lock.yaml, and version conflicts between packages can stop npm cold.
npx pnpm install, or npm install --legacy-peer-deps.Built for sites an agent made
Everything below is on by default or one toggle away in the dashboard — and most of it Manus can drive for you over MCP.
/blog/. 10 posts on the free plan. Blog guideFree plan: 1 site and 10 MB, plenty for a Manus site, with a small “Hosted with Fylo.Host” badge. Custom domains start on Starter and forms on Pro — see pricing. More on HTML website hosting, ZIP file hosting and landing page hosting.
Manus made the site. Let it write the blog too.
A one-page site gets one chance to rank. A blog gives Google a reason to come back — and Manus is already good at researching and writing the posts. Fylo gives them a home next to your pages.
- Turn it on in one step. Blog tab → choose the site → Enable blog, or ask Manus to enable it over MCP. It appears at
/blog/; your files are left alone. - Manus drafts, you approve. Posts created over MCP start as drafts with a preview link, so nothing goes live until you say so.
- Or write it yourself. Visual or Code editor with a media library, categories, tags and a cover image. No redeploy for a new post.
- The SEO plumbing is done for you. Clean URLs, canonical and Open Graph tags, article structured data, an RSS feed and a sitemap.
- 10 published posts on the free plan, unlimited on paid plans. Posts render as static HTML, so they load as fast as the rest of the site. Blog guide
yourdomain.com/ ← the page Manus built
yourdomain.com/pricing/ ← from its folder
yourdomain.com/blog/ ← post index
yourdomain.com/blog/our-launch/
yourdomain.com/blog/feed.xml ← RSS
yourdomain.com/blog/sitemap.xml
// from Manus, connected over MCP
you: research what our customers ask most
and draft a post answering it on the Fylo blog
Manus: Draft saved · preview link
The Manus sites that end up on a real domain
Fylo next to the usual suspects
Netlify and GitHub Pages can both host the files Manus makes. Here is where they differ, taken from their own pages. Where a site doesn’t say, we don’t guess.
| What you need | Fylo.Host | Netlify | GitHub Pages |
|---|---|---|---|
| Free planNot a trial | 1 site, 10 MB | 300 credits/mo | Public repos on free accounts |
| Publish without Git | ✓ | ✓ | ✗ |
| Flat price, no metered usage | ✓ | Credits per deploy, GB | ✓ |
| Business or shop site allowed | ✓ | ✓ | Not for online businesses |
| Live preview before publishing | ✓ | Deploy previews | ✗ |
| Built-in blogEditor, categories, RSS | ✓ | ✗ | Jekyll, via Git |
| Host-side WebP, font subsetting, JS delay | ✓ | Image CDN | ✗ |
| Runs server code and functions | ✗ | ✓ | ✗ |
Netlify and GitHub Pages details as published on their sites, checked September 2026. Check their pricing and usage pages for current terms. Full comparisons: Fylo vs Netlify and Fylo vs GitHub Pages. Made it with another AI? See Claude artifacts hosting, ChatGPT website hosting, Gemini website hosting and v0 hosting.
Keep Manus hosting when it’s an app. Host on Fylo when it’s a website.
Manus’s own hosting is the better fit when
- The app needs member logins, a database, Stripe checkout or a secret API key.
- It runs background jobs, bots or WebSocket connections on a reserved instance.
- Traffic is light enough that the monthly allowance covers it, and your visitors are mostly in the US.
- You’re on a paid Manus plan and want the app, domain and database in one place.
Host it on Fylo when
- It’s a website — marketing, portfolio, report, event or docs — and you’d rather not pay for it in agent credits.
- Your visitors are in India, Europe or anywhere a single US region is far away.
- You want a contact form, a blog and real visitor numbers without building them.
- You’re on the free Manus plan and still want the site on your own domain.
Manus website hosting questions
index.html, paste it into the editor at the top of this page and press Publish & Share. Or download the folder of files Manus made and drop it on the homepage. Either way the site is on its own URL in seconds. Sign up free to keep it online.https://fylo.host/mcp and save, then approve the Fylo sign-in. If no sign-in window opens, add a custom header Authorization: Bearer followed by an API key from your Fylo dashboard. Then ask Manus to publish the site to Fylo. Later requests update the same URL.index.html, often dist or dist/public. Parts that need Manus’s server, such as logins, the database or payments, will not run on a static host. For a simple site it is quicker to paste the rewrite prompt on this page into Manus and let it produce plain HTML instead.index.html was uploaded, so the separate CSS, JavaScript and image files are missing: upload the whole folder. Or the page points at a path that only existed on Manus’s computer, such as /home/ubuntu/. Ask Manus to use relative paths for every file, then upload again./blog/ next to the pages Manus wrote, with an RSS feed and a sitemap. Nothing in your uploaded files is changed. With the MCP connector, Manus can write and publish posts too. The free plan includes 10 published posts. Blog guide.title and meta description on every page, and a Fylo site has nothing telling crawlers to stay away.Manus did the work.
Give it a home that doesn’t cost credits.
Paste once, or let Manus publish. We handle the milliseconds.
Host your Manus site free No signup to try. No Manus credits used. Live in seconds.