← Back to OvernightHow it works

Bring it. Refine it. Run it.

Upload the project or point your IDE at Overnight. The Refinery makes it production-grade, and the Runtime runs it inside a boundary security approved once, locked to the version you approved and logged as it runs.

the site plan — one boundary, however many apps stand inside it
01 the path

One tenant. However many apps.

The first app deploys while you watch it come up. The second one skips all of that: same tenant, same identity, same trail, and a security review that already happened.

Every app takes the same three steps. It comes from whatever tool built it, the Refinery makes it production-grade, and the Runtime runs it inside a boundary that carried the controls before the first line was written.

By the third, the interesting question has moved from whether you can run this to which team gets it next.

acme · workspacetenant
tenantacme.onrt.aiapproved once
RDrefund-deskby support deploying ready

Look up a customer, refund an order, leave a trail.

  1. Waiting for environment
  2. Applying configuration
  3. Starting up
  4. Routing
open refund-desk ↗
IRinvoice-reconby finance ready

Match statements against invoices every morning.

inherited the boundary · no second security review
open invoice-recon ↗
OTonboarding-trackerby people ops ready

Every new hire's first fortnight, in one place.

published to 3 teams · the boundary travelled with it
open onboarding-tracker ↗
1 apps1 tenant1 approvalthe same identity, isolation and audit trail under all of them
one approved boundary, however many apps stand inside it
  1. 0101 · bring

    Bring it from wherever you built it

    Upload the project, or point your IDE at Overnight. Claude Code, Cursor, Codex or any other generator will do, so your team keeps the model and the workflow it already likes.

    Overnight deliberately is not trying to be your code generator. Generation is cheap and getting cheaper. What it gets you is an app that works on your machine, which is where most AI-built software stops.

  2. 0202 · refine

    The Refinery hardens it for production

    A swarm of agents makes a production pass over the project. Hard-coded secrets move to vault references, the files the app saves are kept safe through restarts and updates, and the identity and data planes get wired up.

    It also drafts the gate that decides what the app may call, for you to confirm. That is the prompt-after-prompt slog of hardening, done in one pass instead of weeks, with no Dockerfile to write.

    How the Refinery works →
  3. 0303 · run

    The Runtime runs it inside the boundary

    You confirm who can use the app and what it can reach, and approve it. Then the Runtime runs exactly the version you approved, in isolation, and logs every call. Nothing else can go live in its place.

    Every call the app makes takes one mediated path, and anything you did not explicitly allow is denied by default, including everything nobody thought to write a rule about.

    How the Runtime enforces it →
  4. 04the second app

    Everything after the first arrives already inside

    The second app lands in the same approved runtime, carrying the identity, isolation, and logging your security team already signed off on. There is no second setup and no second exception to request.

    By the third, the interesting question has moved from whether you can run this to which team gets it next.

  5. 05what security reviews

    They review the boundary, once, and then stop

    The controls live on the runtime, so what your security team examines is one boundary with one set of properties, rather than one application at a time forever. The tenth app rides on the same approval as the first.

    That is the whole trade. You give up the ability to make each app special, and you get back the ability to ship any of them without an argument.

    What that review covers →
  6. 06publish

    Hand a tool to another team when it earns its keep

    When something works, the team next door can have it. The boundary travels with it, so the people receiving it skip the procurement and the security review you already passed.

    Everything stays inside the tenant your company owns. What moves is who uses the tool. Where it runs stays exactly where it was.

· sign up
Let’s build it

Close the gap between generated and production.

Sign up, upload your apps, and we will schedule a follow-up to walk through what Overnight made of them.

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.