You adopt a platform and build the operating model, the applications and the workflows on it.
Palantir, workflow buildersYou hire an AI employee, brief it, review its work and approve what it proposes.
Viktor, agentsWe start with the economic opportunity, record a baseline, build and run whatever it takes, and measure the result in your own systems.
AmalgamentWhat Palantir is
From their own site, read 2026-09-17
- Foundry's Ontology is described in Palantir's documentation as "an operational layer for the organization" that maps data sources into objects, properties and links, with action types and functions to change state under organizational controls.
- AIP adds builder tools, named in the docs as AIP Logic, AIP Chatbot Studio and AIP Evals, for building "production-ready AI-powered workflows, agents, and functions on top of the Ontology."
- The documentation is written for the organization's own builders: data engineers, application developers and operators.
Our read
Palantir is an enterprise operating platform. An organization adopts it, models its data, decisions and actions in the Ontology, then builds operational applications, workflows and agents on top, usually with a dedicated implementation team. It is deep, governed and powerful, and it is designed for complex environments with the people to run them.
This page is a conceptual contrast. Amalgament does not claim to be technically equivalent to Palantir, and small businesses are not Palantir's market. What the two share is a philosophy: the business should have an operating model, and work should run on top of it.
What Amalgament is
Amalgament builds systems that improve the economics of a business. We measure the work in customers created, revenue created and cost removed.
We start with the economic opportunity, not the technology. Scout finds demand the business is not capturing and turns it into customers. Forge finds revenue inside the customers, capabilities and relationships the business already has, then builds the offer and the system that make it real. Sift finds recurring cost that can be removed without losing the capability behind it.
Before we build, we record a baseline. Then we build and run whatever combination of software, AI, data, automation and execution the opportunity requires, and measure the result in your own systems of record. You never have to choose the technology.
Customers created. Revenue created. Cost removed.
Side by side.
Text, not checkmarks. Where both do a similar thing, the row says so.
- What you buy
- PalantirA platform. Your organization builds the operational model, the applications and the workflows on it.
- AmalgamentA result: customers created, revenue created or cost removed, with the systems built to produce it.
- Who builds the operating model
- PalantirYour data engineers and builders, often alongside an implementation team.
- AmalgamentWe do, as much of it as the opportunity needs. You never have to learn it.
- Who operates it
- PalantirYour organization, day to day.
- AmalgamentWe build and run what the result requires. You keep working in the tools you already use.
- Who builds the workflows and agents
- PalantirYour builders, using the platform's tools.
- AmalgamentWe do, when the opportunity calls for them. Sometimes the answer is simpler.
- Customer software burden
- PalantirSignificant. It is a platform to learn, administer and govern.
- AmalgamentNone. There is no platform for you to learn.
- Implementation model
- PalantirA project, with the organization's team engaged throughout.
- AmalgamentFind the opportunity, record a baseline, build, measure. You answer questions about your business.
- Human accountability
- PalantirInside the customer organization.
- AmalgamentAmalgament, for the result against the agreed baseline.
- Core unit of work
- PalantirThe operational model: objects, decisions and actions.
- AmalgamentThe economic result, measured in your own systems of record.
- Scale of organization
- PalantirEnterprises and governments with complex data and the staff to operate a platform.
- AmalgamentSmall businesses that need the outcome without the platform.
- Commercial model
- PalantirEnterprise agreements.
- AmalgamentScoped to the opportunity and agreed before work starts.
- Best fit
- PalantirOrganizations that want to own and operate a deep operating platform.
- AmalgamentOwners who want the economics of the business improved without owning a platform.
The unit of work.
A similar idea underneath. The difference is who builds it and what it is measured by.
The organization models the customer, the order, the exception and the decision, then builds the application that acts on them.
We look at your customers, jobs, invoices and costs, find where the economics can move, and build what moves them. You never see the model. You see the result in your own CRM, invoices or payments.
Which one, honestly.
- You are a large organization with complex data and a team to operate a platform.
- You want to own the operating model and build your own applications on it.
- Governance, security and scale requirements come before speed of setup.
- You run a small business and want its economics improved, not a platform to run.
- You have no internal technical team and do not want one for this.
- You want a result measured against a baseline, without an enterprise project.
A few good questions.
Start with the opportunity. Measure the result.
Keep your tools. We find where the business can win customers, add revenue or remove cost, record a baseline, build what it takes, and measure the result in your own systems.
Sources, read 2026-09-17: Palantir docs: Ontology overview, Palantir docs: AIP overview. Descriptions of Palantir are our reading of public material on that date and may be out of date; we do not make claims about accuracy, reliability or pricing beyond what is shown there.
Other comparisons
