All Docs
FeaturesSaaS FactoryUpdated March 12, 2026

Introducing the Public Agent Marketplace

Introducing the Public Agent Marketplace

Version: 1.0.160

SaaS Factory ships with 32+ specialized agents — researchers, architects, engineers, compliance officers, and more — all working autonomously to build and improve your product. Until now, every customization you made to those agents stayed locked inside your own project. The Public Agent Marketplace changes that.


What Is the Agent Marketplace?

The Agent Marketplace is a public registry where SaaS Factory users can share, discover, fork, and install three types of agent configurations:

Asset TypeWhat It Controls
Agent PersonasAn agent's name, role framing, tone, priorities, and behavioral constraints
Pinned SpecsCompliance rules, code quality standards, and architectural constraints that the AI architect and reviewers must follow
Pipeline Config BundlesNamed sets of pipeline toggle settings (e.g. "lean MVP mode", "compliance-heavy fintech", "open-source-ready")

Custom Discovery Agent Prompts — the instructions that steer what features the discovery agent proposes — can also be published as templates.


Core Workflows

Publishing a Configuration

  1. Navigate to Project Settings → Agents.
  2. Select the persona, pinned spec, or pipeline config you want to share.
  3. Click Publish to Marketplace.
  4. Add a title, description, and optional tags (e.g. fintech, b2b-saas, open-source).
  5. Choose a visibility: Public (discoverable by all) or Unlisted (accessible via direct link).

Published listings are versioned automatically. Every edit you save creates a new minor version; you can mark any version as the current stable release.


Browsing and Installing

  1. Open the Marketplace tab from the main sidebar.
  2. Search or filter by asset type, tag, or popularity.
  3. Click any listing to preview the full configuration diff.
  4. Click Install to add it to your current project.

Installed configurations are immediately active. They appear alongside your native agent definitions in Project Settings → Agents.


Forking a Configuration

Forking creates a private copy of any marketplace listing inside your project.

  1. From a marketplace listing, click Fork.
  2. The configuration is copied to your project under a new name.
  3. Edit it freely — your fork is independent of the original.
  4. Optionally, publish your fork as a new marketplace listing.

Forking is the recommended path when you want to customize a community configuration without losing the ability to track upstream changes.


Version Pinning

When you install a marketplace configuration, you pin it to the version that was current at install time. To update:

  1. Go to Project Settings → Agents → Installed.
  2. Listings with available updates show a Update Available badge.
  3. Click Review Changes to see a diff, then Accept Update to apply it.

You can also choose Stay on this version to keep your current install indefinitely.


Marketplace Architecture

The marketplace is built on top of three primitives that already exist in every SaaS Factory project:

  • pinnedSpecs — structured rule sets consumed by the AI architect and compliance agents
  • pipelineConfig toggles — boolean and enum flags controlling which pipeline stages run and how
  • agentPersona definitions — JSON objects describing each agent's identity and behavioral profile

Publishing a configuration packages these objects into a versioned, signed marketplace artifact. Installing one merges the artifact into your project's local copies of those same data structures. No new file formats or runtime dependencies are introduced.


Tips

  • Start with a fork, not a blank slate. Browse the marketplace before writing a new persona from scratch — there is likely an existing configuration close to what you need.
  • Tag your listings precisely. Users filter by industry and use case; a well-tagged listing gets significantly more installs.
  • Pin specs for compliance-heavy domains. A published fintech or HIPAA pinned spec can save a new user hours of manual rule authoring.
  • Use pipeline bundles for team consistency. Publishing your team's standard pipeline config ensures every new project in your organization starts from the same baseline.

What's Coming

The marketplace lays the foundation for Pro Agent Packs — premium, curated configuration bundles for specific verticals and use cases. Stay tuned for announcements in a future release.


Related