A diagram in your READMEthat never goes stale.
Architecture screenshots rot the day the system changes. A live embed is one line of markdown on a permanent URL: edit the diagram once and every copy shows the new version within minutes.
Part of Pro and Team · 7-day free trial · No credit card
GitHub
GitLab
Notion
ConfluenceHow it works
Three steps, then it stays correct
Public project, one line of markdown, done. The embed does the maintenance.
Make the project public
Open Embed in the canvas top bar and switch on "Anyone with the link". That mints the permanent embed URL. Viewers see the diagram, never the editor.
Copy one line
The markdown image for GitHub and GitLab READMEs, the iframe for Notion and docs sites, or the bare image URL. The dialog shows each next to a live preview.
Paste it and forget it
Commit it to the README, paste it in Confluence. Edit the diagram later, by hand or through your agent, and every embed updates within minutes.
An embed is not an export.
The URL serves the current diagram, not a saved copy. What your docs show stops drifting from what your system does.
See it live
This one is real
The rendered pane is a live fetch of a public Datadef diagram, served by the same /api/embed endpoint your diagrams get.
What you paste
## Platform architecture
Identity resolution and activation across our customer touchpoints.
_Diagram stays current. It is embedded from Datadef, not exported._
The highlighted line is the embed. Everything markdown renders takes it: GitHub, GitLab, Notion, Confluence, Obsidian, docs sites.
What readers see
LIVEPlatform architecture
Identity resolution and activation across our customer touchpoints.
Diagram stays current. It is embedded from Datadef, not exported.
A first render after an edit can take a few seconds; after that the image is served cached until the next edit.
The whole integration
One line. Swap the slug for your own diagram and paste it anywhere markdown renders.
Honest answers
Who can see an embedded diagram?▼
Anyone with the link, no sign-in required. Viewing is all the link grants: the embed and the public page are strictly view only, and editing stays with the owner and the people they invite into the project.
Does my project have to be public?▼
Yes. The embed URL resolves only while the project is shared with "Anyone with the link", which is the switch that mints it. For internal-only docs, keep the project private and share the project link with invited members instead.
What if I make the project private again?▼
Every embed of it stops resolving, immediately. Making the project private is the kill switch for every copy at once: READMEs, wikis, docs sites.
How fast do edits show up?▼
Within minutes. The first render after an edit can take a few seconds while the new version is drawn; after that the image is served cached until the next edit.
What happens if my plan lapses?▼
Embeds keep rendering. Nothing is deleted and no URL breaks; the image stays frozen at the last edit, because editing pauses until a plan is active again.
Is embedding part of the free trial?▼
Public sharing is part of Pro and Team, and every new account starts with a 7-day trial of the full product, no card required. Make a project public during the trial and its embed behaves like any other.
Put a live diagram in your docs
Make a project public, copy one line, paste it where your team already reads. Every new account starts with a 7-day trial of everything, no card needed.