I’m new to iyedy
In under an hour you build a first diagram of a system you know, check it, ask the Assistant for a change, save a version and share it. You can do all of it on the Free plan.
This path is for you if
You design or explain systems and want diagrams that stay true when the system changes. You have never used iyedy, or only once.
Not for you if someone sent you a diagram to review: take I was invited to review. If you set iyedy up for a company, take I run an organisation.
At the end you have
- A diagram of a real system, with a containers view drawn from one model.
- A change proposed by the Assistant, reviewed and applied by you.
- A named version, shared with a colleague or exported for a document.
The steps
- What is iyedyWhat one model and many views means, in five minutes of reading.
- Your first diagram in 10 minutesThe core of the path: build, connect, check, ask, save.
- Ask, review, applyHow to read a proposal before you apply it, and how to undo it.
- Save and restore versionsNamed versions, the history and how to restore one.
- Share a diagram or Export a viewShare the diagram with people, or export a view as a picture or a file.
- Plans comparedWhat Free includes, and when Pro or a team makes sense.
If your company already uses iyedy, your administrators set who edits and what the Assistant may read. Read Roles and permissions to know what your role lets you do.
Common questions
- Key concepts: the words iyedy uses, in one page.
- Credits and credit packs: what a credit is and what uses none.
- Changes not saved: what to do when the status bar says your changes are not saved.
Other paths
I was invited to review
I run an organisation
I connect Claude or the API
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.