Skip to main content

Deploy your customers' apps.

Your users build apps. Easel puts each one online with its own project, URL, and usage data. You don't run a hosting platform, and you don't send your users to a competitor.

Every way to host your users' apps has a catch

Once your users can build real apps, they need somewhere to run them. The usual options each cost you something.

  • Send them to Vercel

    You hand your users to a competitor.

    Vercel builds v0, its own AI app builder. Every user you send there to deploy meets a product that competes with yours.

  • A server per app

    You pay for idle machines.

    Most generated apps get a handful of visits, but a VPS bills every hour. Your bill grows with every app your users create, not with the traffic they get.

  • Cloudflare Workers

    Your apps hit runtime limits.

    Workers run in a JavaScript isolate, not Node.js, with tight memory and CPU per request. Apps that need native modules or real server work break, or have to be generated differently.

  • Build it yourself

    You start a hosting company.

    Builds, routing, TLS, custom domains, certificate renewal, DDoS protection, logs, and usage metering. It takes months before it's reliable, and none of it is your product.

Easel is the option without the catch: full runtimes, no idle servers, and a host that isn't competing with you.

Every app gets its own project

Each app your users build is its own project with its own URL, builds, environment, and logs. Apps run on full Node.js, not a trimmed-down edge runtime. Busy apps scale with traffic. Idle apps don't hold a machine.

Customer apps
One project per app your users build
AppStatus
recipe-boxrecipe-box-u4821.preview.easelusercontent.comServing
studio-bookingsbook.harbourstudio.comServing
fantasy-draftfantasy-draft-u3307.preview.easelusercontent.comServing
invoice-trackerinvoice-tracker-u1180.preview.easelusercontent.comIdle
wedding-rsvprsvp.ellaandtom.comIdle

Deploy with your framework

Every edit is a new deployment

Your users change their apps constantly. Each change becomes its own deployment that uploads only the files that changed, and Instant Rollback undoes a bad edit without a rebuild.

recipe-box
recipe-box-u4821.preview.easelusercontent.com
v14Add a shopping list from saved recipesCurrent
v13Let guests rate recipesRoll back
v12Switch to a dark themeRoll back
v11Search recipes by ingredientRoll back

Know what every app uses

Pull usage for any customer app from the usage endpoint: requests, function time, and bandwidth. Then bill your users however you like: plans, credits, or straight pass-through.

GET /v1/usage?period=2026-10
{
  "period": "2026-10",
  "projects": [
    {
      "project": "recipe-box",
      "requests": 182340,
      "functionDurationGbHours": 4.21,
      "dataTransferGb": 12.8
    },
    {
      "project": "wedding-rsvp",
      "requests": 0,
      "functionDurationGbHours": 0,
      "dataTransferGb": 0
    }
  ]
}

Your customers' domains

Customers can put their app on a domain they own. Easel checks DNS, then issues and renews the certificate, so you never handle TLS.

Domains
Certificates issue and renew automatically
DomainStatus
book.harbourstudio.comstudio-bookingsValid Configuration
rsvp.ellaandtom.comwedding-rsvpValid Configuration
shop.northfieldbakery.combakery-ordersProvisioning SSL
app.tidyledger.ioinvoice-trackerInvalid DNS

How we work together

We onboard every platform directly, so the integration fits your product instead of the other way around.

  1. 01

    Walk us through your deploy flow

    Show us what happens today when one of your users publishes an app, and where it hurts.

  2. 02

    We set up the integration with you

    Together we connect how your product creates deployments, attaches domains, and reports usage.

  3. 03

    Launch with our engineers on call

    Your users' apps run on Easel, with a direct line to the people who built it.

Questions

Do you compete with us?

No. Easel doesn't make an app builder. We run the apps; you keep the relationship with your users.

Do we need to change the code our product generates?

Not if your generated apps use a supported framework: Next.js, TanStack Start, Nuxt, React Router, SvelteKit, or Vite. Easel builds them the same way it builds any other project.

What happens to apps nobody visits?

They stay deployed and keep their URL. Server code only runs when a request arrives, so an idle app doesn't hold a machine.

Can our customers use their own domains?

Yes. Each domain is attached to the app it belongs to, and Easel issues and renews its certificate automatically.

Can we bill our users for what their apps use?

Yes. The usage endpoint reports what each app used, so you can charge per plan, per credit, or pass costs straight through.

How do apps get from our product onto Easel?

Your product hands Easel the generated files and Easel builds and deploys them. We set up that integration with you during onboarding, around how your product already works.

Keep your users. Let us run their apps.

Show us how your users deploy today, and we'll show you what running their apps on Easel looks like.