Palori
Source Get the app

PlantUML for Confluence · v2.7.0 · Forge · Free

Source-available PlantUML
for Confluence Cloud.

Write diagrams as text and render them on any Confluence Cloud page. The app is source-available and free — read the code, audit the render path, or point it at your own PlantUML server so sensitive diagrams never leave your network.

Get PlantUML for Confluence → Read the source →
auth-flow.puml plantuml 
1@startuml
2participant Client
3participant "API Gateway" as GW
4participant "Auth service" as Auth
5
6Client -> GW : POST /login
7GW -> Auth : verify(credentials)
8Auth --> GW : token
9GW --> Client : 200 OK
10@enduml
Engineering wiki/Architecture/Auth flow
ClientAPI GatewayAuth serviceClientAPI GatewayAuth serviceClientAPI GatewayAuth servicePOST /loginverify(credentials)token200 OK
Fig 01 Real output from the public PlantUML server, shown in a stylized Confluence page frame.

Sec 01 · How it works

PlantUML for Confluence

  1. 01

    Insert the macro

    On any Confluence Cloud page, insert PlantUML from the slash menu — the same way you'd add a table or a status chip.

  2. 02

    Paste your source

    Drop your diagram text into the macro body. It's stored inside your page, like the rest of your content.

  3. 03

    Publish

    The app renders it as SVG — against the public plantuml.com renderer, or a private server your admin sets under Confluence settings → Apps → PlantUML.

Your diagram source stays in your page — it's stored in the macro body, not on Palori's servers, because there are no Palori servers: the app has no backend functions and no telemetry. The one thing it stores is your render-server URL, per site.

All of this is checkable — the code is source-available at github.com/paloriapps/plantuml-confluence.

What the app stores, what it doesn't, and where data travels at runtime: privacy · terms of use · changelog.

What's stored where
Diagram source
in your page — the macro body
Render server URL
the one stored setting, per site
Telemetry
none
Backend functions
none — nothing server-side to trust
Source code
github.com/paloriapps/plantuml-confluence

Sec 02 · Read the path

The render path is yours to read

PlantUML rendering has one architectural fact that matters: the diagram source is encoded into the URL sent to the render server. Whoever runs that server can see your diagrams. Most teams are fine with the public server; teams diagramming internal systems often are not.

This app treats that as your decision, not ours. The PlantUML server is an open-source project you can run from the official Docker image, and this app is source-available too — so the entire path your diagram takes, from macro to SVG, is code you can read and infrastructure you can own. The setup guide in the README covers the whole thing, including the CORS gotcha that catches most first-time server deployments.

your networkyour PlantUML server(official Docker image)Confluence Cloud page(source lives in the macro body)plantuml.compublic rendererGET /svg/{encoded}or point the app here
Fig 02 The render path — this figure is itself a PlantUML render. · Scroll the panel sideways for the full path →

Sec 03 · From the journal

Written for the engineer who has to make this work

Notes on PlantUML, diagram-as-code, and Confluence Cloud — not for the algorithm.

All articles →

Free · Source-available · No telemetry

Install it — or read it first.

Either door leads to the same code.

Get PlantUML for Confluence → Read the source →