Live nodes
Every app and database in scope shows up as a card with status, CPU, RAM and address. Click it and the side panel opens the resource's real tabs: overview, logs, snapshots, settings.
Vertra Flow · Beta
Apps and databases become live nodes on a canvas, with real state and usage. Group by product, attach what belongs together and leave a note where the decision was made.
Freeze de deploy até o PIX liquidar.
Flow is not a drawing exported from your infrastructure. Each card is the actual app or database, with the same status, CPU and RAM the overview shows.
Every app and database in scope shows up as a card with status, CPU, RAM and address. Click it and the side panel opens the resource's real tabs: overview, logs, snapshots, settings.
Gather cards by product, environment or team. Collapse a group to cut the noise without hiding the architecture; the color is yours, so is the name.
A dotted line documents that two things relate. It organizes understanding; it never opens a port or creates a network.
Sticky notes in seven colors, next to the resource they refer to. A deploy freeze, a pending item, the reason behind a limit.
An app's published page open inside the map, next to its card. Refreshes while visible and opens the public URL in one click.
A minimap to drag the camera, search by name with ⌘F, undo and redo to move, group and attach without fear.
The canvas starts with the projects in scope. From there, it's organizing.
A note or a preview of a published app, from the Add menu in the header.
Drag cards into a group.
Select an item, click Attach, then click the target. The numeric badge shows and removes attachments.
The layout lives in the browser of whoever organizes it, separated by account and by workspace. The resources are shared, the arrangement is yours.
| Groups per canvas | 12 |
| Notes per canvas | 10 |
| Previews per canvas | 3 |
The canvas is view-and-pan: tapping opens the resource sheet, the floating button gathers move, group, note and search. Deep organizing is big-screen work.
Flow is part of the dashboard, on every plan.
Today each person organizes their own canvas. What comes next is not available yet.
Cursors, presence and synchronized edits to investigate and organize the same canvas at the same time.
Discussions pinned to a card or a group, with mentions, without separating the conversation from the infrastructure.
The workspace layout stored on the server, the same for every member, instead of one per browser.
The essentials before opening the canvas.
No. Groups and attachments are visual organization. A line between an app and a database opens no port, creates no private network and injects no environment variable. Vertra has no private network between services; an attachment documents a relationship, it doesn't create one.
Yes. Apps and databases in scope appear as nodes with the same status and usage as the overview, and the side panel opens the resource's real tabs. Note and preview are not resources: they are canvas items.
In the browser, per account and per workspace. Switching machines or clearing site data starts a fresh canvas; the projects stay, only the arrangement is lost. Server-synced arrangement is in the next steps.
No. Flow is part of the dashboard on every plan.
Not yet. In a workspace, every member sees the same projects on their own canvas, but each one organizes their own. Presence, cursors and shared arrangement are the next steps.
In your dashboard
Open Flow and group what's yours.