Operational layer for small teams
You wrote the programs.
Now put them to work.
Fat Controller turns the useful scripts, services, watchers, and automations you already have into work your team can run, see, and keep moving.
01 / the idea
Small teams can run serious operations.
Not with more dashboards. With one calm place to put the work in motion, see its state, and act when it matters.
02 / programs become operations
Useful code deserves a useful life.
Your software already does valuable work. Fat Controller gives it a schedule, a home, a clear state, and a place in the team’s shared picture.
Daily Pricing
A familiar process, now ready to run unattended.
Cash Reconciliation
Waiting for its next window, visible to the people who own it.
Market Data Ingest
Working from the machine with the right access.
03 / work stays put
The program runs where the program belongs.
Some work belongs on a Windows machine with installed software. Some belongs on a Mac with the right credentials. Fat Controller helps you use the machines you already trust instead of moving work for architectural theater.
04 / shared view
See the whole operation at a glance.
This is not a telemetry wall. It is a shared operational surface: a few recognisable states, the machines that can do the work, and enough context to know what comes next.
05 / the engineer
An engineer inside the operating environment.
The Engineer is a repo-grounded assistant for explaining, configuring, and troubleshooting Fat Controller. Over time, it is being designed to understand more of the live operation around it.
Direction, not a promise: deeper awareness of jobs, machines, schedules, dependencies, and state is in development.
Underneath, quietly
People, programs, and agents in the same operational picture.
Vesper provides shared coordination underneath. You do not need to learn a new abstraction to get useful work moving.
Fat Controller
Serious machinery.
A little personality.
Start with one program you are tired of babysitting.