RD refund-deskby support deploying ready
Look up a customer, refund an order, leave a trail.
- Waiting for environment
- Applying configuration
- Starting up
- Routing
open refund-desk ↗
← Back to Overnight How teams use it
Start with yourself.
Someone needs a tool on Monday. They build it with the AI they already use, and it runs on real data by lunch, inside a tenant that was compliant before anyone opened the editor.
Land/Expand/Graduate/One approval, every app/
One tenant. However many apps.
The first app deploys while your team watches it come up. The second one skips all of that: same tenant, same identity, same trail, and a security review that already happened.
Teams adopt Overnight by building for themselves first, on real data, inside a tenant that carried the controls before the first line was written. Every app after that inherits the approval the first one earned.
By the third, the interesting question has moved from whether you can run this to which team gets it next.
tenantacme.onrt.ai approved once
IR invoice-reconby finance ready
Match statements against invoices every morning.
inherited the boundary · no second security review
open invoice-recon ↗
OT onboarding-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 apps 1 tenant 1 approval the same identity, isolation and audit trail under all of them
- 01 the first app
Build for yourself, on Monday
The first app is the one your own team has been asking for and never got funded. Someone builds it with the AI they already use, and it runs on real data by lunch, inside a tenant that was compliant before anyone opened the editor.
Nothing to procure and nothing to stand up, so the value lands in the first session, before anyone has booked a follow-up meeting about it.
- 02 what teams build
Three kinds of software, and none is a prerequisite
Scripts, backends, and data plumbing are the fastest thing to land and the smallest thing to justify. They are also where deny-by-default earns its keep, because a quick data job is exactly where someone would otherwise paste a production credential into a file.
Internal tooling is the tool that never got funded, and SaaS replacements are the workflow you have been renting at a fit you never quite got. Teams start wherever their pain is. None of these is a level you unlock by finishing the one before it.
- 03 the 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.
- 04 what 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 → - 05 no procurement
The quarter you would have lost to a vendor cycle
A tool your team needs on Monday normally means a vendor call, a pilot, a security questionnaire, and a renewal you inherit for three years. Most of that process exists to answer one question: can this thing be trusted with our data?
Overnight answers it once, at the boundary, so the tools you build afterward skip the queue entirely.
- 06 publish
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 one tenant your company owns. What moves is who uses the tool. Where it runs stays exactly where it was.
Let’s build it
Start with one tool. Let it spread.
Bring the AI you already use, build for your own team first, and grow into the platform on your own timeline.