Make things worth keeping

The self-hostable home for AI artifacts.

You've never made more, and never kept less. Derive is your team's library for the work you and your agents make: publish it, share it anywhere with a link, and revise it together until it's right. One URL, every version, yours.

Get a live link for your artifacts in the next 30 seconds.

FIG. 01 — a live artifact · the loop, running
derive.to/artifacts/osc8-launch HTML · v1 password MACY 3 here Approved

OSC-8 Synthesizer

Preorder — €249
PRODUCT IMAGE
8voices
Polyphony
22h
Battery · measured
1.8ms
Key → sound
380g
With battery
Measured on production unit №0043 · not simulated, not quoted
v1v2v3
v1 agent · claude-code first draft · three directions, one straw-man rec
A question for you

Your agents shipped forty things last week.

Can you find them?

Most of it is gone, pasted into a Slack thread or stranded in a chat that scrolled away. Making another draft was never the hard part. The hard part is finding the one from Tuesday, trusting it's the latest, and getting a second pair of eyes on it before it goes out. Derive gives every artifact a permanent link, keeps every version, and puts the review right on it, so "where's the latest?" always has one answer.

01

Publish

Off the clipboard and onto the record.

One command takes a document, a designed page, or a whole built site to a permanent URL. Fully-styled HTML renders exactly as authored, fonts and scripts and images included, in a sandboxed viewer. Every revision is a new version at the same link, so the link you shared last week still resolves, and still shows its history. You can put it on your own domain.

If an agent can make it, Derive can hold it: Markdown, a single HTML file, or a two-hundred-file build. Publishing is instant, and you never have to decide which drafts are worth keeping, because keeping all of them is the default.

derive publish
$ derive publish launch/
→ 14 files · 1.2 MB · sandboxed
✓ live at derive.to/artifacts/q3-launch-plan
02

Share

Your team's library, anyone's link.

Everything your team publishes lands in one library, so "where's that thing?" always has the same answer. When work needs to leave the building, you send a link: put a password on it for a client, open it to anyone who has it, or keep it inside the team. Whoever opens it sees the real, rendered page in their browser, not a zip or a PDF export.

Every link carries a role you chose: viewer, commenter, or editor. People outside your team never need an account, their feedback lands in the same place yours does, and you can revoke a link the moment you change your mind.

Share · redesign-proposal
03

Collaborate

Multiplayer for made things.

Share the link and your team is in, with comments pinned to the exact line, @mentions for people and agents, live presence, and approvals. A draft stays clearly a draft until a named person approves a version, so nobody has to wonder whether what they're reading is final. When it's just you, Derive is a private library of everything you've made, running the same loop with a population of one.

Presence shows who's looking right now, and threads stay attached to the version they were about, so a decision keeps its context long after the conversation would have scrolled away. An approval means something because it's on the record.

Comments · q3-launch-plan
AAda
"pilot cohort first"
Which nine teams? Name them or nobody plans around it.
MMaeva
Seconding. Owners too, @claude-code.
Cagent · claude-code
All nine listed, with owners, in v3.
RESOLVED IN V3
04

Own

Yours, not the model's, not ours.

Claude's artifacts live in Claude. ChatGPT's canvases live in ChatGPT. If half your team runs one and half runs the other, the work ends up split across two walled gardens. Derive doesn't care which model made what: context lives with the artifact, so a page Claude drafts on Monday gets revised by Codex on Tuesday, and your team reads both in one library.

The same openness goes all the way down. The product is Fair Source and runs as a single container on your own infrastructure if you want it to, and everything exports in open formats: artifacts, versions, and comments. If you ever leave, the record leaves with you.

self-host
$ docker compose -f deploy/compose.yml up -d
→ http://localhost:8080 · sqlite · local disk
FSL-1.1-ALv2 → Apache-2.0 after two years
Agent-native

Where agents put their work.

Every agent speaks MCP, and Derive has an MCP server built in: one command connects Claude Code, Codex, Cursor, or whatever your team runs. From then on the agent stops pasting walls of HTML into chat and starts publishing real pages at real URLs, with visibility you control, while you read and review them in an interface built for people. Leave a comment and the agent answers with a revision.

derive · agent session

publish save a revisioncatch_up what changed + open feedbackcomment reply or resolveread any artifact, any version

one paste into any agent — it sets itself up and publishes your first page
Pricing

Free while it's in beta.

Every feature, no card required. When billing arrives someday, publishing and reading stay free, and nothing you've shipped goes dark.

v1 · drafted by an agent, 09:41:07

Good work is generated. prompted. derived.

Nothing you're proud of ships in one pass. It's free while we're in beta, so sign up and we'll email your access link, or clone the repo and run the whole thing tonight.

Check your email. Your access link is on the way.

 ·  $ docker compose up -d  ·  derive-to/derive on GitHub