For the tools your team keeps asking for
ezship turns a folder of React into a deployed internal app. You or your coding agent edits it, one command ships it, and every app your organisation builds runs on the same database, the same people and the same sign-in. There are no servers, pipelines or auth code to write.
Invite-only by design. Every app needs a signed-in Member.
# every app your team has, in one folder
$ ez clone acme
pulled 7 sites into acme/
$ cd acme/qc-line
# edit by hand, or hand it to your agent
$ claude "add a defect log with photos"
$ ez preview
✓ rules ✓ types ✓ build
acme.ezship.site/qc-line/~preview/k2f9/
$ ez push && ez deploy
✓ version 42 by dana@acme.com
✓ live at acme.ezship.site/qc-line/Built for the apps nobody has time to build
How it works
A Site is a small React and TypeScript app with a fixed shape. It has no package.json,
no config and no build setup to maintain. You write screens; ezship does the rest.
ez pull copies a Site's shared files into a working copy: a plain directory you
can version with your own git and open in any editor.
Edit it yourself or have an agent do it. ez preview builds on our Builder and
serves the result at a private URL against your real data. ez dev rebuilds
after every save. Nothing runs on your machine.
ez push records one atomic Version with who made it and when.
ez deploy checks the Rules, type-checks and compiles with the React Compiler, then
swaps the app in whole. If the build fails, the running app stays as it was.
What you write
useLive reads a Table and re-renders the moment anyone changes it. db
writes, and the change is scoped to your organisation, checked against the Table's policy and
recorded in its History. When several writes must succeed together, a server function runs them
in one transaction.
import { useLive, db, Link } from "@ezship/react";
import Badge from "global/Badge";
export default function Defects() {
const open = useLive("defects", {
where: { status: "open" },
order: ["-created_at"],
});
const total = useLive.count("defects");
return (
<section>
<h1>{open.length} open of {total}</h1>
{open.map((d) => (
<Link key={d.id} to={`/defects/${d.id}`}>
{d.part} <Badge>{d.severity}</Badge>
</Link>
))}
</section>
);
}import { serverFunction, z } from "@ezship/react/server";
export default serverFunction(
z.object({ batch: z.string() }),
async ({ db }, { batch }) => {
const left = await db.aggregate("defects", {
where: { batch, status: "open" } });
if (left.rows[0].count) throw new Error("open defects");
return db.update("batches", batch, { closed: true });
});Made for coding agents
A Site cannot call fetch, touch the DOM, use storage or install packages. That sounds
limiting until an agent is writing the code. The platform enforces the Rules on every build, so
what an agent ships is reviewable, predictable and hard to get wrong.
Everything anyone does to a Site is an ez command. The CLI, the browser studio and
its built-in agent all run the same commands, so an agent can do anything a person can do and
nothing a person can't.
ez help is a complete, current brief for an agent. ez clone adds an
AGENTS.md that points to it, so Claude Code, Codex or Cursor knows the shape, the
Rules and the database before it writes a line.
Every Site and the Global Workspace carry a required CONTEXT.md that records the
app's purpose, audience, workflows and decisions. The next agent or colleague starts from what
the last one learned.
Or stay in the browser
Not everyone lives in a terminal. At studio.ezship.dev, Builders get an editor, a live preview and an agent in one window, working on the same Sites and the same Versions as the CLI. Start an app in the studio and finish it in your editor, or the other way round.
One App Database per organisation
Internal tools rarely stand alone. The receiving app and the inventory app need the same parts table. In ezship, every Site in your Instance shares its Tables, its people and its components, so the tenth app is quicker to build than the first.
Every insert, update and delete is recorded, with who made it, when and from which build. You can query who changed something and what it looked like last Tuesday, without building an audit log.
You declare Tables once in schema.sql. Changes are additive and applied atomically
with each deploy, so one app can never break another by dropping a column.
Engine-enforced unique indexes and per-Table sequence numbers, so invoices and ticket numbers never collide, whoever writes them.
The Global Workspace holds your theme, shared components, constants and an optional Shell for branding. Each app picks them up on its next deploy.
Security and tenancy
These tools hold real operational data. ezship treats every Site as sensitive from day one.
ezship is onboarding organisations by invitation. Tell us what you want to build and we'll set up your Instance.