Tessera Serve
PX-05
North Star
One window owns the whole journey.
Detect, run, expose, observe, ship. Every competing tool owns a single stage of that chain — a deploy platform, a tunnel service, a self-hosting panel — and leaves you to stitch the rest together yourself.
One window owns the whole journey. Every competing tool owns a single stage of it — Vercel deploys, a tunnel service exposes, a self-hoster runs. The chain below is the product.
01
Detect
14 project types · templates or any folder
Point it at a directory. It works out what the project is, finds how to start it, and loads the app's own .env without being told.
02
Run
Supervised process · auto-restart
The app comes up on a port with PID tracking, graceful shutdown and a restart with a desktop notification if it falls over.
03
Expose
Tunnel · custom domain · TCP
A public URL immediately, or your own domain by CNAME. Password access and rate limits are applied at Serve's own reverse proxy, so a prototype with no auth code in it can still be shared safely.
04
Observe
Proxy analytics · inspector · logs
Traffic passes through the proxy, so the request counts, P95 and status-code mix are what clients actually experienced rather than what the app believes it served.
05
Ship
ECS · App Runner · Cloud Run · Azure · Docker Hub
Same window. It writes the Dockerfile when the project has none, runs a pre-deploy check first, then tracks what the running service costs.
Databases
Four engines — PostgreSQL, MySQL, Redis and MongoDB — provisioned as real Docker containers from one click, each handing back a connection string ready to paste into the app's .env.
On your machine
The apps, the proxy, the databases and the logs all run on your laptop. The free tier needs no account at all — there is nothing to sign up for before the first public URL.
What owning the whole chain buys you
Protection without writing auth
Password access and rate limits are applied at Serve's own proxy, so a prototype with no auth code in it can still be handed to a client safely.
Numbers a client experienced
Analytics are recorded at the proxy rather than inside the app, so the request count and P95 are what actually reached the browser.
A real database in one click
Four engines as real Docker containers, each returning a connection string ready to paste into the app's .env — no Docker config to write.
One place when it gets real
The same window that started the app writes the Dockerfile, checks prerequisites, deploys it and then tracks what the running service costs.
The specification.
Platforms
macOS · Windows
Templates
React · Next.js · Express · Flask · Vue · SvelteKit
Exposure
Public tunnels · custom domains · TCP
Cloud
AWS ECS · App Runner · Cloud Run · Azure · Docker Hub
Protection
Password access · rate limiting