Open Artifacts alternative
Agent documents for your company, with no server to run.
Open-source artifact servers give you the code. Display gives you the hosted result: sign-in, roles, comments and versions at one link.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – then a teammate opening its URL, selecting Edit, changing a number on the page and saving v2, a colleague commenting on v2, the agent publishing v3 at the same URL and resolving the comment, and the doc being shared with someone outside the company.
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
Used by top teams at
What is an Open Artifacts alternative for company documents?
Open Artifacts is a name that several open-source projects use. Each project hosts HTML or Markdown from coding agents on infrastructure that you control. They suit a team that must run its own server and has people to maintain it. Display (display.dev), the docs workspace for agents and people, runs the service for you. The organization owns the artifacts. Colleagues open them with Google, Microsoft or a one-time password (OTP). Agents read and resolve the comments. Use an open-source server when policy requires that you run the code. Use Display when you want the result without operating a server.
Open Artifacts projects and Display compared
| coda0HQ/open-artifacts | emaxe/open-artifacts | plannotator/artifact-server | Display (display.dev) | |
|---|---|---|---|---|
| License | MIT | MIT | MIT or Apache-2.0 | Hosted service |
| Where it runs | Your Cloudflare account (Workers and D1), or a public shared instance | Docker Compose | Local, Docker Compose, Kubernetes, AWS, Google Cloud or Cloudflare | Display runs it |
| Accounts | None. A write token for each artifact | Organizations with superadmin, admin and member roles | Its deployment guide covers authentication | Google, Microsoft or OTP. Owner, Admin and Member roles |
| Access | Unguessable unlisted links. Optional password with client-side encryption | Team-only, password or public links, with expiry after 1 hour, 1 day, 7 days or 30 days | Private team deployments | Public, company, or private with invited people |
| MCP | Not mentioned | Built in at /mcp, with an API key | Built in | Yes, with OAuth or an API key |
| Versions | Each publish is an immutable version at the same link | Version picker on the share page | Versioned artifacts | 10 on Solo, 50 on Pro, at the same URL |
| Comments | Not mentioned | Not mentioned | Yes | Pinned to a passage. Agents read and resolve them |
| Company sign-in and audit log | You build them | You build them | Not mentioned | Google and Microsoft sign-in and a 90-day audit log on Pro |
| Price | Free software, plus your infrastructure and time | Free software, plus your infrastructure and time | Free software, plus your infrastructure and time | Free €0. Solo €15. Pro €49 a month |
"Not mentioned" means that the README does not say. It does not mean that the feature is absent.
Where an open-source server is better
- Control of the code and data
- You run the server in your own account or cluster.
- Licenses that allow changes
- MIT and Apache-2.0 let you change the code and run your own version.
- Deploy targets
- plannotator/artifact-server lists Kubernetes, AWS, Google Cloud and Cloudflare.
- Client-side encryption
- coda0HQ/open-artifacts encrypts a password-protected page in the browser.
- Link expiry
- emaxe/open-artifacts lets links expire after 1 hour, 1 day, 7 days or 30 days. Display has no expiring links.
Where Display is better
- No operations
- There is no server to deploy, patch or back up.
- Company sign-in and roles
- Google and Microsoft sign-in on Pro, and Owner, Admin and Member roles, with no code to write.
- Records
- Pro keeps a 90-day audit log. Every version shows who or which agent published it.
- A claim flow
- An agent publishes with no account, and you claim the result into your organization.
- Browser edits
- You can correct a line in the browser without a new agent run.
When to use which
- Use an open-source server
- when policy requires that you run the code and you have a person to maintain it.
- Use Display
- when you want company access, comments and version history without a server to run. Tell your agent: "Publish report.html to Display." Without a saved login, the agent returns a 30-day public preview and a claim link. See Publish without an account.
Common questions.
What is Open Artifacts?
Several open-source projects use the name or a similar one. Each project hosts HTML or Markdown from coding agents on infrastructure that you control.
Which licenses do they use?
coda0HQ/open-artifacts and emaxe/open-artifacts state MIT. plannotator/artifact-server states MIT or Apache-2.0.
Can I self-host Display?
No. Display is a hosted service only.
What does self-hosting cost?
The software is free. You pay for the infrastructure and for the time to run it.
What does Display cost?
Free is €0. Solo is €15 a month. Pro is €49 a month. Enterprise starts at €499 a month. Every plan has unlimited viewers.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).