v1.32.0 Static hosting for agents

Instant web hosting for agent-built apps.

Publish HTML, dashboards, games, tools, and SPA prototypes to a permanent upesi.dev subdomain. Deploy from the CLI, or wire Upesi into your agent over MCP.

Install CLI Connect MCP

0.8s: avg deploy
SPA: per app
UpesiDB: built in

$upesi create my-app --spa

ok app created - my-app.upesi.dev

$upesi sync .

uploading 42 files - 1.2 MB ok deployed in 0.8s

$upesi open

// agent -> mcp server

>upesi_app_create({ name: "my-app", spa: true })

ok app ready - my-app.upesi.dev

>upesi_files_upload({ dir: "./dist" })

ok 42 files synced

>upesi_app_spa_enable()

02 / Install

Two install paths. One hosting surface.

Pick a CLI for terminal-driven deploys, or expose Upesi to your agent through MCP. Same projects, same URLs, same capabilities.

Option 01 ~5 sec

Use the CLI

Install one local binary. Then run upesi login and deploy from any project folder.

$ curl -sSf https://api.upesi.dev/install.sh | bash

macOS / Linux / Windows Install guide

Option 02 no install

Use MCP

No CLI install required. Add the MCP server to your agent, complete OAuth there, and let the agent manage projects directly.

→ https://api.upesi.dev/mcp

Claude / Cursor / custom agents Agent guide

03 / Capabilities

What you get on every app.

Authenticated and persistent by default, with the primitives agents and humans both need after the first deploy.

URL

Permanent subdomain

Every app gets a stable Upesi URL, not a throwaway preview.

SPA

Client-routed SPAs

Per-app SPA mode falls back to index.html for extensionless browser routes.

DOM

Custom domains

Point DNS to ingress.upesi.dev and check status before going live.

UpesiDB

Document storage per app. State survives deploys with no separate setup.

PWD

Password gates

Lock any app behind a shared password for staging or client review.

API

OpenAPI + llms.txt

Readable for humans, machine-readable for agents and MCP clients.

04 / Flow

Same result, either path.

Both paths create authenticated, persistent apps with files, SPA mode, passwords, custom domains, and UpesiDB.

CLI flow

upesi create my-app --spa upesi sync . upesi open

MCP flow

upesi_app_create upesi_files_upload upesi_app_spa_enable

https://my-app.upesi.dev Live / 0.8s

05 / FAQ

Questions agents ask first.

What is Upesi?

Minimal static hosting for small apps built by people and agents. Every app gets a stable Upesi subdomain, authenticated and persistent by default.

Do I need anonymous 24h preview deploys?

No. Upesi is built around authenticated, persistent apps so files, domains, passwords, and database state stay manageable over time.

Does it support client-routed SPAs?

Yes. SPA mode is set per app and only falls back to index.html for extensionless browser routes. Static assets and API calls pass through normally.

Can I use my own domain?

Yes. Add a custom domain and point DNS to ingress.upesi.dev. Upesi exposes DNS status checks so you can verify the setup before going live.

Where should an agent start?

For CLI usage, install from https://api.upesi.dev/install.sh. For MCP, connect to https://api.upesi.dev/mcp and read llms.txt.