5 MCP servers live now What’s live ›
Real Biz Digital logo Real Biz Digital

Technology

Building What Comes Next

Real Biz Digital is a product innovation company developing and launching technology products across emerging categories. We continually explore technologies with the potential to become useful, scalable products.

01

Artificial Intelligence

Applied AI for understanding information, identifying patterns and improving decisions inside real operational systems.

Barzel ecosystem →

02

AI Agents

Software that pursues goals and takes actions. Useful in production only when identity, permission and accountability are engineered in.

BarzelVault →

03

Model Context Protocol

An open standard for connecting AI models to tools and data. MCP turns models into actors, which makes governance an infrastructure requirement.

MCP security guide →

04

Cybersecurity

Security thinking applied to autonomous software: least privilege, policy enforcement, approval paths and auditable records.

BarzelVault →

05

Automation

Fragmented, repetitive processes rebuilt as intelligent workflows that adapt instead of breaking on the first exception.

BarzelOps →

06

IoT & IIoT

Connected and industrial devices as a source of operational signal, where reliability and control matter more than novelty.

07

Data Intelligence

Turning operational and financial data into analysis people can act on, rather than dashboards nobody opens.

Barzel FinOps Atlas →

08

Financial Technology

Financial operations logic applied to technology spending, cost governance and financial risk.

Barzel FinOps Atlas →

09

Intelligent Infrastructure

Control planes, gateways and policy layers: the plumbing that decides what AI systems can reach and do.

Barzel Central Gateway →

10

Next-Generation Technologies

Emerging protocols, standards and capabilities we track and prototype against before they become mainstream requirements.

Insights →

Common questions

Questions about how it is built

What technology do the Barzel servers run on?

All five speak the Model Context Protocol over Streamable HTTP with JSON-RPC 2.0 framing. Policy evaluation is deterministic with no model in the decision path, state is held in tenant-scoped PostgreSQL, and governance fails closed — if the policy set is unreachable, the action is denied.

Do I need to install a Barzel SDK?

No, and we do not publish one in any language. MCP is the interface. A client that already speaks the protocol already speaks to our servers, and a wrapper of ours would only be a version of it that ages. Connection detail is in the developer documentation.

Why does deterministic policy evaluation matter?

Because a control you cannot reproduce is not a control. The same action, policy set and context must produce the same outcome every time, or you cannot explain a decision to an auditor or test a policy before enforcing it. A model in the decision path makes the decision unreproducible by construction.

What does “fails closed” mean in practice?

If the governance layer cannot reach its policy set, it denies rather than allowing. An outage therefore stops sensitive agent actions instead of waving them through — which is the right trade, but a real one: your retry logic has to tolerate a deny that is actually an outage.

Is customer data pooled between tenants?

No. State is tenant-scoped rather than one shared table with a tenant column doing the work, and downstream credentials are supplied per tenant and never pooled. The security page states the full posture, including what we are not certified against.

Which technology areas does Real Biz Digital build in?

Applied AI, AI agents, the Model Context Protocol, cybersecurity, automation, IoT and IIoT, data intelligence, financial technology, intelligent infrastructure and emerging next-generation technologies. The five published Barzel servers are where that work ships.

Shared foundation

What every Barzel server has in common

Five products, one set of engineering commitments. These are the decisions we do not revisit per server, because they are what make the servers substitutable for a client and reviewable for a security team.

Transport Streamable HTTP, JSON-RPC 2.0 No proprietary wire format, no SDK of ours to install, no long-lived socket to babysit. A client that already speaks MCP already speaks to us.
Policy evaluation Deterministic, with no model in the path The same action, policy set and context produce the same outcome every time. A governance decision you cannot reproduce is not a control.
Credentials Never in a prompt or an audit record Secrets are referenced by identifier and scope. That is why a full audit export can go to a reviewer without a rotation afterwards.
State Tenant-scoped PostgreSQL Per-tenant isolation rather than one shared table with a tenant column doing the work. The blast radius of a mistake is one tenant.
Failure mode Fails closed If the governance layer cannot reach its policy set, it denies. An outage stops sensitive agent actions rather than waving them through.
Enumeration The server is the source of truth Capabilities are discovered through tools/list, never from a hand-maintained table that can drift. Our own documentation says so explicitly.

How we choose

Not every advance becomes a product

We look for technologies where the capability is real, the problem is expensive, and the gap between the two can be closed with engineering rather than optimism. That filter is why our portfolio concentrates on AI infrastructure, governance, financial intelligence and operations rather than spreading thin.

Capability is proven

The technology works outside a demo, and its limits are understood.

The problem has a cost

Organizations already pay for the problem in risk, effort or money.

A product can scale

The solution generalises beyond one company’s internal setup.

See how the technology becomes product

The Barzel ecosystem is where these technologies meet real operational requirements.