Coming soon · still building it

Build a web app to fit your business.

I’ve had this domain name for 20 years, finally the time is right. 8)

— Jason (aka lecstor)
Get a note when it’s ready.
One email when it’s ready. No newsletter.

What it is

My take on a website builder — designed for more than the basic site. It’s for anyone who wants a web presence shaped to their business, without the overhead of building an app from scratch. I’m building it for myself, and people like me.


How it works · three pieces
01

Every change is saved.

Your app keeps a full history. Roll back to an earlier version any time. Two people editing at once can’t silently overwrite each other.

02

Built by chat.

Chat in the studio. Or point Claude Code, Cursor, or your own agent at the MCP server — same tools either way, same audit trail, same safety rails.

03

Yours alone.

Your app has its own database — nothing pooled, nothing shared. Bring a custom domain or use a subdomain. Customer sign-in when you need it.


Made for · independent operators

Independent operators, mostly.

The point is your app fits your business, not the other way around. A few common shapes:

Recipe · 01

Small business site

Hours, services, contact. The basics, done right.

Recipe · 02

Product range or menu

List what you sell — items, dishes, services — without spinning up a full store.

Recipe · 03

Blog

Posts, tags, RSS feed. The web’s oldest pattern, still the best.

Recipe · 04

Portfolio

Show your work. Suits trades, consultants, photographers, makers.

Recipe · 05

Bookings & enquiries

Take requests through a form, straight to your inbox.

Recipe · 06

Members area

A private corner for staff, paying customers, or course material.


Editor, with build rights

Hand the keys to your AI.

An MCP server is the front door. Claude Code, Claude Desktop, Cursor — anything that speaks MCP gets the same tool layer the embedded chat uses: operation verbs, draft branches, a publish gate. What your AI works with is a small typed tree, not a wall of generated code.


Where we are
Phase 1
Skeleton
TanStack Start on Workers. The renderer. The DB schemas. Apex wired.
in progress
Phase 2
Authoring
The catalog. Immutable-row versioning. The studio’s first real surface.
next
Phase 3
Runtime data
Forms, product lists, media, end-user auth — the bones of a published app.
soon
Phase 4
Public beta
Sign-up. Billing. Custom domains. Open the gate. Phases shift, give or take.
later
© 2026 EzyApp · ezyapp.com