EasyHost docs: the ezhst CLI

Quick start

For agents

Run the installer and choose Global for all projects or Local for the current project, then ask your agent to deploy.

npx ezhst skill install

Then tell it: Deploy this to EasyHost. The agent deploy guide walks through it for each agent. The agent creates an account if you do not have one, creates and links a project, sets environment variables and deploys.

For humans

Install the CLI globally or run it with npx.

npm i -g ezhst

Create an account (or log in), link your Node.js app folder and deploy.

npx ezhst register
npx ezhst verify <code>
npx ezhst link
npx ezhst deploy

Already have an account? Use npx ezhst login instead of register. You can also sign up in the dashboard.

Installing the agent skill

The skill is a single SKILL.md file that teaches your agent how to use EasyHost.

Claude Code uses .claude/skills, Codex uses .agents/skills and Cursor uses .cursor/skills, under your home folder for Global or the current directory for Local. Choose Local to check the skill into the repo for your team. For noninteractive use, including --json, pass --agent <claude|codex|cursor> and exactly one of --global or --local.

For other agents, ask them to read the raw file at https://easyhost.fun/skill.md before deploying.

Authentication

Verification is mandatory. Until you run ezhst verify with the code from your inbox, other commands are rejected. In the dashboard, the same code is entered on the screen shown after sign up.

login and register save your token in ~/.easyhost/config.json. In CI or agent sandboxes, provide the token with the EZHST_TOKEN environment variable instead.

EZHST_TOKEN=<token> npx ezhst deploy --json

Output and prompts

• Every command accepts --json for machine readable output. Agents should always use it.
• In a terminal, missing values are asked for interactively. Without a TTY the CLI never prompts: it fails with a message naming the missing flag.

Projects and linking

A project contains up to three apps (Node.js apps and AI Builder apps count together) and five scheduled API calls, with a shared storage bucket and database. Each app has its own subdomain: <app-slug>.easyhost.fun.

Project-scoped commands use the project linked in .easyhost.json. Pass --project <slug> to any of them to target another project.

ezhst projects create my-project
ezhst projects list
ezhst apps create my-api --project <project-slug>
ezhst link --project <project-slug> --app <app-slug>

Deploying

Use ezhst apps list, ezhst apps create <name>, and ezhst apps delete --app <slug> --yes to manage up to three apps per project. Deployment, environment, build, domain and runtime commands accept --app <slug-or-id>. Link an app with ezhst link --project <slug> --app <slug>.

What gets uploaded

deploy uploads your project source. It skips node_modules, .next, .git and every .env* file. No changes to your project are needed.

Your app is live at https://<slug>.easyhost.fun once the build finishes.

Environment variables

Variables are applied on the next deploy or redeploy.

ezhst env set NEXT_PUBLIC_SITE_URL=https://my-app.easyhost.fun
ezhst env import .env.production
ezhst redeploy

Build settings

Empty settings are auto-detected, which works for most Node.js apps.

Supported frameworks include Next.js, Nuxt, Express, NestJS, Fastify, Hono, Koa, AdonisJS, Remix, SvelteKit, Astro and Strapi. SvelteKit and Astro projects need their Node adapters; any other framework works when its production start command listens on 0.0.0.0:$PORT.

Auto-detection

ezhst build set --node 22 --root-dir apps/web
ezhst build set --install ""
ezhst redeploy

Logs and build logs

When a deploy fails, read the build log, fix the cause and run ezhst deploy again.

ezhst deployments log --json
ezhst logs --tail 200

Custom domains

DNS records

ezhst domains add www.example.com
ezhst domains list
ezhst domains verify www.example.com

Storage S3 compatible

Each project gets one bucket. Files are public by URL.

Using it from your app

Run ezhst storage info, store the credentials with ezhst env set, then use any S3 client. The endpoint is https://storage.easyhost.fun, the region is us-east-1 and requests must use path-style URLs.

import { S3Client, PutObjectCommand } from "@aws-sdk/client-s3";

export const s3 = new S3Client({
  endpoint: "https://storage.easyhost.fun",
  region: "us-east-1",
  forcePathStyle: true,
  credentials: {
    accessKeyId: process.env.S3_ACCESS_KEY_ID!,
    secretAccessKey: process.env.S3_SECRET_ACCESS_KEY!,
  },
});

export const uploadAvatar = async (userId: string, body: Buffer) => {
  await s3.send(
    new PutObjectCommand({
      Bucket: process.env.S3_BUCKET!,
      Key: `avatars/${userId}.png`,
      Body: body,
      ContentType: "image/png",
    }),
  );
};

The file is then served at the public base URL from storage info followed by its key.

Database Postgres

Each project gets one managed Postgres database. See free Postgres hosting for what is included.

Connecting your app

Copy the connection string from ezhst db info into your app's environment. It works with Prisma, Drizzle or any Postgres client.

ezhst db create main
ezhst db info --json
ezhst env set DATABASE_URL="postgresql://..."

Prisma migrations

prisma migrate dev needs a shadow database. Use the shadow connection string from ezhst db info.

datasource db {
  provider          = "postgresql"
  url               = env("DATABASE_URL")
  shadowDatabaseUrl = env("SHADOW_DATABASE_URL")
}

After ezhst db reset-password, update DATABASE_URL with ezhst env set and run ezhst redeploy.

Scheduled API calls

Create up to five schedules per project. Calls support public HTTP/HTTPS URLs, request headers and a body. Intervals range from 1 to 43200 minutes. Calls time out after 30 seconds and do not follow redirects.

The first call follows one full interval. Saving or resuming restarts the interval. Execution may be delayed by the 10-second worker poll or available capacity. Missed intervals are skipped after downtime, and calls to the same schedule do not overlap. Requests already in progress may finish after pausing or deleting.

Email coming soon

Transactional email for your apps is coming soon. It is not available yet: the dashboard Email page shows Coming soon, and the ezhst email commands and the email API return Email is coming soon. Account emails from EasyHost itself, such as verification codes, password resets and invites, are still sent.

Team members

Invite people to a project by email. Members can manage everything in it. Only the owner can invite, revoke invites, remove members, rename or delete the project.

AI Builder dashboard

The AI Builder turns a description into a running app. Open Builder in the dashboard, create an app and describe it. The name becomes its address, https://<name>.easyhost.fun.

For a new app or a big feature, the AI asks a few questions, shows a short plan to approve and lets you pick one of 9 themes before it builds. Small changes go straight to code. Every step is shown live: files written, SQL run and packages installed.

AI apps are plain JavaScript Hono servers. They use the project's Postgres database and storage when they need them (email is coming soon), and work with environment variables, logs and custom domains like any other app. The AI Builder is not part of the CLI.

Each account gets its first AI app and its first build free. After that, AI requests use AI Tokens, bought once in the dashboard and never expiring: 500 tokens for $5, 1,100 for $10, 2,400 for $20 or 6,500 for $50. Each request is charged by how much work it takes, and a typical full build is a few hundred tokens. Hosting AI apps stays free, and AI apps count toward the 3 apps per project.

Limits

EasyHost hosting is free within these limits. The AI Builder uses AI Tokens after your first free AI app and build. Node.js apps are supported, including Next.js and HTTP APIs. The free Next.js hosting page explains what each limit means in practice.