← Back to OvernightUse case · Individual

Your vibe-coded apps deserve a real home.

Host them safely without running any infrastructure. Upload the project, approve it, and get a live URL. The Refinery hardens it, and it runs inside the same boundary whether it is for you or your team.

the keep — your app, inside walls you never had to build
01 from laptop to live url

It works on your machine. Now it works everywhere.

Overnight gives each of your apps a tenant with the controls auditors look for, before you open the editor, so it runs on real data from the first session.

Build the tool with the AI you already use, and upload it. The Refinery does the production pass, and the Runtime keeps it running inside a boundary you never had to build.

overnight · publish / refund-desklive
✳publish · refund-desk
1
step one · upload
Bring the app you built
upload
uploadrefund-desk.zipreplace
2
refinery
step two · refinery
Fixed up, built and tested
Four agents patch the app side by side, then Overnight builds it and tests it.
4 agentsside by side
identity ✓data ✓routing ✓network ✓
building and testing…
refinery4 of 4 patched · testeddiff
3
settings
step three · your settings
Who can use it, what it can reach
▢refund-desk
your settings · 13 allowed
Support teamcan open the app
allow
Everyone elseturned away at the identity check
block
api.stripe.comrefunds go through Stripe
allow
Postgres databasekeeps orders and refunds
allow
smtp.sendgrid.netnobody asked for email
block
settingssupport team · 2 servicesedit
4
approve
last step
Approve it, and it goes live
version 1refund-desk · testedidentity: company SSO, support team onlyreaches: api.stripe.com, its own databaseeverything else: denied
approve & deploylive at its own link, inside the boundary
from upload to live, with you approving before it runs
  1. 01a live url

    Upload the project, approve it, and get a live URL

    You have apps for your own work and your own life that live on a laptop. Upload the project, or point your IDE at Overnight, and once you approve it, each one gets a live URL. Claude Code, Cursor, Codex or any other generator will do.

    There is no server to rent, no cluster to stand up, and no platform to learn before the first app is running.

  2. 02no ops

    No Dockerfile to write, no ops to run

    The Overnight Refinery moves secrets out of the source, keeps the files your app saves safe through every update, and wires up the identity and data planes. That is the production plumbing your IDE skips, done for you.

    Overnight builds and runs the container and keeps the software underneath it up to date. Each update arrives as a new version of your app, ready for you to approve, so packaging is never something you own.

    What the Refinery does →
  3. 03real data

    Protected before you open the editor

    Each app runs in a tenant that carried the controls before the first line was written, so it can hold real data from the first session.

    Every call your app makes takes one mediated path, and it gets logged on the way through. Only the version you approved can go live, so nothing changes underneath you.

    How the Runtime enforces it →
  4. 04one boundary

    The same boundary, for you or your team

    An app you built for yourself runs inside the same boundary as one a whole company relies on. When someone else wants to use it, nothing about where or how it runs has to change.

  5. 05what it costs

    $40 a month, with runtime included

    The Individual plan is one creator seat at $40 a month, with $20 a month of runtime included. Pre-load credits at 20% off with no minimum. Billed annually it is $33.33 a month, two months free.

    See pricing →
· sign up
Let’s build it

From laptop to live URL.

Sign up, upload your apps, and they run inside the boundary from the first session.

Get started

Sign up

Tell us a little about what you have built and we will get you set up.

We use this to connect with you, and for nothing else. No recurring marketing emails.