Artifact Server documentation

Run Artifact Server, publish artifacts, review them live with coding agents, understand the version model, and deploy it for a team.

Artifact Server stores finished browser files as immutable versions and serves each version from an isolated hostname. People and agents can publish, inspect, review, share, and revisit the same work without treating generated output as source code.

Welcome your team

Give teammates and agents one short setup path into your team’s Artifact Server.

Open the team introduction →

Get started locally

Run the application on your machine with loopback-only owner access and publish a first artifact.

Start locally →

Understand the model

Learn why projects contain artifacts, artifacts point at current versions, and versions never change.

Read the mental model →

Built-in MCP server

Connect Claude Code, Codex, Cursor, or another MCP client. Install the Agent Skill to publish from the agent.

Connect your agent →

Publish from agents

Use the CLI for local files. If the connected agent has the bytes and context, use MCP.

Choose a publishing path →

Review with your coding agent

Leave comments and send them to Pi, OpenCode, or Claude Code. The agent can reply to and resolve each thread.

Connect a coding agent →

Deploy for a team

Compare each deployment target and its current qualification level.

Choose a deployment →

Verify the supply chain

Read how CI protects source changes and what evidence each package contains. Learn which public verification assets do not exist yet.

Read the security evidence →

Product hierarchy

Artifact Server installation
└── Project
    └── Artifact
        └── Immutable version

One installation represents one person, team, or company. A fresh installation creates a default project. Stable artifact links resolve to the current version. Exact version links never move.

License

Artifact Server uses the GNU Affero General Public License v3.0 (AGPL-3.0-only). You can use, self-host, and modify it. If you offer a modified version over a network, the AGPL requires you to publish the modified source under the same license. This requirement does not apply when you run the unmodified software or use it inside your own team.

The @plannotator/agent-bridge protocol client and the agent extensions under integrations/ use the MIT License.