Execution governance · South African developed

Govern infrastructure.
Control financial execution.

One Castle OS platform connects authority, policy and evidence to the actions that move money and change systems. Put a defined decision boundary between a request and its consequence.

For finance leaders, infrastructure teams and the engineers building enterprise automation.

Independent policy evaluationHuman, API, workflow or agent-initiated actionsDesigned to complement your existing systems
01 / The missing question

Access is only
the beginning.

A valid credential answers who can enter. The next question is whether this particular action is permitted, under these conditions, right now.

01 — AUTHORITY

May this actor do this?

Evaluate the supplied role, delegation and transaction value against a configured authority rule.

02 — CONTEXT

Do the conditions hold?

Check relevant facts and required evidence. A document being present is not the same as a control being satisfied.

03 — DECISION

What should happen next?

Return a policy decision before the selected integrated action commits, with a reason that can be reviewed.

02 / Explore the boundary

Change the facts.
See the decision.

Try three simplified scenarios. These browser simulations illustrate the concept; they do not call the Castle OS engine or move money.

CASTLE OS / DECISION EXPLORERILLUSTRATIVE DATA
Proposed action

Release a supplier payment

The actor has access to payments. Their configured approval limit is R100,000. Access alone does not authorise every amount.

R150,000
Illustrative delegation limit: R100,000
Illustrative policy decision
BLOCK

rule
mode
path action
downstream outcome not observed in this simulation
A PASS is a policy decision, not proof of execution. Review routing and blocking behaviour depend on the implemented integration.
Unified platform architecture

Two solution pillars.
One governance core.

Choose the business exposure. We define the controls, integration and acceptance evidence with your team.

01 / PEIG

Pre-Execution Infrastructure Governance

Make authority and recovery readiness conditions of high-impact infrastructure changes.

  • Evaluate operation scope and target-resource authority
  • Assess recovery-point age and required protection evidence
  • Govern selected mutations through an integrated execution boundary
Explore PEIG →Connector design and delivery scope →
02 / PEFG

Pre-Execution Financial Governance

Bring transaction-specific controls to financial commitments, supplier changes and payment requests.

  • Map ERP, P2P and procurement records into defined facts
  • Evaluate delegation, supplier verification and duplicate indicators
  • Apply approved controls on integrated payment and change workflows
Explore PEFG decisions →Scope a financial-governance evaluation →

Shared foundation: policy configuration, ReasonGate evaluation, enforcement integrations and decision evidence. View component status and delivery scope →

03 / Where it matters

Different systems.
Consequential decisions.

Start with one action and a control that matters. Establish the data, policy and integration needed to evaluate it.

[ → ]

AI & automated actions

Permission to use a tool should not become unlimited permission to act.

  • Agent-initiated payment requests
  • Approved action scope
  • Evidence before a write action
Explore an agent use case →
[ ≡ ]

Procurement & payments

Make the transaction-specific question visible before resources are committed.

  • Delegation-of-authority checks
  • Supplier banking changes
  • Duplicate-payment indicators
Scope a transaction control →
[ ◎ ]

Audit & forensic review

Move from recurring findings to a focused examination of the underlying control.

  • Historical transaction evaluation
  • Evidence and data-quality gaps
  • Exceptions for practitioner review
Discuss a historical diagnostic →
[ ⌁ ]

Infrastructure & recovery

Make recovery readiness a condition of high-impact infrastructure changes.

  • Authority for the exact operation
  • Recovery evidence for the target
  • Defined handling for unmet conditions
Explore recovery-aware governance →

Veeam integration proposal · technical validation

Infrastructure governance

Before the change.
Check the recovery conditions.

An approved change can still carry unacceptable recovery exposure. Connect authority, action scope and recovery evidence at the decision boundary.

Proposed Veeam integration. Define the workload and validate the evidence with us.

04 / Your route to deployment

Find the exposure.
Put controls to work.

Choose the entry point that fits your workflow: historical assessment, live observation or an integrated enforcement engagement.

START HERE

01. Historic Shadow

Evaluate an agreed historical sample against selected controls. Surface exceptions and identify what cannot be verified.

Agree the dataset, data dictionary, policy versions and evidence requirements. A 90-day sample can be a starting scope.
OBSERVE

02. Live Shadow

Observe selected live requests and record how configured rules would respond, without applying their blocking effect.

Validate mappings, rule behaviour and operational impact with the people accountable for the process.
ENFORCE

03. Active Enforcement

Apply approved policy decisions on the integrated execution path before selected actions reach the receiving system.

Define failure behaviour, authorised exceptions, operating ownership and rollback before activation.
05 / Know what the record proves

Approved.
Executed.
Evidenced.

Three different questions. A governance decision explains whether an action was permitted under the evaluated policy. Establishing what happened next requires outcome evidence.

ReasonGate connects policy to the execution boundary. Explore the architecture and delivery roadmap for policy management and downstream outcome evidence.
01

The decision record

Submitted facts, effective policy and rule version, evaluation mode, decision and reason. The record is bounded by the information available at evaluation time.

02

Commit Adapter PLANNED

Link evidence from receiving systems to distinguish permission from a confirmed downstream outcome.

03

Causation Record PLANNED

Connect instruction, authority, decision and recorded outcome, while keeping evidence gaps visible.

04

Control Plane PLANNED

Manage policy lifecycle, approvals, deployment states and exception workflows around the decision engine.

06 / Clear boundaries

Good questions.
Direct answers.

Trust starts with understanding what a control can—and cannot—establish.

Does Castle OS replace our ERP or identity platform?

No. Your existing systems retain their roles. Castle OS is designed to add an independent policy decision for selected integrated actions. Compatibility and enforcement coverage must be established for each deployment.

What can we evaluate first?

Start with a focused historical diagnostic or a technical demonstration of the policy boundary. Live deployment is scoped around your systems, approved controls and acceptance tests. Customer production references are not currently available.

What happens if an action bypasses Castle OS?

Only requests routed through the governed boundary can be evaluated there. Preventing bypass requires integration and access controls on alternative paths. This website does not claim universal visibility or enforcement.

Can we start with sample data?

Yes. Start by agreeing a bounded example and its data requirements. Use synthetic or appropriately authorised sample data first. Confirm security, access, retention and commercial terms before transferring real records.

Does an exception prove fraud or a financial loss?

No. An exception identifies a condition for investigation. Source accuracy, context and professional review matter. A flagged amount is not automatically a loss or a recoverable saving.

How does a diagnostic lead to remediation?

An evaluation delivers the agreed evidence-linked exceptions, data gaps and prioritised control recommendations. We scope implementation separately, with owners, milestones and acceptance criteria. Process owners retain responsibility for corrective action.

For architects, engineers & assurance teams

Inspect the architecture.

Trace the request, inspect the enforcement point and define the integration. Clear engineering responsibilities from source data to receiving-system evidence.

Architecture & technical evidence

Understand what sits behind the decision.

Decision facts · ReasonGate · Evidence limits · Capability status

Explore the architecture →
Commercial engagement

A clear scope.
A measurable result.

Commission the work your organisation needs, with deliverables, dependencies and acceptance criteria agreed before delivery starts.

01 / PAID EVALUATION

Establish the value

Agree the workflow, data and controls. Evaluate the findings against your baseline and decide whether implementation is justified.

02 / DESIGN PARTNERSHIP

Shape the integration

Define a new connector or control workflow through a funded development scope. Agree responsibilities, milestones and test evidence.

03 / IMPLEMENTATION

Deploy against acceptance

Integrate the approved controls, validate operational behaviour and establish support before production activation.

Castle OS Group owns the software. Dinatla ICT provides solution delivery and implementation. Contracting, licensing and support responsibilities are defined in each proposal.

Start with one consequential action

Turn governance into
an execution control.

Bring the action that matters to your business. Leave with a defined control question, the evidence needed and a practical evaluation path.

info@castlegroupos.com →
Your evaluation starting point

One transaction type, one agreed control and the evidence available to evaluate it.

Book a solution session →

Opens your email application with a prepared enquiry. No data is uploaded or submitted through this page.