Self-hosted artifact layer

Owned URLs.

Push generated work from CLI or MCP. Atlas gives it one owned link with versions, access, and review attached.

Interactive path

Build it. Publish it. Control it.

The next step is an interactive artifact demo: bundle on the left, live artifact in the middle, control sidepanel on the right.

./Build

$Push

v4Version

⌁Share

published artifactlive url

Client report

Static bundle rendered at one stable address.

Control sidepanel

VersionsAccessComments

v4Current · 2 min ago

✓

v3Review copy

v2Internal draft

public

unlisted

private

password

Access updatedPrivate link active. Share without exposing the server.

Comment attachedFeedback stays with the artifact, not the chat.

URL unchangedThe artifact changed. The link stayed.

Not another static host

A deploy gives you a URL. Atlas gives it a lifecycle.

Static hosts are great for publishing files. Atlas is for generated work that needs ownership, access, versions, and review.

Static hosting

Upload filesyes

Get a public linkyes

CDN, SSL, domainplatform

Review contextexternal

Atlas artifact layer

Stable owned URLcore

Versions and rollbackartifact

Access per artifactbuilt in

Comments and handoffattached

Built for agent output

Small primitive. Serious controls.

Atlas is not a CMS or a drive. It is the handoff layer after generation.

▣

Self-hosted security

Run it on infrastructure you own. Keep access rules per artifact.

AI-first handoff

Agents get a simple publish target through CLI and MCP.

⌁

Access control

Public, unlisted, password, or private links.

Version history

Replace the bundle. Keep the URL and context.

Roadmap

Self-host first. Hosted when you want it.

Atlas starts as owned infrastructure. The roadmap includes a managed service for teams that want artifact hosting without running the box.

Bring your artifacts. Choose your control plane.

Run Atlas on your VPS today. Later, use hosted Atlas when you want the same artifact lifecycle without operating storage, TLS, and backups.

Now

Self-hosted AtlasOne Go binary, SQLite metadata, filesystem blobs, CLI and MCP publish target.

Interactive artifact control panelVersions, comments, access rules, activity, and share links in one sidepanel.

Later

Hosted Atlas serviceManaged artifact hosting for people who want the workflow without running the server.

Waitlist

Own the handoff.

Join for early builds and notes on self-hosted artifact workflows.