Your web apps
Your app runs where its data lives.
Lathe runs your app for you on the dedicated machine that already runs its databases: a container image of yours, in any language, pulled from your registry, served over https on a name of its own and on your domains, with every engine's connection string already in its environment. A deploy starts the new version beside the old one and moves traffic once it answers. It is in the plan price: nothing more for the app, its traffic or its domains. The machine runs images you have already built - not a build of its own, and not an autoscaler: a bigger app moves you to a bigger plan, not to more instances.
What you get with Apps on Lathe.
- Any image
- Built for linux/amd64 from any base image, in any language. Three rules: listen on the port the machine sets, answer a health path, keep state under /data.
- Its databases, a loopback away
- DATABASE_URL, REDIS_URL and the rest arrive in the app's environment with their passwords, before your own variables. Nothing to copy.
- Deploys that cannot take you down
- The new container starts beside the running one and takes traffic only after its health path answers. One that never answers is left out, with the old version still serving.
- From a GitHub push
- Connect a repository and the workflow that already builds your image; a green run deploys it. Or call the deploy endpoint from any CI. Lathe deploys itself this way.
- Your domain, its certificate
- Point an A record at the machine and add the hostname; the machine gets a certificate for it within a minute. Every public app has a name of its own from the start.
- Memory you set
- Each app takes its share of the engine's budget out of the plan's RAM, and automatic reallocation moves memory between the engines and the apps from what each holds.
- How it runs
- Your image, pulled by the machine from your registry and run in a container of its own with no privileges beyond the capabilities you name. The runtime is updated in the fixed weekly window (Sundays 03:00 UTC), announced in advance.
- On the same machine
- Postgres, Redis, CouchDB, NATS, Apps and Auth can run together on one dedicated instance; switch any of them on or off later, each with its own memory budget.
Address
https://db-7f3a-web.lathe.computer
A public app answers over https on a name of its own, and on every domain you add.
Good for
- The web app that fronts the database, on one bill
- APIs and workers that talk to Redis and NATS on the same machine
- Internal tools and admin panels beside the data they read
- A side project that needs a database, a domain and a place to run
Questions about Apps
Does hosting the app cost extra?
No. The apps engine is one of the engines in every plan: the app, its traffic and its domains are in the flat price.
How do I deploy?
Push a new build to the tag the app carries and press Deploy, call the deploy endpoint from CI, or connect the GitHub repository and let a green run of your workflow do it. Roll back by naming the previous tag.
Can I run more than one app?
Yes. Each has a name of its own, its own memory share and its own environment; apps on the same machine reach each other on loopback.
Is there a build step?
No. The machine pulls the image you built and runs no build of its own, so what runs is what you tested.
Also on Lathe: Postgres 17, Redis 8, CouchDB 3, NATS 2, Auth. See pricing, or the home page for the whole offer.
Apps beside your databases, from $15 a month.
Live about 90 seconds after checkout. Cancel any time; Mini starts with a 3-day free trial.
Start free - 3 days, no card needed