Community Requests

It would be nice to be able to relate ARDs to domains and objects rather than just diagrams.

All REST API and MCP writes go directly to latest — there's no way to scope them to a draft for review before merging. We run automated C4 migrations and AI agents (via MCP) that create dozens of objects, connections, and diagrams at a time. Without draft targeting, we rely on version snapshots as a safety net instead of the built-in draft review/merge workflow. Request: Accept an optional draftId parameter on model object, connection, and diagram content write endpoints so changes land in a draft and are mergeable via UI or POST /drafts/{draftId}/merge. Tested (v1 API, April 2026): Using the draft's versionId in the URL path, draftId as a query param, and draftId in the request body all either silently go to latest or return errors. MCP server lists draft tools as unsupported.

useful for visualizing protocols (http, events, SSL, etc)

Allow connection curves and points to be controlled. Like draw.io (but better). Even small controls would help with overlap issues.

Add C4 level to the 'In diagrams' dropdown list, displayed in object side-panels. This helps with identifying the correct diagram faster when this list is large.

We use a context diagram to show our system landscape, but it somehow appears in the same hierarchy as other context diagrams that represent a single system. Would be nice to have a "level 0" support https://c4model.com/diagrams/system-landscape

Hello IcePanel Team, I would like to request the addition of an auto-layout feature to IcePanel. This feature would greatly enhance the usability and efficiency of the tool by automating the arrangement of elements within the diagrams. Currently, manual layout adjustments can be time-consuming, especially for complex models with multiple components, containers, and relationships. An auto-layout feature could simplify this process, ensuring: Clear and Consistent Layouts: Automatically aligning elements for better readability and uniformity. Time Savings: Reducing the time spent manually positioning elements, particularly during iterative updates. Scalability: Making it easier to work with large and complex systems by maintaining an organized structure. Kind regards

It's difficult to maintain visibility of architecture diagrams in Confluence. Currently, we use an iframe-based approach that requires opening IcePanel, generating a share link, switching back to Confluence, inserting the iframe, and manually configuring parameters. This is time-consuming, error-prone, and limits adoption. Request to build a native IcePanel plugin for Confluence (like the Miro plugin) Feature details: * From within Confluence, provide a UI modal to browse and select diagrams from IcePanel spaces the user has access to. * Support for an embeddable iframe view of a selected IcePanel diagram. * Navigation to the source in IcePanel * Full-screen viewing

Linking model objects to the ServiceNow (or other CMDB) object(s) to help with keeping people informed and also keeping model inline with reality.

A way to request for approvals on a diagram from other team members.