Sequence diagram generator
Early accessEarly access. Free to start.
Sequence diagram generator: describe who talks to whom
Describe a scenario step by step: who sends what, to whom, and what comes back. The sequence diagram generator draws the lifelines, messages and alt or loop frames, and gives you Mermaid code to keep with your code.
How the sequence diagram generator works
Describe the scenario
Name the participants (user, web app, API, database, email service) and list the messages in order. Mention the failure case too: 'if the token has expired, the API returns 401'.
Get the diagram
Munition draws one lifeline per participant, solid arrows for calls, dashed arrows for replies, and alt or loop frames for conditions and retries.
Review, then copy the code
Check the order and the reply to each call. Then copy the Mermaid code to keep next to your code, or download it as Markdown.
Early access
Describe the flow, skip the arrow-pushing
Join early access, describe a scenario in plain words and get a UML sequence diagram with its Mermaid code. Free to start.
What the sequence diagram maker gives you
Correct UML notation
Lifelines, activation bars, synchronous and asynchronous messages, return messages and notes, drawn the way UML courses and code reviewers expect.
Conditions and loops as frames
'If the card is declined' becomes an alt frame with both cases. 'Retry up to three times' becomes a loop frame. Optional steps get an opt frame, parallel calls a par frame.
Mermaid code you can commit
The diagram is shown on the page and copies as plain Mermaid text: keep it in a Markdown file next to your code, review changes line by line, and render it in any tool that reads Mermaid.
From code, logs or a spec
Paste a request handler, an API spec excerpt or a log trace and ask for the sequence behind it. Compare the result with the real calls before you rely on it.
Exam detail or design-doc detail
Ask for every activation bar and return message when you practice for a UML exam, or for the main calls only when the diagram goes into a design document.
Here, in ChatGPT or Claude, or by API
The plan: use it on this page, inside ChatGPT or Claude through the Munition connector, or from your own code through the Munition API. All three come with early access.
Who uses it
A backend developer preparing a security review
She describes the redirect, token exchange and refresh steps of her login flow and gets the diagram the reviewers asked for.
A software engineering student before a UML exam
He writes the 'borrow a book from the library kiosk' scenario, generates the diagram, then redraws it by hand to practice the notation.
A product manager checking a checkout flow
She describes what she thinks happens when a payment is declined. The diagram shows the engineers exactly where her understanding differs from the code.
A support engineer explaining webhook retries
He diagrams when the platform sends a webhook, what counts as a failure and when it retries, and sends it to a customer instead of a long email.
An architect comparing two designs
He generates one diagram with a direct call and one with a message queue, to show the team where waiting and failures move.
How to draw a sequence diagram for free
Sequence diagrams are among the easiest UML diagrams to write as text, so the free tools are good. Munition saves time when the scenario is buried in a long spec, a meeting summary or code you did not write.
On paper, with the UML notation
Useful to learn the notation, and still the fastest way to sketch at a whiteboard.
- Write the participants across the top, left to right, in the order they first appear.
- Draw a dashed vertical line under each one: its lifeline. Time runs downward.
- Draw each message as a horizontal arrow from sender to receiver, labeled with the call, such as 'POST /login'.
- Use a solid line with a filled arrowhead for a synchronous call, a solid line with an open arrowhead for an asynchronous message, and a dashed line for a reply.
- Frame conditional parts in a box labeled alt, with a dashed line between the cases, and repeated parts in a box labeled loop.
Mermaid
Free and open source. Start with sequenceDiagram, then one line per message: Browser->>API: POST /login for a call, API-->>Browser: 200 + token for the reply. Wrap cases in alt … else … end and repeats in loop … end. Paste it into the Mermaid Live Editor (mermaid.live) to see it drawn. Many documentation and code-hosting tools render Mermaid blocks directly.
PlantUML
Free, open source and long used for UML. Write Alice -> Bob: Hello between @startuml and @enduml. It runs locally (it needs Java) or on the public PlantUML web server. A good choice if your team already draws its other UML diagrams with it.
sequencediagram.org
A free web editor: you type on the left and the diagram draws itself on the right, then you export an image. Handy for a one-off diagram without installing anything.
Tips for a readable sequence diagram
- Order participants left to right in the order the request travels. Most arrows pointing left should then be replies.
- One scenario per diagram: the happy path, or one main failure. Use a single alt frame if you need both.
- Label messages with the real endpoint, function or event name, so the diagram can be checked against the code.
- Show replies only where they carry information. A diagram where every call has a dashed reply doubles in length.
Frequently asked questions
A UML diagram that shows how participants (people, systems or objects) exchange messages over time. Participants sit at the top, time runs downward and each arrow is a message. It answers one question: what happens, in what order, between whom.
Munition is free to start: joining early access costs nothing, and there will be a free plan when the tool opens, with paid plans for heavier use. Mermaid, PlantUML and sequencediagram.org are free today and all turn text into sequence diagrams.
They are combined fragments. alt shows alternatives, like if/else, with a dashed line between cases. opt shows a part that runs only under a condition. loop shows repeated messages, with the condition in brackets, and par shows messages sent in parallel.
A flowchart shows the logic of one process: steps and decisions. A sequence diagram shows the conversation between several participants: who calls whom, and in what order. If your question is 'which system does what, and when', draw a sequence diagram.
Yes, paste a function or a log trace as text and ask for the sequence of calls. The AI reads what the code says, not what happens at runtime, so check the diagram against real traces before using it to debug anything critical.
Paste the Mermaid code into any page or file that renders Mermaid, such as a Markdown file on a code host that draws Mermaid blocks. For a tool that only takes pictures, paste the code into mermaid.live, which turns it into a PNG or SVG file. The text version is easier to keep up to date when the flow changes.
Not yet. The sequence diagram generator is in early access: the plan is for it to work on this page, inside ChatGPT and Claude through the Munition connector, and through the Munition API for developers. With the API, a script could regenerate the diagram whenever the scenario in your docs changes. Join early access and tell us where you would use it: it helps us decide what to build first.
During early access, nothing you type here is processed by an AI. If you join, we may keep the start of your text with your signup, to see what people want the tool for, so leave out anything private: no secrets, API keys or customer data from logs, and only code you are allowed to share. When the tool opens, the Munition privacy policy will describe how text is processed.
Benjamin Martin · Written with the help of AI tools. · Updated