The problem was never a shortage of data.
IPAC exists because the gap in high-consequence work is not detection. It is the distance between knowing something changed and being able to act on it in a way that survives review.
The pattern repeated across every environment we worked in. A team had more inbound signal than it could read, several systems that each held part of the answer, and a decision that had to be made before a review date and explained a year later.
The tooling on offer solved the first problem and ignored the third. It aggregated, visualized, and alerted. Then it handed the judgment back, with no record of what had been known at the moment the call was made.
So IPAC was built from the decision backwards. One engine that ingests the sources, resolves them to the entities you actually operate, scores the exposure against a baseline that means something for flight hardware, recommends an action with a confidence and a cost of waiting, and binds the whole thing to the evidence it stands on.
The reasoning outlives the moment it was made in. That is the product.
What we hold to.
- The output is the decision, not the dashboard.
- Presenting data back to an operator moves the work. It does not finish it. The useful output is a named action with its confidence and the cost of waiting.
- A recommendation without evidence is just another opinion.
- Every recommendation should carry the record it was made on: versioned, reviewable, and still intact months later when somebody asks why.
- Trust should survive leaving the platform.
- Some claims have to hold for people who will never log in. That is the entire reason the verification layer exists.
- Say the limit out loud.
- No SSO. No ISO 27001. Not an export-control enclave. An internal hash chain, not a ledger. A buyer finds all of this eventually. The only question is whether they hear it from us first.
Built by operators. Powered by SGS.
IPAC is developed by Schubring Global Solutions. SGS works across security, risk, intelligence, and technology for organizations operating where mistakes are expensive and explanations are mandatory. IPAC is pointed at one of them: space and aerospace hardware, where a readiness call is signed before a window and examined long after it.
That background is why the product is shaped the way it is. Someone who has had to defend a decision in front of an auditor builds an evidence vault differently from someone who has only had to demo one.
SGS is the company behind IPAC. IPAC is not a service line inside SGS. The platform stands on its own, and is intended to move to its own home.
What we will tell you in the first conversation.
- What IPAC will and will not hold, including the export-control boundary, before you ask.
- Whether the decision you described is one IPAC would actually have caught earlier.
- The controls we do not have, before you ask for them.
- If the answer is that you do not need this yet.
Tell us about the hardware and the call you keep making late.
Reach us directly at [email protected], or send the detail through the form.