FRStart for free

For architects, tech leads and developers who have to hand over a design

Your architecture, designed with AI, checked and shared in one place, readable by the whole team and by your coding agents.

One model behind every C4, deployment and BPMN view.

Start for freeSee how your team reads it

AI assistant

The assistant proposes a first model from your own words. You review it and apply it.

On a computer, on your first day after sign-up, your home page opens on:

The sample and the draw.io import run without AI.

One model. Three ways to read it.

  • Architect

    Stop redrawing the same system in every view: iyedy draws each one from your model. Before the review, checks that run without AI flag reliability, security and performance risks, and the dossier you export lists their findings.

    Start as an architect

  • Tech lead

    The whole team reads the same model and the same views, a newcomer included. With Team, your organisation gets its own space: members, workspaces and shared rules, around the same models.

    Start as a tech lead

  • Developer

    See where each part runs and what depends on it, from the model. A coding tool you connect to iyedy reads that model too, within your access rights, and can only propose changes: the model changes only when a person applies them in iyedy.

    Only a short list of coding tools can connect, set by iyedy. In your personal space, the connection is on; in an organisation, it is off until an owner asks us to turn it on. Write to us to connect a coding tool.

    Start as a developer

Not technical? iyedy explains your system in plain words.

How it works4 steps

Designed with AI, checked without it, then signed off.

  1. 01/04Assistant

    Describe your system in plain words.

    On a computer, describe a new system in plain words on the home page: iyedy opens a new diagram and the assistant proposes a first model.

    The left part of the home composer: What do you want to design or check? with the start of a description of an online insurance claims platform typed in, and the buttons Explore a sample and New diagram from a description.
    In the application: the home composer
  2. 02/04Assistant

    You decide.

    The first model arrives as a proposal, listed change by change. Nothing changes in your model until you click Apply.

    The end of the first model in the assistant panel: the last changes listed one by one, a ticked security setting in its own group, then the buttons Apply 22 changes and Discard.
    In the application: the proposal
  3. 03/04Without AI

    Check it before review.

    The checks run without AI, in your browser. Same model, same register and radar, same day: same findings, in the same order.

    The sign-off panel of version 8: the rules run without AI, 18 findings, starting with DATA-01 No backup on a database, severity MED.
    In the application: the checks
  4. 04/04Approved

    On your own, you sign off a version.

    A version you put up for review moves through Draft, In review, Changes requested and Approved. You sign it off as the author; in an organisation, verdicts count by its rule.

    Close-up of the sign-off panel: the sign-off of v8 with the status Approved, by Alex Morgan, author, signed off by the author without an outside opinion.
    In the application: the sign-off

The assistant

It proposes, change by change. You apply.

Describe a new system in plain words, or ask about the one you have. The assistant proposes; nothing changes in your model until you click Apply.

The assistant panel: the first model as a numbered list of elements and relationships to add, a security setting in its own group, then Apply 22 changes and Discard.
In the application: a first model, listed change by change.
Illustration: on an existing diagram, a pending proposal is drawn dashed and marked PROPOSED until you apply it.
The assistant panel: an answer with a Not stated in the diagram paragraph, an Assumed paragraph, then the cited elements of the model.
In the application: an answer that names what it rests on.

  • Applied to a diagram, a proposal becomes a version

    Each proposal you apply to a diagram becomes a version, with who applied it and when. Undo takes it back as long as nothing else has changed, and History lets you compare or restore an earlier version.

  • Answers that cite your diagram

    Answers cite the parts of your diagram they rest on. What the diagram doesn’t state is listed apart, and assumptions are labelled.

  • Security never changes silently

    A security change you did not ask for waits for your yes, in its own group, unticked until you tick it.

  • AI credits, and an off switch

    The assistant uses AI credits. AI can be turned off, for a whole organisation, per workspace or in your personal space, and the model, the views, the checks, imports and exports keep working.

Your diagrams are stored in the European Union, and iyedy trains no model on your data. When AI is on, what a request needs and, in a personal space, short summaries for the landscape map are processed by our AI model provider, with no guarantee of processing inside the European Union. What leaves iyedy, in full

The film4 min

From a first architecture diagram to sign-off, in six steps.

The film follows Alex, a solution architect, through a fictional case. Pick a step to jump straight to it.

Title card of the film: From a blank page to sign-off, iyedy.Play the film
  1. DescribeA few sentences are enough: the assistant proposes a first model.
  2. DecideNothing changes before Apply, and security is never added silently.
  3. DeployProduction joins the same model, with the official cloud icons.
  4. Every viewSequence, data flow and BPMN from one model: a rename reaches the sequence and the deployment.
  5. AskAnswers name the parts of the diagram they rest on; unknowns and assumptions are set apart.
  6. Sign offThe author signs off the version; each proposal applied to the diagram is a version.

Narrated in English, with English captions, 4 min 13.

Read the transcript
  1. Can an assistant design with you, without changing anything behind your back?
  2. Follow Alex Morgan, solution architect, from a blank page to sign-off in iyedy.
  3. Step one: describe it in plain words, and the assistant drafts the model.
  4. Alex starts on the home page, and describes the system in plain English.
  5. An API gateway, two services, two stores, and fraud scoring on Kafka.
  6. One Enter, and iyedy opens a new diagram while the assistant drafts it.
  7. Step two: you decide. Nothing changes until the architect applies it.
  8. Half a minute later, the first model: every element and relationship, listed for review.
  9. Yet the canvas is still empty: nothing lands until Alex applies.
  10. Security is never added silently: it asks first, and Alex says yes.
  11. A moment later, the gateway joins the proposal, in its own security group, unticked.
  12. Alex ticks it, then the four links that go through it.
  13. One Apply, and the whole design lands, with a single undo.
  14. And two views nobody drew: the system context, and the containers.
  15. Step three: production joins the same model, not a separate drawing.
  16. Next, production on AWS: eu-west-3, the Paris region, with managed services.
  17. Seconds later, the cluster, the network and the managed stores are ready to add, on AWS.
  18. Before anything lands, it counts the findings production would add, rule by rule.
  19. Alex applies it anyway, and keeps the gaps for the sign-off.
  20. The deployment view draws the cluster,
  21. the database and the storage, with official AWS icons.
  22. Step four: every view comes from one model, so none of them drift.
  23. Alex asks for a customer filing a claim, plus a data flow.
  24. Half a minute later, both are ready, and Alex applies them.
  25. The sequence shows the claim moving through the services, step by step.
  26. The data flow numbers the stores and the event stream: D1, D2, D3.
  27. Alex selects Claims Service, and renames it once: Claims Engine.
  28. The sequence follows: its lifeline now reads Claims Engine.
  29. So does the production deployment, inside the EKS cluster.
  30. One undo puts the old name back.
  31. Then the business process, in BPMN: how a claim is handled, from filing to payment, with a lane per service.
  32. Moments later, the process is proposed, and Alex applies it.
  33. It is drawn in BPMN: a lane per service, each task, and each decision.
  34. Step five: question the design, and get answers that cite it.
  35. Alex selects Claims Service, and asks what depends on it.
  36. The answer is instant: computed in the browser, with nothing sent.
  37. Or Alex asks in plain words: what breaks if Claims Service goes down?
  38. Seconds later, the answer names the parts of the diagram it rests on.
  39. What the diagram doesn't say is listed apart, and assumptions are labelled.
  40. Step six: sign off. The approved version is frozen, and every applied change is a version.
  41. Before signing, Alex opens the checks: thirty-six rules, run without AI.
  42. The backup gaps from the deployment are still open, in plain sight.
  43. As the author, Alex signs off this version; an outside opinion stays optional.
  44. The stamp turns Approved: on the version, on the view, and in its title block.
  45. And each applied proposal is its own version, with who and when.
  46. iyedy: the assistant drafts, the architect decides.
  47. From plain sentences to an approved, versioned design.
Review dossierPDF

What your reviewers receive.

A review dossier built in your browser from your model, exported as a PDF. Your reviewers read it for free, with no account. For a diagram classified Public, you can also share a read-only link that opens without an account, for 90 days at most.

The dossier text is in English today; its statuses follow the diagram’s language. In a personal account, the same PDF is titled Sign-off pack, with one sign-off row: the author’s.

  1. 1Summary and stakeholders
  2. 2Views
  3. 3Interfaces
  4. 4Requirements and quality attributes
  5. 5Decisions
  6. 6Risks
  7. 7Findings
  8. 8Revisions
  9. 9Sign-off
Cover of the review dossier: Lumora Retail, omnichannel commerce and payments, a title block with document id, date, status In review, classification and template Review dossier.
Page 3, summary and stakeholders’ concerns: 6 views, 29 elements, 28 interfaces, open findings and risks, and a table of viewpoints.
Containers view page of the commerce platform, printed on its page with its title block.
Risks page: the 5 × 5 heat map of likelihood and impact, with the risk ratings.
Sign-off page as an organisation exports it: an empty table for the author, the reviewer and the approver, to fill in a PDF reader or on paper.
Exported PDF of the sample: the review dossier of a fictional retail platform, 20 pages, as an organisation exports it.

Who signs, said plainly.

Personal accountFictional example

You sign off as the author.

On your own, you sign off your version, and the people you invite give an opinion recorded with their name.

  • Alex MorganAuthorApproved
  • Inès RobertInvited reviewerOpinion recorded
OrganisationFictional example

Verdicts count.

In an organisation, verdicts count by its rule: four eyes by default, a quorum or required reviewers if it sets them.

  • Marc DuboisArchitectureApproved
  • Inès RobertSecurityApproved

A person you invite to review signs up for free and accepts your invitation. Reading the PDF needs no account.

Clear prices. Start for free.

Readers never pay: they read the PDF with no account.

Launch price: 19.99 € excl. VAT a month, that is 23.99 € incl. 20% French VAT (199 € excl. VAT a year, that is 238.80 € incl. 20% French VAT) until 31 January 2027

Billing period

Free

To try it on your own.

0 €

No card needed

  • 1 editor, 5 active diagrams
  • 300 welcome AI credits, valid 30 days
  • 3 public links, 30 days of history
Start for free

For an organisation: Team at 24 € excl. VAT per seat per month, plus VAT, from 2 seats, 1,000 AI credits per seat per month, pooled, 14-day free trial.Team at 240 € excl. VAT per seat per year, plus VAT, from 2 seats, 1,000 AI credits per seat per month, pooled, 14-day free trial. Enterprise from 480 € excl. VAT per seat per year, plus VAT, from 25 seats, 1,500 AI credits per seat per month or your own key, billed yearly.

Try Team for 14 daysTalk to the team

Pack of 500 AI credits: 11.99 € excl. VAT (14.39 € incl. 20% French VAT), valid 12 months, for paying Pro and Pro+ subscribers, and for Team, trial included. Prices exclude VAT: VAT is added at checkout, according to your country and status. The price including VAT shown for the personal plans and the pack is that of a consumer in France (20%); an organisation pays excl. VAT, VAT on top. Consumers have 14 days to withdraw.

Questions.

Already have diagrams?

Import them, on a computer: a draw.io file, a Structurizr workspace, a Mermaid flowchart, or a Mermaid sequence or C4 diagram. Imports run in your browser, without AI, and each one becomes a model that iyedy checks like any other.

Can the assistant change my diagrams without me?

No. The assistant proposes changes, listed one by one. Nothing changes in your model until you click Apply, and each proposal you apply to a diagram becomes a version, with who applied it and when. Undo takes it back as long as nothing else has changed, and History lets you compare or restore an earlier version.

What leaves iyedy when AI is on?

Your diagrams are stored in the European Union. AI can be turned off, for a whole organisation, per workspace or in your personal space, and the model, the views, the checks, imports and exports keep working. When AI is on, what a request needs (an excerpt of the model, a file you attach, the assistant’s web searches) and, in a personal space, short summaries of your diagrams for the landscape map are processed by our AI model provider, with no guarantee of processing inside the European Union, and deleted by it within 30 days, except content its safety checks flag. iyedy trains no model on your data. A coding agent you connect to iyedy is another case: what it reads goes to your agent’s AI provider, under your agreement with that provider. Turning AI off in iyedy does not stop it: to end the connection, disconnect iyedy in your agent.

Do my reviewers need an account?

Not to read: they read the PDF, with no account. For a diagram classified Public, you can also share a read-only link that opens without an account, for 90 days at most. A person you invite to review signs up for free and accepts your invitation.

Do I need a computer?

To design and to import, yes: describing a new system, applying a proposal and importing a file happen on a computer. Reading also works on a phone: the PDF, a read-only link for a diagram classified Public, or the app, to check a diagram and ask about it; changes are made on a larger screen.

Your architecture, in one place, for the whole team.

Start for freeContinue with Google

No card needed. Readers never pay.

Approved