← Back to OvernightUse case · SaaS replacement

Kill your back-office SaaS bill.

Build the tools you are renting and run them on Overnight. Your second app inherits the boundary, so it skips a second review, and when you publish to other teams the boundary goes with it.

the site plan — one boundary, however many tools stand inside it
01 land, expand, graduate

Every tool you build is one you stop renting.

What changes on the invoice is the second-order effect. The licence you were renewing is replaced by runtime you are metered on, inside a boundary security approved once.

Start with the tool your own team needs. The second one skips the review, and the third goes to the team next door with the boundary attached.

acme · manage / spendannual
staysyou rebuildconforming to it1,000 people · 87 apps
athe stack$6.0M of licences
$1M100k10k100%log40 apps = 79%34 systems of record · $4.3M53 you rebuild · $1.7M
bthe swap2 hrs/person/wk × $65
$10M$5M0renew everything · $12.0M−$4.1M / yr$7.9M−34%m0m12m24
87apps in the stack
$12.0Ma year, all in
2 hrsa week, per person
53 / 87apps rebuilt
$4.1Msaved a year
−34%of the true cost
illustrative — the shape of the change, not a quote
  1. 01the rent

    Build the tools you are renting

    Every workplace runs on software someone else designed, priced by the seat, and renewed whether or not it fits. Build the tool that matches your process, run it in your own tenant, and stop renewing the license.

    The tool that fits has always been buildable. It was just never worth the quarter it would take. When a team can build it in an afternoon and the Refinery takes it to production, that math stops holding.

  2. 02land

    Build for yourself first

    The first app is the one your own team has been asking for. It runs in a tenant with the controls auditors look for from the first minute, so the value lands in the first session, with no vendor call, pilot, or procurement cycle in the way.

  3. 03expand

    Your second app skips a second review

    The second app arrives inside the same approved runtime, with the same identity, isolation, and logging. Security reviews one thing, once, no matter how many apps follow.

    What that review covers →
  4. 04graduate

    Publish to other teams, and the boundary goes with it

    When something works, hand it to another team. The boundary travels with it, so the people receiving it skip the 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.

  5. 05what it costs

    Pay for who builds, not for everyone who uses it

    The Business plan is $40 per creator a month, minimum two creators, with up to $2,500 a month of runtime included. The people who use what you publish are add-on users at $10 a month each. Pre-load credits at 20% off with no minimum.

    Billed annually, seats are $33.33 a month with two months free, add-on users are $8.33, and up to $25,000 of runtime is included for the year.

    See pricing →
· sign up
Let’s build it

Stop renewing. Start owning.

Bring the tool your team has been asking for, and every one after it lands inside the same approval.

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.