Start from existing sources
Analyze code dependencies, turn SQL DDL into an ER diagram or import Markdown, CSV and API specifications. SQL is never executed; infrastructure imports do not query clusters, providers or state.
DIAGRAMORA · LOCAL-FIRST CODEX PLUGIN & DIAGRAM EDITOR
Turn an idea into a diagram. Turn the diagram into a decision.
Transform natural language, source code, SQL and documents into editable diagrams. Diagramora connects a local editor with Codex tools to understand structures, make focused changes, validate them and share them with clear format boundaries.
For architecture teams, developers, process owners and anyone who needs to explain relationships.
Local editor and MCP tools · 57 diagram types · Optional cloud integration requires setup
From the first draft to a traceable handoff.
57 types, one editor
Architecture, UML, BPMN, data models, planning, business analysis, charts, whiteboards and wireframes. Editable templates provide a starting point; pages connect overview and detail.
Control changes
Edit nodes, ports, connections, labels and tables directly. Layouts respect fixed positions; local versions, comments and semantic code diffs make changes reviewable.
Make quality visible
Local validation and quality review highlight structural, semantic and layout issues. Source provenance helps explain results; safe repair actions are available for deliberate selection.
Work locally
Local editing never uploads documents automatically. The editor persists locally and synchronizes local open tabs. Cloud storage and external AI endpoints require explicit configuration and deliberate actions.
Choose the right handoff
SVG, PNG, PDF, editable PowerPoint and documentation, plus Mermaid, draw.io, DOT, PlantUML, BPMN and Excalidraw. Format checks and machine-readable fidelity reports explain retained, degraded and unsupported fields.
ARCHITECTURE INTELLIGENCE
Architecture Intelligence: Turn the model into a decision resource.
Eight capabilities use the relationships and metadata in your local diagram. Insights are bounded by the maintained model; they do not replace measurements of your actual systems.
Ownership & rules
- Architecture Control Center
- Keep owner, system, runbook, runtime status, cost, latency and process duration on components.
- Architecture Contracts
- Evaluate declarative rules for ownership, runbooks, states and topology locally with CI-friendly tooling.
Scenarios & causes
- Scenario Lab
- Model an outage, latency or cost shock. Select the modeled blast radius and retain the result as a decision note.
- Causal Explainability
- Explain the shortest modeled causal path and relevant risk factors between elements.
History & decisions
- Architecture Time Machine
- Read local versions as a semantic change chronicle and restore an earlier state.
- Decision Receipts
- Record decisions, assumptions, status and affected components as portable Markdown evidence within the document.
Portfolio & actions
- Portfolio Risk Radar
- Rank up to 50 local diagrams using recorded runtime failures, governance debt and dependency bottlenecks.
- Remediation Planner
- Create a local P0–P2 action plan. The plan never changes the diagram automatically.
Create architecture diagrams from code: start with a focused scope.
Select the source files for one module and name the view you need, such as module dependencies. A focused scope makes provenance and missing relationships easier to review.
Analyze these TypeScript files and create an architecture diagram of module dependencies. Show source provenance and identify assumptions not established by these files.
Check components and connections against the source files. Deliberately add external systems missing from the sample; a code sample does not automatically describe the complete runtime architecture. Lock reviewed positions and inspect later code changes as a proposed semantic diff. Save editable Diagramora JSON before sharing.
Concrete tasks instead of an empty canvas.
Architecture from code
“Analyze these TypeScript files and draw the module dependencies.” Review source provenance, lock positions and inspect later code changes as a proposed semantic diff.
Data and interfaces
“Create an ER diagram from this SQL DDL.” Edit tables and references or import OpenAPI as an integration diagram; request credentials, headers, scripts and bodies are not rendered.
Explain processes
“Create a BPMN diagram for order processing.” Refine steps, lanes and gateways in the editor; use validation and comments for stakeholder review.
Explain change decisions
“What depends on this gateway?” Explore modeled impacts, compare scenarios and document the decision with its assumptions in Markdown.
Clear boundaries make results useful.
Local planner and Codex AI
The editor uses a deterministic local planner for drafts and local natural-language edits by default. LLM-assisted code, SQL or document analysis uses Codex Chat and MCP, subject to Codex data-processing settings. An optional editor AI endpoint requires explicit setup and confirmation for each request.
JSON as the editable source
Diagramora JSON is the canonical versioned document with pages, ports, metadata and provenance. Foreign formats can lose information. Review the specific export boundaries; complete BPMN, UML and C4 semantic rule sets remain planned.
Self-managed collaboration
Cross-device work requires the optional token-protected relay within a trusted network. You configure roles, identities and optional snapshot storage. Revision checks and conflict previews support deliberate merges.
Add cloud deliberately
Cloud storage and subscriptions are technically prepared and require a configured deployment. Local editing has no automatic upload. Managed AI credits, team invitations, live cloud collaboration and durable cloud history remain future services.
Start with your own diagram.
- 01
Prepare the environment
Provide Codex with the enabled Diagramora plugin and local MCP server for the Codex workflow. The server uses the bundled local Node runtime; editor development requires Node/npm and the repository.
- 02
Choose one source
Bring a focused process, supported source files or an existing diagram. Establish access and processing requirements for Codex beforehand.
- 03
Review the result and handoff
Review structure, provenance and assumptions together. Save the canonical JSON and evaluate fidelity for your intended export format.
Before getting started
Do I need a cloud account?
The local editor and local MCP tools do not require a Diagramora cloud account. Codex is needed for the plugin workflow. Optional cloud features require a configured cloud environment and, where applicable, sign-in.
Is Scenario Lab a monitoring system?
No. Scenario Lab models effects from represented relationships and metadata. It does not observe running systems or verify actual outages or measured values.
Is every export fully editable?
Diagramora JSON preserves the canonical model. Other editable formats may lose details; image and PDF outputs are visual handoffs. Check the format report for ports, layout, styles, metadata, comments and pages.
How does team collaboration work?
Local tabs synchronize without a network upload. For multiple devices, configure a self-managed relay with tokens and editor/viewer roles. It belongs behind a trusted network boundary and is not a public managed team backend.
How are setup and terms agreed?
We review your use case, installation state, suitable sources and support needs. Scope and terms are agreed individually; prepared cloud subscriptions do not promise an already operated public service.
Which relationships would you like to make clear?
Bring code, a data model or a process. Together we evaluate the local workflow, the diagram types you need and an appropriate handoff.
Discuss getting started