Dotwork vs Palantir
A data and AI platform, including Foundry and AIP, that builds an operational ontology over enterprise data and runs applications that act on it.
Palantir builds an ontology over operational data and runs applications that act on live systems, with the flexibility to model almost anything a customer needs. Dotwork starts from a reference Enterprise Operating Model of strategy, portfolio, cost, architecture and AI, and works as the management layer beside operational platforms such as Foundry.
At a glance
Data & operational intelligence
Palantir
Operating model
Dotwork
Overlaps with
Dotwork runs these and 13 more on one model.
Usually runs alongside Dotwork
Dotwork connects to it and puts its data in the context of the whole enterprise.
The short version
What each is built for.
Palantir
Palantir builds software platforms, including Foundry, AIP, Gotham and Apollo, that integrate operational data into an ontology of objects, links and actions. Customers use it to build operational applications and AI workflows that write decisions back into live systems, often with Palantir's forward-deployed engineers working inside their teams.
- Integrating large volumes of operational data into one ontology
- Building operational applications that act on live systems
- Running AI workflows and agents over operational data
- Operating in demanding environments, including classified and sovereign deployments
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. Dotwork works at the management layer, steering how the enterprise is funded and run, and is designed to sit alongside operational platforms such as Foundry rather than replace them.
- Steering strategy, portfolio and investment decisions across the enterprise
- Showing what capabilities, applications and AI cost, based on allocated cost
- Connecting architecture, standards and AI governance to funding
- Starting from a reference Enterprise Operating Model with management records already defined
The core difference
How Dotwork and Palantir approach the problem.
Palantir and Dotwork work at different layers. Palantir builds an ontology over operational data and acts on live systems, while Dotwork starts from a reference Enterprise Operating Model of strategy, portfolio, capability, cost and AI records and uses it to steer how the enterprise is funded.
Context
Palantir's ontology is built for each customer around the objects that matter to its operations, such as orders, assets, patients or shipments. Dotwork's model arrives with management record types already defined, including strategy, investments, capabilities, applications, allocated cost and AI assets, and is shaped to the customer.
Decisions
Palantir supports operational decisions and writes them back to source systems, such as dispatching, re-planning or assigning. Dotwork supports management decisions, such as what to fund, what a capability costs and where AI spend goes, and records them in Dotwork rather than writing to external systems.
Time
Palantir focuses on operational cadence, often measured in hours and days. Dotwork focuses on planning and funding cycles, with plans, budgets and investments held as records with history.
Change
In Palantir, new use cases are added by extending the ontology and building applications on it. In Dotwork, change starts from the reference model and is shaped through configured record types, fields and views.
Architecture and data model
Side by side.
Both platforms use a graph of connected objects. Palantir's strength is breadth: it can model and act on almost anything a customer builds. Dotwork's model is narrower and arrives defined for managing the enterprise, which is why the two usually run side by side.
| Dimension | Palantir | Dotwork |
|---|---|---|
| Starting point | An ontology built for each customer, often with forward-deployed engineering | A reference Enterprise Operating Model with management record types already defined |
| Core objects | Any operational objects the customer models, with links and actions | Strategy, objectives, investments, capabilities, applications, teams, allocated cost and AI assets |
| Actions | Writes decisions back into operational systems | Agents change Dotwork records; Dotwork does not write back to external systems |
| Cost and portfolio | Can be modeled when a team builds those objects and applications | Cost allocation, portfolio and strategy views are part of the product |
| Industry focus | Industry offerings focused on operations, such as hospital operations, manufacturing and procurement | Industry editions that model industry economics |
| Primary users | Operations teams, analysts and builders of operational applications | Strategy, finance, portfolio, architecture and technology leaders |
The role of AI
Where the AI gets its context.
Palantir's AI is designed to act inside operations. Dotwork's AI is designed to answer and update management questions across strategy, cost, architecture and AI governance.
Palantir
Palantir AIP brings large language models and agents into the ontology, so AI can reason over operational data and take governed actions in connected systems. AIP bootcamps help customers build working use cases on their own 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. Dotwork agents change Dotwork records only.
A fair comparison
Where Palantir is strong — and where Dotwork is different.
Where Palantir is strong
- Operational write-back: dispatching, re-planning, assigning and automating work in live systems
- A flexible ontology that can model almost anything a customer needs, including cost, when a team builds it
- Proven at scale for data integration and operational applications across large, complex estates
- Industry offerings in areas such as hospital operations, manufacturing and procurement
- Classified and sovereign deployment options, plus a forward-deployed engineering model that works inside customer teams
Where Dotwork is different
- Starts from a reference Enterprise Operating Model with strategy, portfolio, capability, cost, labor and AI record types already defined
- Includes strategy and portfolio as product features: strategy-to-investment trace, OKRs, investment scoring and benefits tracking
- Prices capabilities and the application portfolio from allocated cost and connects them to the investments that change them
- Connects architecture, standards and AI governance to cost and funding on one model
- Works as a management layer that reads operational signals and leaves operational systems in place
Choosing
Which fits your situation.
Choose Palantir when
- You need to act on live operational systems: dispatch, re-plan or assign
- You need to integrate and model large volumes of operational data
- You operate in classified or sovereign environments
- You want forward-deployed engineers to build custom operational applications
Organizations whose main opportunity is acting on operational data, in plants, hospitals, supply chains or missions where decisions must be written back into live systems.
Choose Dotwork when
- Your question is how the enterprise is steered and funded, not how an operation runs this week
- You want strategy, portfolio, cost, architecture and AI spend on one model
- You prefer to start from a reference operating model rather than build management objects from scratch
- You already run Foundry for operations and need a management layer beside it
Executive, finance, portfolio and technology leaders who need to steer how the enterprise is funded and run, and who want a management model with strategy, cost, architecture and AI already defined.
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 Palantir.
FAQ
Questions buyers ask.
Can Palantir and Dotwork be used together?+
Yes. They work at different layers. Foundry and AIP run operational applications and act on live systems, while Dotwork steers strategy, portfolio, cost, architecture and AI spend. Operational signals from Palantir can inform the management model. Dotwork does not replace Foundry.
Could we build this on Foundry?+
Yes. Foundry can model cost allocation, portfolio and capability objects when a team builds them. Dotwork starts from a reference Enterprise Operating Model in which those record types are already defined, and is shaped to the customer from there.
Does Dotwork take actions in operational systems?+
No. Dotwork agents create and update Dotwork records, with optional human review. They do not write to external systems. Operational write-back is a Palantir strength.
Keep comparing
Buyers also compare Dotwork with
Be Decisive.Build Fast.Connect Everything.
Start ConnectingSolutions
Platform
Resources
© 2025-2026 Dotwork, Inc. All rights reserved.