All Docs
FeaturesSaaS FactoryUpdated March 12, 2026

Blog: Enterprise-Grade Fleet Management Has Arrived in SaaS Factory

Enterprise-Grade Fleet Management Has Arrived in SaaS Factory

Released in v1.0.163

From day one, SaaS Factory's promise has been simple: every great idea deserves a company that never stops getting better. For a long time, that meant taking a single product idea and autonomously building, shipping, and growing it — end to end, no humans required.

But great companies rarely stay simple. They grow into platforms. A web app spawns a mobile client. The mobile client needs a dedicated API tier. The API tier surfaces an admin dashboard. Suddenly you have four interconnected codebases that all need to change in lock-step — and the agents running them need to know it.

Today's release fixes that.

The Problem with One-at-a-Time

SaaS Factory previously managed products in isolation. Each project had its own autonomous pipeline — its own feature queue, its own releases, its own agents. That's powerful for a single product, but it breaks down fast for product suites.

Consider an enterprise team running four products that share a common design system and an API client library. Before v1.0.163:

  • Agents were dependency-blind. When the API team shipped a breaking change, the web app agents had no idea until CI blew up.
  • Releases were uncoordinated. The mobile app could ship before the API it depended on was ready.
  • Shared libraries drifted. Different products pinned different versions of the same package with no central view of the divergence.
  • monorepoConfig existed but did nothing. The schema column was there — populated by some customers — and silently ignored.

For small teams building a single SaaS product, this was fine. For enterprise customers building interconnected platforms, it was a blocker.

Fleet Management: What It Is

Fleet Management is a coordinated orchestration layer that groups related projects into a Fleet — a first-class entity in SaaS Factory with its own dashboard, dependency graph, release calendar, and shared library registry.

A Live Dependency Graph

The moment you tag two or more projects with the same fleetId in their config, SaaS Factory builds a live dependency graph. Every product is a node. Every shared library or service dependency is a directed edge. At a glance you can see:

  • Which products will break if library X gets a major bump.
  • Which release needs to go first.
  • Where version drift has already crept in.

This graph isn't a static diagram that goes stale. It updates automatically as agents merge PRs and versions change.

Agents That Actually Understand Context

The AI Architect agent and the Beast Mode supercycle now read monorepoConfig at planning time. Before generating a feature decomposition or planning a refactor, the agent asks: who else depends on the interface I'm about to change?

If the answer is "three other products in your fleet," the plan widens to include coordinated changes across all three — rather than discovering the incompatibility at 2am when a downstream CI run fails.

Coordinated Release Scheduling

The Fleet Release Calendar enforces dependency ordering across products. When a producer project cuts a release, the pipeline automatically:

  1. Identifies every downstream consumer.
  2. Opens compatibility-check PRs in each consumer.
  3. Stages their releases in dependency order.
  4. Pauses and alerts if any compatibility check fails.

No human has to manually sequence deploys or cross-reference Jira boards to figure out what needs to ship first.

Shared Library Registry

Every shared package your fleet uses gets a row in the Shared Library Registry: current version, all consumers, any version drift, and a direct link to the changelog. When the producing project bumps a version, the agents open coordinated bump PRs in every consumer automatically — labelled fleet-sync and cross-linked so reviewers have full traceability.

Who This Is For

If you're building a single SaaS product, today's release doesn't change your day-to-day. SaaS Factory continues to work exactly as before — just smarter under the hood.

If you're an enterprise customer running a product suite, Fleet Management is the feature you've been waiting for. It brings the same autonomous, always-on engineering capability to large-scale, long-lived, interconnected codebases — the kind of complexity that until now required dedicated platform engineering teams just to keep things from falling apart.

This is genuinely enterprise-tier capability that no vibe-coding competitor currently offers. And because it's built into the factory itself, every improvement to Fleet Management automatically benefits every product suite running on the platform.

Getting Started

Fleet Management is available starting in v1.0.163. To set up your first fleet:

  1. Open Project Settings → Fleet Config on each product in your suite.
  2. Add a shared fleetId and configure sharedLibraries and dependsOn relationships.
  3. Head to Development → Fleets in the sidebar — your fleet will appear automatically.
  4. Review the dependency graph, set release ordering in the Fleet Release Calendar, and let the agents take it from there.

Full configuration reference and setup guide: Fleet Management Documentation.