OPTIMIZED CORE · EVIDENCE, ENGINEERED.

Software that keeps the evidence behind operational decisions.

Optimized Core develops products for analytical review, freight operations, security oversight, communication, private assistance, connected workspaces, investigations and protected exchange. Each has a distinct purpose, with a shared emphasis on clear context, human judgment and responsible information use.

Pilot phase · first pilots: KANDOR CORE and Meridian · scope agreed per organisation

SHIPMENT RECORDFOR REVIEW
Document
Arrival notice attached to the shipment
Position
Arrival estimate awaiting confirmation
Review
Check the update against the source
Next step
Prepare an approved customer update
ILLUSTRATIVE WORKFLOW · OPERATOR REVIEW
MERIDIAN · Working view · Illustrative example, not a product screenshot

Products

A shared principle: the record keeps the evidence.

Each product serves a different team. KANDOR CORE and Meridian lead the pilot programme.

KANDOR COREGATHER · analytical intelligence

Analytical insight, with the reasoning in view.

For analytical, risk and operational decision-support teams

Scope by agreementExplore product
MERIDIANTRACK · shipment operations

Keep shipment flow clear, from document to handoff.

For freight forwarders and the teams coordinating their shipments

Scope by agreementExplore product
SENTINEL COREHOLD · security operations

Incident oversight, with evidence at the centre.

For security operations teams, site managers and service partners

Scope by agreementExplore product
OCMEMIT · communication workflow

Clear communication, from first draft to approved release.

For marketing teams, communication leads and the people reviewing their work

Scope by agreementExplore product
OCHREALIGN · federated workspace

Independent systems. A coherent way to work across them.

For organisations coordinating specialised systems and the teams responsible for them

Scope by agreementExplore product
PARAFDRAFT · private intelligence

Useful intelligence. Memory and permission under your control.

For individuals, professional teams and organisations that value control over their context

Scope by agreementExplore product
QUESTEREXAMINE · investigation workbench

Complex investigations, with the context intact.

For investigation, risk and operations teams

Scope by agreementExplore product
NEW ERA OF PRIVACYPROTECT · protected communication

Private interaction, with boundaries people can understand.

For individuals, organisations and partners evaluating private communication workflows

Scope by agreementExplore product
Explore the products
The product instruments · A shared visual language for distinct roles · Concept illustrations
What we build
Operational software in which every material fact keeps its source, its time and its approver.
Products
Products in one family. KANDOR CORE and Meridian lead the pilot programme.
Stage
Pilot phase. Products are delivered through scoped pilots, agreed per organisation.
People
JPH van Mastrigt is the contact for technical questions.

The problem

Operational decisions rest on scattered, hard-to-verify information.

Scattered inputs

Emails, PDFs, portal screens and spreadsheets each hold part of the picture, and people match them by hand.

Conflicting versions

Teams, customers and suppliers work from different states of the same case, so every question triggers another check.

No reconstructable record

When something goes wrong, it is hard to prove what was known, when it changed and who approved it.

Every Optimized Core product answers this the same way: each material fact keeps its source, its timestamp and its reviewer.

How it works

Four questions every material fact can answer.

The same principle runs through all products. Each step below shows one example from a shipment record.

  1. Source

    Identify the origin and time of an observation. Example: an estimated arrival taken from an arrival notice, page 1.

  2. Record

    Connect relevant information without losing its context. Example: observed at 11:05, recorded at 11:07, linked to the shipment.

  3. Review

    Make uncertainty and the human review step explicit. Example: an operator approves the extracted date, and the approval is stored with it.

  4. Decision

    Agree what must be retained to examine a decision later. Example: the earlier date is kept and marked as superseded, not overwritten.

Read the full approach

Working with us

A pilot in three steps.

No data is shared and nothing changes in your operation before scope and readiness are agreed.

  1. Talk

    A first conversation establishes fit: your team, the workflow and the questions a pilot must answer.

  2. Agree

    We agree sources, permissions, review steps, retention, access boundaries and success criteria in writing.

  3. Evaluate

    A bounded pilot runs beside your existing tools, read-only where possible, with a defined way back.

Discuss a pilot

Security and control

The same controls in every product.

Every product is built on the same six controls. Implementation details are shared under agreement, not published.

  • Each organisation’s data is kept separate.
  • Roles limit what each person can see and do.
  • Sign-in requires a second factor.
  • Every material action is logged and attributable.
  • Exports are controlled and recorded.
  • Offboarding and retention are defined before access.

Ask for the security summary relevant to your pilot.

THE COMPANY

The people behind the products.

Optimized Core develops software for market analysis and shipment operations. Contact us to discuss technical evaluation, pilots or partnerships.

  • JPH van Mastrigt
    Founder & Technical Director

    Technical direction, architecture discussions and review of product claims and evaluation scope.

    j@optimizedcore.tech

Questions investors and clients ask

Straight answers.

How do we get access to a product?

Through a scoped pilot. We agree the workflow, sources, review steps and success criteria first; access follows the agreement.

Do you publish customer names or results?

No. Pilot outcomes are measured against an agreed baseline and shared with the participating organisation. Publication requires its permission.

What does a pilot involve?

One workflow, agreed sources and permissions, explicit human review steps and written success criteria. The pilot runs beside your existing tools and can be reversed.

Who owns the data during a pilot?

You do. Data scope, retention, export formats and offboarding are agreed in writing before access.

Does the software act on its own?

No. In every product, automation proposes and a person decides. KANDOR CORE, for example, never executes trades or holds assets.

Who is behind Optimized Core?

JPH van Mastrigt leads technical direction. Contact us for product, pilot or partnership questions. Contracting details are shared on request.

Which languages and regions do you support?

This website is available in eight languages. Product languages, regions and support are agreed per organisation.

Start with one workflow.

Describe your team and the workflow you want to evaluate, with an anonymised example if you like. We discuss scope, connections and readiness before any data is shared.

JPH van Mastrigt · Founder & Technical Director