← Back to OvernightUse case · Forward-deployed

Ship custom experiences to every customer.

Forward-deployed teams build a bespoke experience per customer. Overnight is the vehicle: each one gets its own isolated runtime and the audit trail your customer’s security team will ask for.

the finished drawing — one boundary under every customer
01 isolate, deploy, prove

A bespoke build per customer. One boundary under all of them.

Every customer gets a runtime of its own, an app built for them, and a record of every change and outside call it made, sealed and ready for their auditor.

When their security team asks what ran, what it touched, and under which identity, the answer is already written. You export it and hand it over.

acme · manage / audit traillogging
apprefund-deskidentityj.okafor · supportevents0
timecallagainstdecision
09:41:02identityj.okafor · company SSOallow
09:41:02POST /refunds201 · order A-40913allow
09:41:03api.stripe.comoutbound · on the allowed listallow
09:41:03smtp.sendgrid.netnot on the allowed listdenied
09:41:04archivehourly · chained · lockedallow
✕ deniedThe app tried to reach an email service that isn’t on its allowed list, so the connection was refused — and the refusal is in the record too.
export evidenceidentityapprovalsaudit logone export answers the question your auditor opens with
what ran, who ran it, and what it was refused
  1. 01isolate

    Every customer runs in its own isolated runtime

    Every app has its own database, and each customer’s apps run sandboxed and walled off, so one customer’s app can never reach another’s data.

    The network edge in front of each runtime is shared infrastructure across customers today. Customer data is not.

    How isolation works →
  2. 02deploy

    A bespoke build per customer, no new infrastructure

    Build the custom experience each customer needs with the AI tools your team already uses. The Refinery makes each one production-grade, and each runs inside the same approved boundary.

    You don’t build the infrastructure for each one. The boundary under every customer is the same one, approved once.

  3. 03domains

    Each workspace can have its own domain

    Give each customer’s workspace its own domain, so the app they use lives on their name rather than yours.

  4. 04prove

    Export the audit trail for their auditor

    Every identity check, settings change and approval is logged, along with every action that changes data and every call the app makes to the outside world, each under the identity behind it. The trail is written as it happens, sealed, and one export away when your customer’s security team asks for it.

    What an auditor gets →
  5. 05what it costs

    Enterprise, quoted to your workload

    Enterprise is for companies shipping to their customers. It is annual, scoped to your organization, with up to $250,000 a year of runtime included, an isolated cluster, and pre-load credits, all quoted to the workload.

    See pricing →
· sign up
Let’s build it

One boundary under every customer.

Tell us what you ship to your customers and what they need to see. We will scope it from there.

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.