PrettyFly.ai· AI ops
Case study

Internal Operating System

Ongoing
← All case studies

Workflow receipt · prettyfly os

PrettyFly OS gives internal agent work one operating surface.

PrettyFly needed a way to see agent state, cost, failure, and handoff without chasing logs across servers.

PrettyFly.aiPrettyFly OScoded proof surface · future motion slot
No. 02

Inspectable proof

Proof video
prettyfly.ai / prettyfly-osPrettyFly OS
No. 03

Original drag

Drag named first

Original drag

The work was distributed, but the operating state was not.

Agents were running across servers, but health, cost, tasks, and handoffs were split across logs and local state. The system needed one operating surface before more agent work could be trusted.

  1. 01

    Agent health lived outside a shared operating view.

  2. 02

    Failures could hide until someone checked the wrong place.

  3. 03

    Cost controls were separate from the work being done.

  4. 04

    Task handoffs had no common surface.

No. 04

Operating route

Mapped path

Operating Route

A PrettyFly OS route for agent work: observe, budget, trip, trace, hand off.

PrettyFly built an internal operating surface with fleet state, real-time events, circuit breakers, cost visibility, tracing, and MCP tools for development sessions.

01

Fleet state

Seven agents report into a shared view with real-time event streaming.

02

Circuit breakers

Repeated faults trip the route and make recovery explicit.

03

Cost readout

Per-agent spend, daily budgets, tracing, and monthly reports sit beside the work state.

04

18 MCP Tools

Observability and task tools are exposed directly to development sessions.

05

Small runtime

A raw Node.js HTTP server keeps the coordination layer inspectable.

06

Two auth modes

Supabase JWT handles dashboard access; bearer tokens handle machine communication.

No. 05

Shipped system

Receipt

Shipped System

A live PrettyFly OS surface for internal agent operations.

7Agents Running 24/7
$50Monthly Cost
18MCP Tools
0NPM Dependencies
Stack
Node.jsPostgreSQLLangfuseSSEsystemdSupabase Auth

Your route

Bring the workflow before the build.

Name one route that feels expensive. The diagnostic reads the drag, owner, risk, and next move before anyone recommends a build.