Version History and Lifecycle Management
Create named version snapshots, manage entity lifecycles with active, planned, and deprecated states, and track architectural evolution across diagrams, graph diagrams, and documentation pages.
Built-in version history and lifecycle management are available for standard diagrams, graph diagrams, and Content Foundry pages. Version snapshots record the state of a document at a specific point in time. Lifecycle tagging marks individual elements as active, planned, or deprecated, giving teams a clear view of what exists today, what is coming next, and what is being retired.
Version Snapshots
Stamp a named version at any milestone to create a permanent record of the document state. Version snapshots are available for standard diagrams, graph diagrams, and Content Foundry pages.
Lifecycle Tagging
Every node in a diagram or model can carry a lifecycle status. This provides a clear, visual indication of architectural intent across the entire project.
| Status | Meaning | Visual Indicator |
|---|---|---|
| Active | The element is live and in production today | Default styling, fully opaque |
| Planned | The element is approved but not yet implemented | Dashed border or muted styling |
| Deprecated | The element is being phased out and should not be used for new work | Strikethrough or faded styling |
Lifecycle status is stored directly on each node in the model or diagram file. It is queryable, filterable, and propagates through derived views (ERD views, graph views, search views) automatically.
Succession Tracking
When an element is deprecated, NeoArc tracks where it goes next. Two edge types link deprecated elements to their successors:
Repoint Wizard
When deprecating an element, downstream references (schemas, diagrams, pages, endpoints) may still point to the old element. The Repoint Wizard migrates these references to the replacement.
Deprecation Reporting
Two reports help manage the deprecation lifecycle:
Page Versioning
Use Cases
Create architecture diagrams, ERDs, flowcharts, and network diagrams with icon libraries from Azure, AWS, Kubernetes, CNCF, Lucide and brand collections. Includes presentation mode with animated viewport transitions, infographic mode with canvas presets, version snapshots, architecture transitions, and full auto-layout.
Create interactive force-directed graph diagrams in three authoring modes: mindmap, conceptual, and graph-db. Graph-db mode adds typed properties with 12 abstract types, 6 key roles, per-property projections, composite constraints, and Cypher DDL export. Includes 18-rule validation, version snapshots, architecture transitions, group and tag filtering, and search. Graph-db mode also serves as the editing canvas for the project model (model.neoarc).
Model architectural roadmaps using lifecycle tagging on diagram elements. Mark shapes and connections as active, planned, or deprecated to represent current state, interim phases, and target architectures.
Model data model evolution with graph transitions. Document current schemas, interim states, and target entity relationships.