Claude’s missing
‘publish’ button

Instantly publish webpages, websites, and even complete apps in seconds.

Which version of Claude are you using?

Using Claude Desktop?

Share what you made in seconds. Seriously, try it out below.

Upgrade to add passwords
roxer.com/
Try it!
Your page is live

Free, no signup. Pages expire after 30 days. Go permanent with a Hosting plan.

Using Claude Code?

Publish Pages
Instantly.

Tell Claude to publish your page to Roxer. Single files, directories, ZIP archives. Your page is live in seconds.

npx -y @roxer/mcp
Learn more 
$ claude

> Publish this landing page to Roxer

Using roxer MCP: pages_publish
Published! /landing-page

> Now publish the portfolio site as a zip

Using roxer MCP: pages_publish
Published! /portfolio
Just say "publish this" Files, dirs, & ZIPs No copy-paste needed 
$ claude

> Build a URL shortener with a SQLite database and deploy it to Roxer

Creating files...
  src/index.js  ✓
  src/db.js     ✓

Using roxer MCP: apps_deploy
Building... done (11s)

✓ Live at: roxer.com/a7f2k9
Detects your framework Builds in the cloud Persistent database

Deploy Production
Apps in Seconds

Deploy Node.js, Python, and React apps with one command. Cloud-built, live on your subdomain.

Node.js Express Flask React Vite Next.js FastAPI
Learn more

Instant hosting for anything Claude builds.

Claude is the fastest way to build. Roxer is the fastest way to ship. Together, you go from idea to live website without touching a terminal, creating an account, or reading documentation. Describe what you want. Claude builds it. Roxer hosts it. You share the link. That's the whole story.

Everything you need.

⚡

Instant URLs

Live in under 3 seconds.

🔒

Password Protection

Lock previews for client eyes only.

🔗

Custom Slugs

roxer.com/your-project-name

🔄

Update in Place

Same URL, new content. No broken links.

📈

Analytics

See who’s viewing, when, and from where.

📦

ZIP Upload

Multi-file projects. Just drag and drop.

One MCP Server. Total Control.

Every prompt below is real. Roxer's MCP server turns plain English into deployed sites and apps.

> Build a landing page for my coffee shop and publish it to Roxer
pages_publish
Published! roxer.com/k8mXp2vR4nQ1
> Publish this at roxer.com/my-portfolio
pages_publish
Published! roxer.com/my-portfolio
> Password-protect it, my client needs to review
pages_publish
Published with password! Share the link and password.
> I redesigned it. Push the new version to the same URL
pages_update
Updated! Same URL, new content.
> Deploy this Express API with a SQLite database
apps_deploy
Deployed! roxer.com/q9Rv5mHx3pT8
> Publish these 5 files as a site: HTML, CSS, and three JS files
pages_publish_files
Published! 5 files at roxer.com/n4Yk8cWf2jR6
> Set the API_KEY env variable and redeploy
apps_deploy
Deployed with 1 env variable set.
> Publish this permanently, no expiration
pages_publish
Published permanently! roxer.com/h7Lp3vBx9mQ4
> Is my app still running?
apps_status
Status: running. Last updated 2 minutes ago.
> Take down the old demo
pages_delete
Deleted.

Add Roxer to your MCP config:

{
  "mcpServers": {
    "roxer": {
      "command": "npx",
      "args": ["-y", "@roxer/mcp"]
    }
  }
}

No API key. No account. No setup.

Go beyond Claude Code.

Pipe it. Script it. Cron it. Drop into the command line for direct control, CI/CD integration, and automation that runs without a human in the loop.

npm install -g @roxer/cli
Publish a page
$ roxer publish ./landing-page
Published! roxer.com/landing-page
Deploy a full-stack app
$ roxer deploy .
Detected: Express + SQLite
Building... done (8s)
Live at: my-app.roxer.com
Tail logs in real time
$ roxer logs my-app
2026-04-05 00:14:32 GET /api/users 200
2026-04-05 00:14:33 POST /api/order 201
2026-04-05 00:14:35 GET /health 200
Manage env vars
$ roxer env set API_KEY sk-abc123
Set API_KEY on my-app

$ roxer env list
API_KEY  sk-ab***
NODE_ENV production
Update in place
$ roxer update my-page
Updated! Same URL.
Check app status
$ roxer status my-app
Running 142 reqs today
In a deploy script
# deploy.sh
$ npm run build && roxer deploy .
Live at: roxer.com/prod
CLI reference | Full docs | npm
The Landscape

Compare for yourself.

Feature Roxer Vercel Netlify Surge.sh
No account needed ✓ ✕ ✕ Email
Paste HTML ✓ ✕ ✕ ✕
CLI deploy ✓ ✓ ✓ ✓
MCP server ✓ Plugin Agent ✕
Full-stack apps ✓ Frontend JAMstack ✕
Build service ✓ ✓ ✓ ✕
Versioning ✓ Git Git ✕
Free forever ✓ Limited Limited Limited
Built With Roxer

What people build.

🏠

Landing Pages

Ship a startup landing page in seconds.

🔒

Client Previews

Password-protected sites for client review.

🎨

Portfolios

Showcase your work with a shareable URL.

🚀

Demos & Prototypes

Interactive prototypes, not screenshots.

🛠

Internal Tools

Dashboards and admin panels for your team.

📬

Email Templates

Preview and share HTML email designs.

Pricing

Simple pricing. Start free.

Free plans. Request access.

Quick Sharing
Share what you made in seconds.
Free
no signup
  • Perfect for quick demos
  • Instant publishing, zero setup
  • Live in seconds, not minutes
  • No account, no signup
  • Stays online for 30 days
  • Paste HTML, get a link
  • Custom URLs
  • Analytics
  • MCP + CLI + API
Start Sharing
Hosting
Your projects, always online.
Free
invite only
  • Everything in Quick Sharing
  • Stays live indefinitely
  • Password protection
  • Custom domains
  • Publish whole websites
  • Deploy complete apps
  • No Roxer branding
  • Detailed analytics
Pages
  • 10 MB files, 20 MB zips
  • Deploy via CLI, MCP, or API
  • Email support
App Hosting
  • Node.js Express, Fastify, Hono, Koa
  • Python Flask, FastAPI, Django
  • SQLite database persistent via EFS
  • Auto-detect framework
  • Environment variables
  • 512 MB memory per app
  • 60s request timeout
  • 20 concurrent connections
Request Access
Max
For power users and agencies.
Free
invite only
  • Everything in Hosting
  • 100 app deployments
  • 1 GB memory per app
  • 120s request timeout
  • 50 concurrent connections
Upgrades from Hosting
  • 100 apps vs 5 in Hosting
  • 1 GB memory per app vs 512 MB
  • 120s request timeout vs 60s
  • 50 concurrent connections vs 20
  • Priority support
Request Access