A shared picture.
A better release.

Built for the whole delivery conversation

• DevOps and automation engineers: connect infrastructure, build, deployment, verification and recovery in a single model.
• Developers: understand dependencies, database changes and the path from a source change to production.
• Architects: review environments, runtime dependencies, delivery decisions and target designs with a team.
• Product owners: see where manual work and uncertainty affect delivery, then agree on an improvement backlog.
• Consultants and clients: use a shared diagram to surface assumptions, discuss alternatives and capture what was agreed.

Run a useful design session

1. Choose a starting point. Open a template, explore the example workshop, start a blank blueprint or load an existing file.
2. Map the current design. Add your environments, components and activities. Describe what is manual, assisted, automated or unknown. Record owners, assumptions and evidence where you have them.
3. Connect the work. Show execution prerequisites, promotion between environments and runtime dependencies. Include verification and recovery so the diagram explains more than the happy path.
4. Design a target scenario. Clone the current scenario and change the proposed process. Keep today's reality available while you compare what improves.
5. Agree on next steps. Review findings and open questions. Capture improvement items, ownership and acceptance criteria for the team to discuss.
6. Save and share deliberately. Save a blueprint file to continue later, or use Share design to send an editable copy to colleagues. Export diagrams and process documentation for your workshop output.

Example: an automated app, a manual database

Your app deploys through a pipeline, but an operator runs database scripts and checks production by hand. Model those activities as they work today. Capture the database dependency, who runs the scripts and how success is verified.

In the target scenario, propose a controlled migration step, a verification gate and a recovery path. Discuss ordering and compatibility before connecting parallel work. The result is a design the client, product owner and engineers can review together.

Work with your AI assistant in both directions

Choose Export → Work with AI… in the editor to prepare a prompt and blueprint for your assistant. Ask it to map the design into implementation tasks, tests and open questions. You choose when and where to share that handoff.

You can also give an assistant workshop notes or feedback and point it at the AI guide. The assistant answers with a model link it writes itself: the flow as readable text inside a link that opens the model directly in Automation Modeler, with a short note on what it assumed. Complete blueprint files and design links are for full documents, such as a revision of a blueprint you gave it, and for assistants that can run code. Review the model, refine it with your team and use Share design for a short link.

The app supports this exchange through links and files. It does not run an AI model, deploy infrastructure or execute the modeled process for you.

Share a design by link or file

Choose Share design beside Save file in the editor. Sharing includes the complete snapshot, with all scenarios, notes and layouts. Later edits do not change a link you have already sent; recipients work on their own copies.

• Encrypted link: choose Create short link, then Copy link for Slack or Teams or Open email draft. Your browser encrypts the snapshot with AES-256-GCM before uploading it directly to Disroot Bin, an independent service that is free to use without an account. Automation Modeler does not host the transfer. Nothing is uploaded just by opening the sharing dialog. The link expires after 30 days; the dialog shows the expiry date. The email draft contains the actual link and expiry, ready for you to send.
• Link with design: the compressed snapshot travels inside the URL, with no upload or service expiry. This link is not encrypted. Long URLs can be rejected or cut short by email and chat apps, especially on mobile.
• Download blueprint file: send the complete .automationmodeler.json file as an attachment. It has no service expiry. The recipient downloads it and chooses Open blueprint. Use this option for lasting sharing, very large designs or when a service or organisation blocks a link.

Anyone with a complete link can open its snapshot, including an email or chat provider that receives it. With a Disroot link, the decryption key is in the link and is not sent to Disroot. The service receives encrypted content and connection information such as your IP address; its privacy policy and terms apply. The app has no early revoke option, and service availability is not guaranteed. Short-link transfers are limited to 2 MiB after compression, encryption and encoding; the app offers the file when the design is too large.

For sensitive information, we recommend sharing the file through your organisation's approved, secure channel. The downloaded JSON file is not encrypted by Automation Modeler.

A Disroot link first shows Open shared design. Choosing Open design downloads and decrypts the snapshot in that browser. The editable copy appears under Recent blueprints and remains available after the link expires. Opening a shared design does not create a file in Downloads: choose Save file to keep a portable copy.

Your blueprint stays under your control

Your working copies are stored in your browser and in files you choose on your computer. Optional Disroot transfers store an encrypted snapshot temporarily; they do not back up or synchronize your workspace. Save a file before clearing browser data or moving to another browser or device. An AI assistant receives your blueprint only when you share it with that assistant.

Designs moved to the Recycle bin remain there until you restore them or confirm permanent deletion. Delete all clears the designs in the bin and their browser snapshots and preserved imports after confirmation. Active blueprints and files saved on your computer stay available. Clearing browser data also clears the bin.

The optional usage counter stores daily totals for app opens and blueprint creation. It does not store visitor or blueprint details. Page visits are counted with Cloudflare Web Analytics, without cookies; it never receives the design or key in a share link. The app's Privacy panel explains both and lets you opt out.