Quant8
Book a briefing

Forward deployed teamForward deployedGovernance reviewGovernanceCost reviewCost

Can you prove who controls your Foundry platform?

An independent review against 32 controls in 8 domains. One result that you can show a board, an auditor or a regulator.

Book a briefing See the eight domains

What you get

An answer to one question. Is this platform under control?

You receive a report, a plan with owners and dates, and a certificate of review. Every score rests on evidence.

See a sample report

Instead ofA self-assessmentAssurances by emailAnswers nobody signed

Check your own platform

Ten questions an auditor could ask.

Tick each one that your platform owner could show today.

0Shown today, of ten

  1. Fewer than sevenThe review is worth asking about. It ranks each gap by the harm it could cause.
  2. Seven or moreYou are close. The review lets you prove it to a board, an auditor or a regulator.

Send these answers with a briefing request

The eight domains

Eight domains, and the question each one answers.

Ownership and decision rights

Who approves a change, and is that written down?

Ontology structure and change control

Does each business object exist once, and how does it change?

Identity and access

Who can sign in, and what can contractors do in production?

Data classification and protection

Is sensitive data marked where it enters the platform?

Automation and outbound actions

Does every automated message leave a record? Can it be stopped?

Connections and data movement

Which outside systems can the platform reach and write to?

Timeliness and reliability

Are time targets defined and measured?

Audit, evidence and third parties

Do audit logs reach security monitoring?

How it runs

Four steps to a signed result.

Step 1

Agree the scope

We confirm what is in scope, and that we are independent of the people who built it.

Step 2

Test each control

We ask, look, test and collect evidence. Your own staff run any test that changes state.

Step 3

Score and certify

A second reviewer checks every score against its evidence. We present the result first, then the findings.

Step 4

Close and test again

We test each condition again after its due date.

Where it fits

Who it is for, and what it needs.

Who it is for

The CIO, the chief data officer or the platform owner of an organization that runs Foundry in production.

When it fits best

Before an audit or a renewal.

Before a second ontology, the model of your business objects.

Before the first automation that acts by itself.

When the vendor's engineers hand the platform to your own team.

What it needs

Read-only access for two reviewers. Interviews with the people who run the platform. Documents that already exist.

What it leaves

A dated list of conditions. The reviewers do not design the fix, so the list is work for your delivery team.

How we keep it independent

Nobody reviews work that they built. We certify no platform that we, or a firm we work under, built or run.

Read only. We change nothing on the platform.

Evidence is graded. A top score needs evidence that we saw ourselves.

No waiting. A live exposure is reported on the day we find it.

What it is not

Not an ISO 27001, SOC 2 or regulatory certification, and not a replacement for one.

Not a penetration test.

Not a review of the platform vendor's own infrastructure.

Questions people ask

Eight answers about the review.

Is this an audit?

No. It is a review against a written standard, and nothing on the platform changes.

Will it slow our delivery?

No. The review changes nothing on the platform. It needs about ten interviews, and documents that already exist.

The vendor's engineers already look after the platform. Why a review?

They build and extend it. This is an independent check of what already runs, by people who did not build it.

Who does the review?

Two Quant8 reviewers, and the second checks every score against its evidence. Most of our engineers came from Palantir, which is why we know the platform. Quant8 is independent of it, which is why you can rely on what we find.

Does the review cover AIP?

Yes. AIP is the set of AI tools that Palantir adds to Foundry. When it runs in production, the review adds tests for it: which models are enabled, what each agent can read, and whether an agent can change data or send anything without a person approving it.

Who fixes what the review finds?

Your delivery team. The reviewers design no fix: a finding says what must be true, not how to build it. We test each condition again after its due date.

Could we do this ourselves?

You can, and we hand over the method. With us you gain time, and a result that is independent of the team that built the platform.

What if you find something serious?

You hear on the day we find it. A live exposure does not wait for the report.

Name one decision.

Tell us the decision you must defend this year, or the Foundry platform you want an answer on. We start there.

Book a briefing James replies to you himself.

Book a briefing

Name the decision or the platform you have in mind. James replies to you himself.