Skip to main content

Ship what your agent built.

Your agent wrote the app. One command puts it online with a real URL, HTTPS, and a working backend. No cloud account to wire up, no infrastructure to learn.

Your agent can write the app. Getting it online is where it stalls.

Building got fast. Hosting still asks for infrastructure knowledge the app never needed.

  • Static hosting

    Your backend doesn't come along.

    The pages go up, but API routes, server rendering, and database calls need somewhere else to run.

  • A VPS

    You become the sysadmin.

    SSH, nginx, certificates, and security updates, for an app that took an afternoon to build.

  • Your laptop

    It's only online while your laptop is.

    There's no stable URL to share, and it stops when you close the lid.

  • A big cloud console

    Your agent gets lost in setup.

    IAM roles, regions, and twenty services to choose from. Every step is a chance for your agent, or you, to guess wrong.

Easel is one command between "it works on my machine" and a link you can share.

One command

No Git required. The CLI uploads only what changed and builds remotely, with server rendering, API routes, and server actions working as they do locally. It skips .env files by default, so an agent can't upload your secrets.

habit-tracker
Agent session
You

This works locally. Put it online.

Agent

Deploying to production with the Easel CLI.

$ npx @easel-sh/cli deploy --prod --wait --yes

Deployment
  ID:     dpl_7hq2mx9c
  Target: production
  Status: READY
  URL:    https://habit-tracker-maya.preview.easelusercontent.com

It's live at habit-tracker-maya.preview.easelusercontent.com.

Deploy with your framework

Docs your agent can read

Your agent looks up the answer instead of guessing.

  • llms.txt

    An index of every docs page, plus the full corpus in one file, for agents that read whole sites.

  • Markdown docs

    Append .md to any docs URL and your agent gets clean Markdown instead of HTML.

  • MCP server

    Search and read the Easel docs from Cursor and other MCP clients.

The rest is handled

The parts of hosting you'd otherwise ask your agent to figure out.

  • Your own domain

    Point a domain you own at the app. HTTPS certificates issue and renew automatically.

  • A way back

    If your agent's last change broke something, Instant Rollback restores the version that worked, without a rebuild.

  • Private previews

    Every deploy gets a preview URL. Require sign-in so only your workspace can open it.

Questions

Is it free?

Hobby is free for personal projects within its included limits. Commercial projects need Pro, which is $20 a month for the whole workspace and includes $20 of usage.

Do I need Git?

No. easel deploy uploads straight from your machine. Connect a GitHub repository later if you want a deploy on every push.

Does my agent need special setup?

No. Point it at /llms.txt or the MCP server and it reads the same docs you do. The CLI's --wait and --format json flags give it output it can check.

Will it upload my secrets?

Not by default. The CLI skips .env files. Set environment variables in your project settings instead.

Which frameworks work?

Next.js, TanStack Start, Nuxt, React Router, SvelteKit, and static Vite apps. Each framework guide lists what's supported.

Put your next project online

Free for personal projects. One command from your agent to a link you can share.