Flagship Ecosystem
The Barzel Ecosystem
Barzel is the flagship AI infrastructure and intelligent operations ecosystem developed by Real Biz Digital. It gives organizations a governed path between AI systems and the platforms that run the business.
In one paragraph
AI is evolving from technology that answers questions into technology capable of executing actions. That transition creates new challenges around security, governance, permissions, cost, risk, integration, orchestration and operational control. Barzel addresses these challenges through four enterprise products that can be adopted independently or combined.
The shift
AI systems are moving from generating text to invoking tools, calling APIs and changing records in systems of record.
The gap
Existing identity, security and cost tooling was designed for human users and static services, not for autonomous software that decides what to do next.
The Barzel answer
A control layer between AI and the business: what is allowed, where requests are routed, what it costs and how execution reaches real systems.
Architecture
One intelligence and control layer, four products
AI models and agents sit above the Barzel intelligence and control layer. Inside that layer, BarzelVault governs what may happen, Barzel Central Gateway routes and controls access, Barzel FinOps Atlas measures financial consequence and BarzelOps executes against operational systems. Below the layer sit the systems organizations already run. Select a module to see what it does and where it connects.
Layer 01
AI Models & AI Agents
Barzel Intelligence & Control Layer
Governance & Security
BarzelVault
Evaluates AI actions before sensitive operations execute: policy enforcement, approval workflows, risk assessment and an auditable record of what agents were permitted to do.
Explore BarzelVault →Typically connects to
- Enterprise Systems
- Databases
- Business Applications
Works closely with
Barzel Central Gateway, which routes the requests BarzelVault rules on, and BarzelOps, which carries approved actions into operational systems.
How the products relate
Independent products, one coherent path
Adoption
Start where the risk is, expand from there
Path 01
Govern first
Begin with BarzelVault when agents already touch sensitive systems and the immediate need is policy, approval and audit.
Path 02
Centralize first
Begin with Barzel Central Gateway when MCP servers, tools and credentials have multiplied across teams.
Path 03
Measure first
Begin with Barzel FinOps Atlas when AI and cloud spending is growing faster than the visibility around it.
Path 04
Execute first
Begin with BarzelOps when the goal is agents that participate in real workflows rather than answer questions.
Also in the portfolio
Specialized Technology
Barzel Scripture Intelligence is a specialized Scripture technology product for search, Scripture Q&A, contextual analysis, cross-referencing, language study, teaching and devotional study. It sits in the wider Real Biz Digital innovation portfolio rather than in the enterprise infrastructure proposition.
Evaluate Barzel for your environment
Try a Barzel product directly, or tell us about the AI systems you are putting into production.
Shipping today
All five servers are published and callable
Barzel is not a roadmap. Every product below is live on the MCPize marketplace with a public endpoint, published plans and a 100% call success rate. Two of the five have a free tier you can call without a card.
The five published Barzel MCP servers — Barzel Scripture Intelligence, Barzel FinOps Atlas, Barzel Central Gateway, BarzelOps MCP AI Business Operations and BarzelVault MCP AI Action Firewall — each marked active on the MCPize marketplace.
| Product | Does | Surface | From |
|---|---|---|---|
| BarzelVault | AI action firewall — four-outcome policy, approvals, tamper-evident audit | 9 tools · 12 resources · 9 prompts | Free |
| Barzel Central Gateway | MCP governance gateway — identity-aware policy, routing, SIEM evidence | 25 tools · 18 resources · 15 prompts | Free |
| Barzel FinOps Atlas | Finance controls — close readiness, audit evidence, SOX/SOC 2 defense | 30 tools · 21 resources · 16 prompts | Free |
| BarzelOps | Governed workflow automation across HubSpot, Xero, Gmail, Drive, Slack | 40 tools · 20 resources · 20 prompts | Free |
| Barzel Scripture Intelligence | Bible MCP server — WEB, KJV, ASV search, theology, original languages | 54 tools · 36 resources · 75 prompts | Free |
Plans and counts as published on the marketplace listings, 2 September 2026.
Common questions
Choosing between five servers
How many Barzel MCP servers are there, and what does each do?
Five. BarzelVault is an action firewall that decides whether an agent action may execute. Barzel Central Gateway governs and routes across every MCP server your agents reach. Barzel FinOps Atlas assembles financial evidence. BarzelOps executes operational work across HubSpot, Xero, Gmail, Google Drive and Slack. Barzel Scripture Intelligence is a free public server with 54 tools.
Do I need all five, or can I start with one?
Start with one. They share a governance model and a transport but none requires another. Most teams begin with either Central Gateway, because it fronts servers they already run, or BarzelVault, because they have one dangerous action class they want to control first.
What is the difference between BarzelVault and Barzel Central Gateway?
BarzelVault decides whether a specific action may execute and returns one of four deterministic outcomes. Central Gateway sits in front of many MCP servers — including third-party ones you did not write — and governs which identities may reach which capabilities at all. Vault is depth on one decision; Gateway is breadth across an estate.
Which servers have a free tier?
All five. Central Gateway gives 1,000 calls a month, FinOps Atlas a 500-call sandbox, BarzelOps 100 calls a day, and Scripture Intelligence is free and unmetered with no signup. BarzelVault has a free Dev tier of 10,000 calls a month, with paid plans from $199 a month.
Are these products or a platform?
Five independent MCP servers, each published and billed separately on the MCPize marketplace. They interoperate because they speak the same protocol, not because they share a runtime you have to adopt wholesale.