DocsArtifacts
How Marketplace artifacts work — versioned, immutable packages of blueprints that can be distributed and installed across organizations.
An artifact is a versioned, immutable package created when a blueprint is published to the Marketplace. Artifacts are the unit of distribution — they are what organizations browse, acquire, and install.
Artifact structure
An artifact is a deep copy of a blueprint at a specific point in time. It captures:
| Component | What is included |
|---|---|
| Blueprint configuration | Name, description, category, icon |
| Agents | All agent definitions, instructions, model settings, tools |
| Flows | Complete flow graphs — steps, groups, edges, triggers |
| Collections | Schema definitions — fields, types, validation rules |
| Integrations | Integration definitions, operations, auth schemes, channels |
| Knowledge base | Document references and embedding configurations |
| Actions | All action definitions and runner configurations |
The artifact is self-contained. It does not reference the original blueprint — changes to the source blueprint do not affect published artifacts.
Versioning
Each publish creates a new version of the artifact:
Versions follow semantic conventions:
| Part | Meaning |
|---|---|
| Major | Breaking changes — new required connections, removed features |
| Minor | New features — additional agents, flows, or collections |
| Patch | Bug fixes — corrected flow logic, updated instructions |
Organizations that have acquired an artifact can choose when to upgrade to a new version. Upgrades are explicit, not automatic.
Acquired artifacts
When an organization acquires an artifact from the Marketplace, it is added to the organization's artifact library. From there, it can be installed into any space.
Artifact lifecycle
Published → Acquired → Installed → Running| State | Description |
|---|---|
| Published | Available in the Marketplace catalog |
| Acquired | Added to an organization's library |
| Installed | Deployed as an app in a specific space |
| Running | Active and processing data, conversations, and flows |
Multiple installations
A single acquired artifact can be installed in multiple spaces. Each installation creates an independent app instance with its own:
- Runtime data (collections, records, conversations)
- Connections (integration credentials)
- Configuration overrides
Immutability
Artifacts are immutable once published. This guarantees:
- Reproducibility — installing version 1.2.0 today produces the same result as installing it next month
- Stability — running apps are not affected by changes to the source blueprint
- Auditability — you can trace exactly which version is installed in each space
To make changes, publish a new version of the artifact.
Related concepts
- Publishing — how to create and publish artifacts
- Marketplace — browsing and discovering artifacts
- Blueprints — the source material for artifacts
- Apps — what artifacts become after installation