For warehouses, labs, production lines and kitchens

Describe how your operation works. Get the app that tracks it.

ezship is where operations teams build their own tracking apps with AI. Explain a process in plain words, and an agent builds a precise, working app on one shared database that your whole team signs in to. You don't need developers, and you don't need the spreadsheet only one person understands.

No card needed. Sign up with your email and start building in minutes.

What you can build

If you track it on a clipboard today, you can build it this afternoon.

ezship is made for operational record-keeping: the logs, queues, checklists and boards that keep a physical business running. Some of the apps teams start with:

Warehouse & distribution

  • Receiving and put-away log
  • Cycle counts and discrepancies
  • Pick, pack and ship board
  • Returns and damage reports

Labs

  • Sample intake and chain of custody
  • Equipment calibration schedule
  • Reagent and consumables inventory
  • Test requests and results

Manufacturing

  • Defect and non-conformance log
  • Downtime and maintenance tracker
  • Batch and traveler records
  • Shift handover notes

Restaurants & food service

  • Temperature and food safety logs
  • Prep lists and par levels
  • Waste tracking
  • Supplier orders across locations

Plus inspections, work orders, asset tracking, training records, IT requests and approvals: anything with people, records and a process.

Sound familiar?

Your operation already has a system. It's spread across forty spreadsheets.

The clipboard by the dock

Someone types it up at the end of the shift, if they remember. When something goes wrong, the record you need is in a binder.

The spreadsheet nobody else touches

It works because one person knows which tabs not to break. Ten people edit copies, and nobody is sure which one is current.

The software that almost fits

The big system covers most of the job, but changing a single field takes a vendor ticket or a six-month IT project. So the workarounds pile up around it.

ezship replaces those gaps with small, connected apps that the people who run the process can build and change themselves.

How it works

From a conversation to an app on the floor.

You describe the work. The agent builds it. You try it on real records and ask for changes until it's right, and then you publish it to your team.

  1. 1

    Describe the process

    Tell the agent who does what, what gets recorded and what should raise a flag. Paste in the columns from the spreadsheet you use today. Plain language is enough.

  2. 2

    Try it on real work

    A live preview runs against your actual data. Click through it, then ask for what's missing: "make temperature required", "add a photo", "show me only my shift".

  3. 3

    Publish to your team

    One click puts it live. Invite people by email. They sign in from the tablet on the line, the phone on the floor or the desktop in the office.

  4. 4

    Keep improving it

    Processes change, and now your app can change with them. Every save is a version with a name and a time on it, and a failed update never takes the running app down.

The studio

An app builder that talks back, and asks before it acts.

Everything happens in one browser window at studio.ezship.dev: the agent, the app it's building, and the data behind it.

  • Agent. It builds new apps and edits existing ones from a conversation.
  • Live preview. See every change on your real records before anyone else does.
  • Data view. Browse, filter and correct records in a familiar grid.
  • Approvals. The agent stops and asks before it publishes, changes data or adds files.
  • Versions. Every save records who made it and when.
  • Code, if you want it. Every line is there to read, edit or hand to a developer.

Why ezship

AI is good at building software. It's precise inside a framework.

A general-purpose AI coding tool can make anything, and that's the problem. Each app comes out different, with its own database, its own login and its own surprises. ezship gives the agent a framework built for one job, operational record-keeping, and holds every app to it. The result is apps you can trust with the records your business runs on.

One shape for every app

Every app is built the same way, from the same parts. The tenth app is as dependable as the first, and anyone, person or agent, can pick up where the last one left off.

Checked before it goes live

The framework's rules, a type check and a full build run on every publish. If anything fails, the running app stays exactly as it was.

Data made for operations

Live tables, lot and ticket numbers that never collide, photo and document attachments, and updates that succeed or fail together. These come built in, so they're never improvised.

Security isn't the AI's job

Sign-in, roles and access control belong to the platform, not to code an agent wrote. Every app gets them, and none of them can get them wrong.

No hidden connections

Apps can't reach out to the internet, install add-ons or store data anywhere else. What the agent builds is what you see.

It remembers why

Each app keeps a written record of its purpose, its users and the decisions behind it, so the next change starts from what the last one learned.

One operation, one source of truth

Small apps that add up to a system.

Each app does one job well, but they all share one database, one set of people and one look. The receiving log and the inventory board read the same lots. Quality sees what production logged a minute ago. Because everything you've already built is there to reuse, each new app comes together faster than the last.

For the person who gets asked for the numbers

Clean data, by design.

Data from scattered spreadsheets has to be cleaned before you can use it. ezship keeps records structured from the moment they're entered, in one place, with the full story behind every change.

  • History on every table. Every change records who made it, when and from which app. You can see what a batch looked like last Tuesday without building an audit log.
  • Query across every app. Run SQL across the whole operation, from receiving through shipping, in one database.
  • Live counts and totals. Dashboards update the moment someone on the floor saves a record.
  • A structure that only grows. Tables gain fields, but they're never dropped out from under you, so a report doesn't break because someone changed an app.

Ready for your IT team

Starts with one process. Built to run the whole site.

These apps hold real operational records, so ezship treats every one as sensitive from day one, whether it's one team's checklist or a hundred people across three shifts.

  • Invite-only, everywhere. Nobody signs up to your apps from a link. People are there because someone invited them.
  • Every app requires sign-in. Nothing is public, not even a preview. Admins can limit an app to named people.
  • Clear roles. Admins manage access, Builders make apps and Members use them. Every action lands in the audit log.
  • Your own private address. Your organization gets its own address and its own database, isolated at the database engine from every other customer.
  • Nothing silently lost. Apps are archived, not deleted. Saves keep their versions, and databases are backed up with encryption.
  • Any device with a browser. Tablets, phones, shared floor terminals and desktops all work, with nothing to install or update.

Got developers?

They'll like it too.

The apps your team builds in the studio are plain React and TypeScript. Developers can open the same apps from a terminal with the ez command, keep them in git, and work with Claude Code, Codex or Cursor. The rules and checks are the same either way, so ops and engineering can share the work without stepping on each other.

Pick one process. Have an app for it by the end of the day.

Start with the clipboard that bothers you most. The free trial includes your own private ezship and $5 of AI credit to build with.