The GCC regulatory decision layer is already built. Not another platform to compete with yours — the authored decision architecture that sits underneath it.

BLUFRAIM is authored GCC regulatory decision IP: applicability, operational checks, evidence requirements, ownership, clearance and the management position, already written and already structured.

License it. Embed it. White-label it. Deploy it.

Discuss strategic access See it working

01ScopeThirteen plain business questions decide which regulatory areas apply to the firm.
02AssessOne check at a time: what evidence is needed, where it sits, who owns it, then a human judgement.
03PositionOne defensible conclusion, read three ways — assessor, management, executive.

Your interface or ours. The decision logic is the same.

Authored across all six GCC states, with dedicated QFC, DIFC and ADGM regulatory layers.

CBUAE SCA / CMA VARA DFSA FSRA SAMA SDAIA NCA QCB CBB CBO CBK UAE PDPL IFRS S1 / S2 ISO / NIST

The problem

Regulatory information is not a regulatory decision.

Regulatory text is available. Change feeds are available. Mapping libraries are available. The market has largely solved the retrieval of regulation.

None of it answers the questions a regulated firm is actually accountable for: which obligation applies to this business, what would have to be true to satisfy it, what evidence would prove that, who inside the organisation holds that evidence, whether the position is adequate, and what would clear the finding if it is not.

The distance between regulatory information and a defensible regulatory decision is authoring work. It is the expensive part, and it does not arrive with a feed.

What it is

Regulation, converted into a decision chain.

BLUFRAIM is an authored decision layer. Every applicable obligation is resolved into the same seven-part chain, so an assessment produces a position someone can defend rather than a list of references.

The decision chain

ApplicabilityWhether the obligation reaches this business at all.
Operational checkWhat has to be true, stated as something testable.
EvidenceWhat must be produced, and what it must prove.
OwnerWho inside the organisation holds it, and where it sits.
Human judgementA person's assessment, recorded against that evidence.
ClearanceWhat closes the finding — a defined test, not an assertion.
OutcomeThe management and executive position, and what must be referred.

The machinery stays underneath. The person using it sees one journey.

Scope→Assess→Position

Position is where the assessment resolves into a management and board-level outcome — the same figures read three ways, at the density each audience needs.

See it working

Three screens. One decision on each.

This is the working reference implementation of the decision layer — not a mock-up. It exists so the logic underneath can be inspected before anyone commits to embedding it.

Every regulatory line below is the workbook's own text, shown against the workbook's demonstration data.

BLUFRAIM Scope · 1 of 13

Does it use AI or automated decision-making in financial services (lending, pricing, onboarding, fraud)?

Yes No

Thirteen plain business questions · the answers decide which regulatory areas are assessed

BLUFRAIM Assess · S2.12 · Governance & Accountability

Financial Services · 18 of 47 · area 1 of 6

Whether the governing body actually decides

Evidence needed

Produce the constitutional record for whether the governing body actually decides — terms of reference or mandate, the appointing minute, and the individuals currently holding the role.

To show it operates: minutes of at least one meeting where the body exercised the responsibility in substance rather than noting it, plus evidence a decision it took was implemented.

Where to find it

the board or committee secretariat; appointment records sit with HR or the company secretary.

Ask: Company Secretary / Board Secretariat

Your assessment

4Strong
3Adequate
2Needs attention
1Serious weakness
0Not in place

Source of truth · BLUFRAIM Workbook v5.4 — 501 authored checks, 13 regulatory areas

BLUFRAIM Position · Worked example

Assessor Management Executive

Where are we?

A critical condition is present and has not been cleared.

Governance score 2.29 of 4 · evidence confidence Medium · 96% of the assessment complete.

What is wrong?

Model Management Standards alignmentFinancial Services · Critical condition

DPO appointment and roleData Protection · Critical condition

Risk-management and compliance frameworkPayments & Fintech · Critical condition

What remains open?

11 of 245 checks are not yet assessed. 3 critical conditions recorded and not cleared.

Source of truth · BLUFRAIM Workbook v5.4 — 501 authored checks, 13 regulatory areas. This is the workbook's demonstration data.

Open the Workspace preview

The same journey runs at /workspace against the workbook's demonstration data. Under an embedding or white-label arrangement these screens are yours to replace — the decision layer underneath them is what BLUFRAIM supplies. A critical condition is flagged for human judgement; nothing is escalated to a board automatically.

For operators

Your platform. Your customers. Your brand.

BLUFRAIM is written for an operator that has already built the hard commercial machinery — a platform, a workflow engine, a customer base, a support function, regulatory update infrastructure and a route to market — and does not have a deep authored GCC regulatory decision layer.

Everything you have already paid for stays exactly where it is. Only the layer you are missing changes.

You already provide

Platform and workflow
Customers and commercial relationships
Sales, onboarding and support
Regulatory feeds and change monitoring
Distribution, hosting and integrations
The brand the client signs with

BLUFRAIM provides

The authored GCC decision architecture underneath it
Applicability logic across six states and three financial free zones
Evidence requirements, ownership and clearance tests
The scoring, completion and risk-signal architecture
Rule references that carry regulatory change into affected checks
A working reference implementation to integrate against

BLUFRAIM sits beneath existing retrieval, workflow, monitoring and AI rather than competing with them. Your platform can already find documents; the decision layer tells it what to look for, who holds it, what it must prove and what would clear the finding.

Build or license

Why recreate the GCC decision layer internally?

It is a fair question, and it is the only one that matters. The regulatory text is obtainable by anyone. What takes the time is deciding, obligation by obligation, what would actually satisfy it — and being right about that.

Building it internally

A regulatory research and authoring programme across six states and three financial free zones, finished before the first client sees anything.
Deciding what evidence actually proves an obligation — the judgement that cannot be scraped, generated or bought as a feed.
Designing the scoring, completion and clearance architecture from a blank page, then defending those choices to a regulated client.
Carrying the false-clearance risk: an assessment that closes a finding it should not have, in front of the client's regulator.
Your GCC roadmap slot spent on authoring rather than on the platform your customers buy.

Licensing BLUFRAIM

The authoring is done. Applicability, evidence, ownership and clearance are already written across the GCC.
The architecture has already been thought through — how a score is reached, when an assessment is provisional, what a critical condition does.
Deployable decision logic, structured for your platform to consume rather than a document to interpret.
GCC time-to-market measured against your next sales cycle rather than your next roadmap year.
Your brand, your contracts, your operating model — unchanged.

The comparison is not build-versus-buy in the abstract. It is whether authoring GCC regulatory judgement is the thing your engineering and regulatory capacity should be spent on this year.

Assurance

Defensible, because judgement stays human.

An output that reaches a management or board audience through your platform carries your name on it. The decision layer is built so that it holds up when someone pulls on it.

Human judgement, not inference. A score is a person's assessment recorded against a stated evidence requirement. Nothing is concluded on the reader's behalf.
Evidence before conclusion. Every check states what must be produced and what that evidence must prove — including whether an arrangement operates in substance rather than merely exists on paper.
Clearance is a defined test. A finding closes when the stated clearance condition is met, not when someone asserts it has been handled.
Traceability. Every check carries its rule reference back to the instrument it comes from, so a regulatory change can be traced into the checks it affects.
Uncertainty is reported, not smoothed over. An incomplete assessment reads as provisional rather than as a result, and evidence confidence is reported alongside the position.
Nothing escalates automatically. Findings touching licence, authorisation, prohibition or cease wording are flagged for human judgement. A person refers them.

These are properties of the authored layer, so they survive being embedded in someone else's interface.

What is already authored

The depth is the asset.

An authored regulatory test is not simply a question. Each one carries its own applicability, evidence, ownership, scoring and clearance logic underneath.

501Authored regulatory tests

13Regulatory areas

4,008Jurisdiction mappings

All sixGCC states + QFC · DIFC · ADGM

The rules change by jurisdiction

The assessment architecture doesn't. One authored structure carries multiple regulatory regimes, so adding a jurisdiction is an authoring exercise rather than a rebuild.

Regulatory change has a path

Rule references run both ways. A change to an instrument can be traced into the specific checks it affects, which is what makes the layer maintainable in your hands rather than only in ours.

These figures describe what has been authored underneath the assessment — not what a user has to operate, and not the reason to license it. The reason is the position it produces.

Commercial deployment

Structured around your commercial model, not ours.

Available routes

Non-exclusiveLicense the decision layer and deploy it through your platform.
ExclusiveHold it exclusively, by territory or by segment.
White-labelDeploy it entirely under your own brand.
EmbeddedIntegrate the decision layer beneath your existing product.
SublicensingExtend it to your own partners and channel.
AcquisitionAcquire the authored layer outright.

Territory, exclusivity, term and support are matters for discussion under NDA. Nothing on this page is an offer.

Access

Test it against something you already know the answer to.

Evaluation is controlled and deliberately unflattering: take a live client engagement or a historic case whose outcome you already know, run it through the instrument, and compare what it concludes with what you concluded.

That is a shorter conversation than a capability deck, and it is the only one that settles the question.

Materials are released in stages. The authored architecture, the scoring engine and the jurisdiction mappings are opened under NDA, in controlled briefing and diligence.