# Palantir and Mithandir: a shared vision of operational transformation

> Why we, the founders of Mithandir, take Palantir as a reference: connecting data, understanding processes and turning that knowledge into action. What we share, what we don't, and what we learn.

Field note No. 05 · Perspective · October 7, 2026 · 7 min read
By: Alfonso Ponzellini, co-founder and director at Mithandir · https://mithandir.com/en/blog/palantir-y-mithandir

## The starting point

Palantir and Mithandir share a central idea: technology creates value when it improves the way an organization works, decides and executes. Connecting information, understanding processes and turning that knowledge into action is the core of this comparison.

At Mithandir, we founders draw a lot of inspiration from Palantir. Personally, we love the company and take it as a reference for how to build technology solutions that are deeply connected to the client's reality. We are especially interested in its combination of engineering, business understanding and focus on operational results.

This admiration reflects an influence on our vision and methodology. The comparison does not imply a commercial relationship with Palantir, nor equivalence in platforms, capabilities or scale.

## What Palantir is and what problem it solves

Palantir is a software company founded in 2003 that began by developing technology for the U.S. intelligence community, for counterterrorism investigations and operations. Over time, it extended its reach to commercial organizations and other areas of the public sector. [1]

The problem it addresses is common in large organizations: there is a lot of data and many systems, but they are separated across departments, tools and teams. That fragmentation makes it hard to build a shared view and coordinate decisions.

Palantir integrates that data, ties it to operational reality and lets people build applications, analyses and workflows on top of it. Its offer connects three elements: available information, logic for deciding, and actions that change the operation. [2][3]

For example, an organization may know its inventory, its orders and its production capacity in different systems. By connecting those sources, it can detect which delivery is at risk, evaluate alternatives and coordinate a response. The value is in turning knowledge into the ability to execute.

## What it does for governments and multinationals

Palantir provides technology to governments and companies, adapting common capabilities to different operational contexts.

In defense and intelligence, it can help relate information, investigate situations, plan operations and coordinate resources. In other public areas, its capabilities are also applied to management and service problems.

In a multinational, the same logic can be applied to production, maintenance, supply, logistics and planning. Palantir documents applications in hospitals, airlines, energy, manufacturing and defense built on a common architecture. [3]

The goals and demands change depending on the client. A government may need to coordinate a mission; a company may need to respond to a supply disruption. In both cases, the difficulty is gathering the relevant information, understanding how it relates, and enabling a coordinated response.

## The platforms behind that offer

Palantir builds its offer around four main platforms: Gotham, Foundry, Apollo and AIP. [1]

Gotham is especially tied to defense and intelligence. Foundry offers capabilities to integrate and operationalize data. AIP connects artificial intelligence with operational processes. Apollo lets teams deploy and manage software across different environments.

These capabilities are combined: solutions for government and for enterprises use shared components and specialized applications. [3]

An important concept is Palantir's Ontology: a representation of an organization's objects, relationships and actions. It links technical data with the elements users recognize in their work, such as assets, orders, suppliers or resources. [2]

## What Mithandir does and why the similarity is real

At Mithandir we develop software, integrate systems and apply automation and artificial intelligence to specific business processes. Our work starts by understanding how the client operates and where delays, errors, repetitive tasks or coordination difficulties appear.

From that diagnosis, we connect existing tools and build the missing pieces: platforms, applications, integrations, agents and workflows. The solution has to become part of day-to-day operations and produce a verifiable improvement.

The similarity with Palantir shows up in five dimensions:

1. The client's problem guides the solution. Technology is chosen based on an operational need.
2. Integration is central to the work. The value depends on connecting systems and data that used to be separate.
3. The business gets translated into software. Customers, documents, suppliers, orders and rules become executable models and processes.
4. Information leads to action. The solutions let a workflow move forward, in addition to showing its status.
5. Development requires closeness to the client. Understanding the context, implementing and adjusting with real use is part of the delivery.

We share, therefore, a logic of operational transformation. The similarity is in the type of problem and the way of approaching it; the technological implementation has relevant differences.

## Engineering close to the client

Palantir describes its methodology as Forward Deployed Engineering: engineers deeply involved in the client's environment who solve real problems and feed that learning back into the evolution of the platforms. [3]

That approach is one of Mithandir's main references. We seek to understand processes together with the people who run them and to build solutions that work under the organization's real conditions.

Closeness demands technical judgment and business understanding. An initial request might be "we need a dashboard," but the real problem may be the quality of the data, a manual approval or an integration that doesn't exist. Solving it requires investigating the whole workflow.

Our resemblance to this model depends on keeping that responsibility for the outcome: mapping, building, supporting adoption and improving the solution with evidence of use.

## What it looks like in Mithandir's projects

The following examples illustrate the approach and the scope of the projects. They do not represent measured financial results, nor features that are necessarily complete in every case.

At Vinesco, the work on suppliers, invoices, vouchers and reconciliation aims to connect parts of a single administrative operation. The opportunity lies in relating documents and transactions to make controls easier and reduce manual work.

At BuildBuy, the workflow of orders, quotes, comparison and purchase orders aims to organize sourcing decisions. The goal is for the information to follow the whole process and let it move from a need to a purchase.

In real estate solutions like Claveo, connecting searches, properties, clients, communication and scheduling helps organize sales work and make follow-up easier. The integrations and tools for agents must operate within the permissions of each role.

These cases show the conceptual connection with Palantir: scattered data and fragmented processes become a more coordinated operation through software.

## Origins: a similar approach, different histories

Palantir's historical origin is tied to intelligence and national security. Mithandir's path is tied to business problems of integration, automation and development. They are not equivalent founding stories. [1]

The similarity is in the approach: building technology from the concrete problems of real organizations and using that learning to develop capabilities that can serve new implementations.

At Palantir, the relationship between fieldwork and platform is explicitly built into its methodology. At Mithandir, turning recurring solutions into reusable modules and products is part of the direction we want to consolidate. [3]

## The brand link to Tolkien

There is also a symbolic affinity. Palantir takes its name from the seeing-stones in Tolkien's work. Mithrandir is one of Gandalf's names and means "Grey Pilgrim"; Mithandir can be read as an adaptation of that reference. [4][5]

As a brand interpretation, the seeing-stones represent the ability to observe and understand a distant reality; Gandalf represents guidance, judgment and coordination in the face of complex situations.

That parallel goes along with our admiration for Palantir. It is a symbolic reading, separate from the technical and business comparison.

## The differences that bound the comparison

Palantir has its own platforms, which form the basis of its implementations. Mithandir combines third-party tools, its own development and vertical products. The difference includes the maturity of the platform, the infrastructure, the scope of the deployments and the requirements each organization can take on.

Sharing a methodology does not automatically bring the same guarantees of security, availability, governance or ability to operate critical environments.

For Mithandir, the strategic lesson is to strengthen a reusable base: connectors, data models, permissions, traceability, operational modules and tools for agents. Each implementation should contribute learning and capabilities to the next ones.

This way, custom work can feed common products and components. The quality of that reuse determines how far the model can scale without depending proportionally on more manual work.

## The thesis of the case

Mithandir shares with Palantir a vision of operational transformation: understanding how an organization works, connecting its systems and turning data into decisions and actions through software and artificial intelligence.

Palantir applies this approach through its own platforms in governments and large companies. Mithandir adapts it to specific business processes through integration, development and vertical products.

As Mithandir's founders, we personally admire Palantir and draw a lot of inspiration from the way it connects engineering with real problems. That influence is reflected in our ambition to build solutions that become part of the client's operation and improve its ability to execute.

The comparison holds up when it rests on that vision, that methodology and concrete projects. Our challenge is to consolidate the platform, the components and the operating discipline that turn that inspiration into a lasting advantage.

## Sources and scope

The claims about Palantir rely on public documentation. The description of Mithandir expresses our vision and the projects mentioned here; the comparison is a conceptual analysis, not an independent assessment of technical equivalence.

1. [Palantir, Annual Report 2025, Form 10‑K](https://www.sec.gov/Archives/edgar/data/1321655/000132165526000011/pltr-20251231.htm)
2. [Palantir, Ontology Overview](https://www.palantir.com/docs/foundry/ontology/overview/)
3. [Palantir, AIP, Foundry, and Apollo — architecture and Forward Deployed Engineering](https://www.palantir.com/docs/foundry/architecture-center/platforms)
4. [Palantir — origin of the name](https://en.wikipedia.org/wiki/Palantir)
5. [Tolkien Gateway, Gandalf — names and meaning of Mithrandir](https://tolkiengateway.net/wiki/Grey_Pilgrim)

---

More field notes: https://mithandir.com/en/blog · Talk to the team: https://mithandir.com/en#contacto