Operational infrastructure / for small teams

You wrote the programs.
Now put them to work.

Fat Controller turns scripts, services, watchers, and automations into real operational processes — running across the machines you already have, observable and coordinated for your whole team.

Run anywhere. See everything. Keep it moving.

Start free See how it works
Live All systems operational
Windows compute Online
macOS compute Online
Linux & cloud compute Direction
Team operators Active
Engineer product assistant Online
Inbox / Alerts notifications Live
≪

Fat Controller

control plane

●morning.reconciliation running across 3 nodes
●customer.import completed on macOS

One control plane. Everywhere work gets done.

A script is not an operation.

A useful program still depends on its author remembering to run it, watching it while it runs, knowing where it lives, interpreting its failures, and telling everyone else what happened. That's automation that still needs an operator standing next to it.

Fat Controller changes that.

  • A program should run at 5:00 AM whether its author is awake or not.
  • A watcher should keep watching.
  • A reconciliation should trigger what comes after it.
  • A failure should become visible — not silent.
02

The program runs where the program belongs.

Maybe that's a Windows workstation with the network access nobody else has. Maybe it's a Mac mini quietly running overnight. Maybe it's a server sitting in a closet that happens to hold the one credential the job needs. Fat Controller coordinates the operation without forcing the workload to move somewhere unnatural.

Windowsverified
macOSverified
Linuxdirection
Cloud / edgedirection
03

Know what is happening while it is happening.

Running, completed, failed, waiting. Every machine online or off. Every job's history, one place — the lights come on in an operation that used to be invisible.

04

The firepower of a technology department. Without the department.

Small teams are powerful because the people doing the work stay close to the work. Fat Controller gives them the operational capability that's usually scattered across a scheduler, a monitoring tool, a secrets manager, and a deployment system built by someone else's platform team — without turning the team into that platform team.

What's real today

  • Organizations and role-based access
  • Shared, org-owned jobs
  • A live machine registry
  • Org-owned secrets, not per-machine env vars
  • Shared operational visibility
  • Run history across the whole team

Who's on the grid

People

Stay in control. Decide what runs, get told when it matters.

Programs

Do the repeatable work, reliably, without someone standing over them.

Agents

Participate alongside the team — another operator on the grid, not a separate system.

05

An engineer who understands how Fat Controller works.

The long-term idea: describe an operation in plain terms and have the Engineer help turn your programs, schedules, and machines into something coherent.

“Run this after the files arrive. Don't publish the report unless reconciliation passes. If it fails twice, alert Sarah and keep the downstream job stopped.”
Today

A real, repository-grounded product assistant — explains how Fat Controller works, walks through configuration, troubleshoots what you're seeing.

Direction

Increasingly helping operate the grid itself — reasoning about jobs, dependencies, and state, not just answering questions about them.

Principles

  1. Run where the work belongs.
  2. Make state visible.
  3. Automate incrementally.
  4. Keep humans in control.

Underneath, Fat Controller coordinates through Vesper — Calapi's shared communications fabric. You'll never need to think about it to run your operation.

Serious machinery. A little personality.

Personality Packs

Once the operation is running, the control room can wear a different face. The portrait, the voice, the daily quote — the machinery underneath doesn't change.

Winston Churchill Personality Pack hero poster

Winston Churchill

Steady under pressure.

churchill / 1.1.0

Showing built-in catalog data.

Start with one program. Put it in motion.

You don't need to re-architect anything. Point Fat Controller at the one script you keep meaning to babysit, and stop babysitting it.

Start free See how it works