whale

Why whale

Four parts you keep renting. An edge you keep leaking. Whale keeps both in your folder.

You’ve been buying the same
software over and over.

Under the hood, every business app is the same four parts — records, actions, rules, views — with a different name on the box. Whale is those four parts, once.

All four parts — once, in your words. One program, no monthly bills, yours. Six subscriptions become one folder.

harness / four parts one declaration
01 · records

What is true

Products, people, orders, money, files — declared once.

Products 231 Customers 4,820 Orders 18,449 Locations 3
02 · actions

What can happen

Every change is a typed command through the same door.

place orderreceive stockissue refundsend campaignprint receiptadvance work
03 · rules

What is allowed

Your policies decide what runs, waits, or never happens.

Oversellblocked
Refund > $100human
Daily closeautomatic
04 · views

What people see

Every surface reads the same live record; nothing drifts.

once · in your words · on your hardwareno duplicate truth

Your edge is leaving the building.

Every prompt, file, and customer list you feed a rented AI leaves your walls — on their terms, not yours. The parts of your business nobody could copy become somebody else's data. And you pay for it, by the token.

Whale keeps the record in your folder. The AI sees only what the door allows — and it can run entirely on your own hardware. Your data never leaves and never trains someone else's model.

network / data boundary measured
rented ai

Your edge leaves.

Prompts, files, customer context, and policy cross the boundary.

your businessprovider cloudshared model
customer_context.json left building pricing_rules.yaml left building
whale cell

Your edge compounds.

The model comes to the record. The record never goes to the model.

your businesslocal cell
record + rules local model training never
your premisesegress 0 B
get whale — one command