Create a PlantUML deployment diagram online to map runtime nodes, deployed artifacts, databases, and network connections, then preview and export PNG or SVG.
Start with the Deployment Diagram template, edit the PlantUML source, and preview the result live.
Use this focused deployment diagram tool for quick previews and exports. Open the full editor for AI generation, syntax repair, sharing, and saved projects.
Model runtime nodes, execution environments, deployed artifacts, databases, queues, network boundaries, and labeled connections in an editable PlantUML workspace with live preview and PNG or SVG export.
Start from valid PlantUML source designed for a practical deployment diagram.
See the rendered diagram update as you edit the PlantUML source.
Learn the syntax and modeling choices used for production architecture reviews, cloud migration planning, environment documentation, incident response, and release handoffs.
Download a shareable PNG or scalable SVG from the same source.
Create and preview PlantUML without installing Java, Graphviz, or an IDE extension.
Move to the full editor for AI generation, repair, sharing, and saved projects.
Use the built-in template to create a deployment diagram for production architecture reviews, cloud migration planning, environment documentation, incident response, and release handoffs.
Choose one environment and question, such as how the production application is deployed.
Add the machines, cloud services, devices, or execution environments that exist at runtime.
Nest each deployed artifact or service inside the node where it runs.
Connect the nodes and label important protocols, ports, or data paths.
Check the live preview for missing boundaries or dependencies, then export PNG or SVG.
Learn the core syntax and modeling decisions behind a useful deployment diagram, then apply them directly in the online editor above.
Use node for a machine, device, cluster, or execution environment. Use cloud, database, queue, storage, and other deployment elements when their shapes help readers recognize infrastructure roles. Name elements after the deployed environment, not an abstract software capability.
Nest artifacts, components, or files inside a node to answer the practical deployment question: what runs where? Keep the artifact name concrete, such as a container image, service package, executable, or configuration bundle.
node "Application Server" as appNode {
artifact "orders-api.jar" as api
}Connect nodes or deployed elements with arrows, then label the relationship with the protocol or responsibility that matters to operators. HTTPS, AMQP, SQL/TLS, and replication are more useful than an unlabeled line.
webNode --> appNode : HTTPS
appNode --> databaseNode : SQL/TLSUse a deployment diagram when the question is where software runs and how runtime environments connect. Use a component diagram when the question is which software modules or services exist and which interfaces they depend on, independent of their physical placement.
The editable example demonstrates a practical deployment diagram. Change the source, check the live preview, and export the version you need.
@startuml
node "Web Server" as Web {
artifact "web-app" as Frontend
}
node "Application Server" as App {
artifact "orders-api.jar" as Api
}
node "Database Server" as DbNode {
database "Order Database" as Db
}
Web --> App : HTTPS
App --> DbNode : SQL/TLS
@endumlUse these related tools when you need a different export format or a full PlantUML editing workflow.
Browse the complete OnUML matrix of online PlantUML tools and converters.
View all PlantUML toolsUse the general editor when you want to switch freely between diagram types.
Open the general editorCreate and export a focused component diagram with a built-in template.
Create a component diagramPlantUML keeps deployment diagrams in reviewable text, making them easier to update, version, reuse, and export as the design changes.
Open directly into a Deployment Diagram template instead of adapting an unrelated example.
Store the diagram as readable text that works well in documentation and version control.
Check structure, labels, and relationships before exporting the rendered diagram.
It is a browser-based editor that starts with a Deployment Diagram template and lets you edit PlantUML source, preview the rendered diagram, and export PNG or SVG without local setup.
Use it to model runtime nodes, execution environments, deployed artifacts, databases, queues, network boundaries, and labeled connections. Common uses include production architecture reviews, cloud migration planning, environment documentation, incident response, and release handoffs.
Include the runtime nodes needed to answer the review question, the important artifacts or services deployed to them, and the connections that affect delivery, security, reliability, or operations.
Yes. PlantUML supports deployment elements including node, cloud, database, queue, storage, artifact, component, and nested elements, which can be connected and labeled.
Yes. Preview the diagram, then download PNG for slides and quick sharing or SVG for scalable documentation and web use.
No. The online tool uses a server-backed preview, so you can edit and render the diagram directly in the browser.
Open the full OnUML editor for AI generation, syntax repair, sharing, saved projects, and multi-format diagram workflows.