Dotwork vs Ardoq
An independent, graph-based enterprise architecture platform with survey-driven data collection and AI assistance.
Ardoq is a graph-based enterprise architecture platform that keeps the architecture current through surveys and supports deep lineage, impact and scenario analysis. Dotwork uses a graph that extends past architecture into allocated cost, labor, investments and AI, so applications and capabilities can be priced and funded on one Enterprise Operating Model.
At a glance
Enterprise architecture
Ardoq
Operating model
Dotwork
Overlaps with
Dotwork runs these and 15 more on one model.
Connect it or consolidate it
Start by connecting it; consolidate when the model can carry the load.
The short version
What each is built for.
Ardoq
Ardoq is an independent enterprise architecture platform built on a graph. It collects architecture data through surveys and integrations, shows application portfolios as TIME assessments sized by cost, analyzes lineage and dependencies, and has added AI assistance, custom agents and temporal and scenario capabilities to its graph.
- Keeping an enterprise architecture model current through surveys and integrations
- Analyzing data lineage and the impact of changes across dependencies
- Showing application portfolios with TIME assessments
- Exploring architecture scenarios and how the landscape changes over time
Dotwork
Dotwork is an AI-native enterprise operating platform built on the Enterprise Operating Model: one live, graph-based model that connects strategy, capital, work, technology and AI across the enterprise. Like Ardoq, Dotwork uses a graph; its graph extends past architecture into allocated cost, labor, investments and AI spend.
- Pricing the application and capability portfolio from allocated cost
- Connecting architecture to strategy, investments, planning and AI on one model
- Showing labor, vendor and AI spend at application and capability level
- Supporting funding decisions that depend on the architecture
The core difference
How Dotwork and Ardoq approach the problem.
Ardoq and Dotwork both model the enterprise as a connected graph. Ardoq's graph centers on architecture and is fed by surveys and integrations, while Dotwork's graph starts from a reference Enterprise Operating Model in which architecture sits beside allocated cost, labor, investments and AI.
Context
Ardoq gathers context from the people who own applications and processes, through surveys and imports. Dotwork gathers context from systems of record, such as finance, HR, delivery tools and the architecture inventory, into one model.
Decisions
Ardoq helps architects answer impact questions: what depends on this, and what changes if it goes. Dotwork helps leaders answer funding questions: what a capability costs, which investments change it and whether that is worth it.
Time
Ardoq is adding temporal queries and scenario branching to its graph, so architects can compare past, current and future states. Dotwork holds plans, budgets and cost history on the same records, so architecture can be read against planning periods.
Change
Ardoq supports change through scenarios and impact analysis inside the architecture. Dotwork shows how a change connects to funded work, allocated cost and the controls it touches.
Architecture and data model
Side by side.
Both platforms treat the enterprise as a graph rather than a set of lists. Ardoq's graph is deep on architecture, with lineage, impact and scenario analysis. Dotwork's graph is broader, carrying the same applications and capabilities into allocated cost, labor, investments and AI spend so architecture can be priced and funded on one model.
| Dimension | Ardoq | Dotwork |
|---|---|---|
| Graph scope | Architecture: applications, capabilities, processes, data, technology and their relationships | Strategy, portfolio, capabilities, applications, teams, allocated cost, labor and AI assets |
| Data collection | Surveys to owners, integrations and AI-assisted import | Systems of record brought into the model through connectors, APIs and bulk import |
| Application cost | TCO used to size TIME views, from collected or imported cost data | The sum of allocated cost linked to each application, with the share of cost covered shown alongside |
| Lineage and dependencies | Strong data lineage and dependency impact analysis | Basic dependency analysis |
| Planning and portfolio | Architecture-led roadmaps and scenarios, with financial planning usually in other tools | Investment scoring, OKRs and a planning workspace as product features |
| Starting point | A flexible architecture meta-model with use-case templates | A reference Enterprise Operating Model, shaped to the customer |
The role of AI
Where the AI gets its context.
Both bring AI to a connected graph. Ardoq's AI focuses on building and maintaining the architecture model, while Dotwork's AI works across a model that also includes cost, funding and AI governance, so questions can cross those domains.
Ardoq
Ardoq positions itself as an AI-first EA platform, with an AI assistant, an AI import builder and custom agents intended to automate routine architecture work, grounded in the customer's architecture data.
Dotwork
Dotwork includes an assistant that answers questions across the whole model and agents that can create and update Dotwork records, with optional human review. An MCP server, enabled per site, makes the same model available to outside AI tools. Because the model spans strategy, cost, architecture and AI, a single question can cross those domains.
A fair comparison
Where Ardoq is strong — and where Dotwork is different.
Where Ardoq is strong
- Survey-driven data collection keeps the architecture current without relying on a small team of architects
- Data lineage and dependency impact analysis are deeper than Dotwork's
- A dedicated technical debt register is part of the platform
- TIME portfolio views sized by cost are an established, shipped feature
- AI assistance, AI import and custom agents aim to automate routine EA work, and temporal and scenario capabilities are being added to the graph
Where Dotwork is different
- Prices the portfolio from allocated cost, so the size of an application reflects the ledger cost linked to it, with coverage shown
- Extends the graph past architecture: the same applications and capabilities carry allocated cost, labor, investments and AI spend
- Includes planning and portfolio as product features, with investment scoring, OKRs and a planning workspace
- Shows the cost reaching non-conformant applications beside standards and controls
- Starts from a reference Enterprise Operating Model rather than a model built up for each customer
Choosing
Which fits your situation.
Choose Ardoq when
- You want application owners to keep the architecture current through surveys
- Data lineage and dependency impact analysis are central to your work
- You need a dedicated technical debt register inside the EA tool
- Your architects want to model and compare future-state scenarios
Architecture and transformation teams that want a data-driven EA practice, with survey-based collection, lineage and impact analysis, and scenario planning inside the architecture.
Choose Dotwork when
- You need application and capability cost based on allocated ledger cost
- Architecture must connect to investments, planning and strategy on one model
- You want AI assets and spend on the same records as the architecture
- Your architecture questions are mostly about cost and funding
Organizations that need architecture costed and funded on the same model as finance, strategy and AI, where the main question is what capabilities cost and which investments are changing them.
The bottom line
Choose Dotwork when you want to connect the enterprise across systems and silos — with a lower total cost of ownership.
One operating model across strategy, capital, work, technology and AI, instead of another tool to integrate, reconcile and maintain alongside Ardoq.
FAQ
Questions buyers ask.
Can Ardoq and Dotwork be used together?+
Yes. Some organizations keep Ardoq as the architecture practice tool and bring its application and capability data into Dotwork to connect it to cost, funding and planning. Others whose architecture need centers on capability cost use Dotwork for both. The right choice depends on how much architecture depth the team needs.
Ardoq also sizes applications by TCO. What is different?+
In Dotwork, application cost is the sum of allocated ledger cost linked to the application, shown with the share of cost that is covered. Ardoq can also bring in cost data. The difference is that Dotwork uses the same allocated cost it carries into capabilities, business units and investments.
Does Dotwork do dependency analysis?+
Yes, at a basic level. Ardoq is deeper on data lineage and dependency impact analysis.
Keep comparing
Buyers also compare Dotwork with
Be Decisive.Build Fast.Connect Everything.
Start ConnectingSolutions
Platform
Resources
© 2025-2026 Dotwork, Inc. All rights reserved.