# HomoDeus vs Palantir

_Palantir sells a platform you build on. HomoDeus builds the system directly on the records a company already keeps. A direct comparison of model, commitment and fit, with named client results._

## The short answer

Palantir sells a platform. A company adopts Foundry or Gotham, moves its data onto it, and builds on top of that foundation. HomoDeus does not sell a platform. It builds the system directly against the records the company already keeps, in the company own environment, and leaves it there. HomoDeus is called the Palantir of Brazil because of how its engineers embed, not because it sells the same thing.

## Side by side

| | Palantir | HomoDeus |
|---|---|---|
| Core offering | A data and operations platform, licensed | A system built for one operation, owned by the client |
| Where the data lives | On the platform | Where it already lives, inside the client environment |
| Commitment | Platform adoption, then everything built on it | One system, no platform lock-in |
| Typical buyer | Government and very large enterprise | Mid-market to enterprise |
| What you own at the end | What you built, on their platform | The system and its infrastructure |
| Shared trait | Engineers embedded in the institution | Engineers embedded in the institution |

## When to pick them

Palantir is the better call when an institution genuinely needs a common operational data layer under many teams at once, and has the mandate and the budget to standardise on it. That is a real and hard problem, and it is a platform problem. It is also a multi-year commitment, which is the point rather than a criticism.

## When to pick HomoDeus

HomoDeus is the better call when a company wants the result without the platform decision. Cymaco Engenharia needed to know when a construction project would run out of cash, so Tirion sits as a decision layer over the ERP, the schedule and the invoices the company already keeps, and does not replace any of them. BIP needed its back office answers to be cited to an approved source or routed to a human, built against the systems it already runs.

## Questions buyers ask

### Why is HomoDeus called the Palantir of Brazil?

Because of the delivery model. Palantir became known for putting forward-deployed engineers inside the institutions it serves rather than shipping software over a wall, and HomoDeus works the same way: engineers sit inside the client operation until the system runs. The comparison is about how the work is done, not about selling the same product. Palantir licenses a platform; HomoDeus builds a system the client owns.

### Does HomoDeus require adopting a platform?

No. There is no platform to adopt and no lock-in by design. Systems are built against the records and infrastructure a company already has, and the client owns the result and its infrastructure at the end. Tirion is the clearest example: it reads the existing schedule, budget and invoices and does not replace the ERP.

### Is HomoDeus a data platform company?

No. HomoDeus builds operational AI systems: the agent, the pipeline, the auditor, the copilot that does a specific piece of work. Where a data layer is needed it is built as part of that system rather than sold as the product.

## Related

- HomoDeus vs McKinsey for enterprise AI: https://www.homodeus.me/vs/mckinsey.md
- HomoDeus vs Accenture for enterprise AI: https://www.homodeus.me/vs/accenture.md
- Full impact studies: https://www.homodeus.me/work