INTELLIGENCE, WITH BOUNDARIES.
Your knowledge should power your operations. Not leave your control.
Private infrastructure. Governed knowledge. Verifiable evidence.
One system, designed around your perimeter.
AI products. Platforms. Possibilities.
Applied AI. Agentic systems. Human control.
Explore the mAIb Tech ecosystem: Locs for critical operations, GAIO for AI governance, AOS-1 for agentic systems, and mAIb Labs for learning, productivity and everyday tools.
- On-premises deployment
- Air-gapped option
- Customer-controlled environment
- Controlled knowledge lifecycle
- Human approval gates
- Evidence & audit lineage
- Built for regulated operations
- No uncontrolled data egress
One system, inside your perimeter.
Approved knowledge flows through governed ingestion to a local model runtime, wrapped by policy, approval and audit layers. Nothing leaves the boundary.
Read the Architecture The problem
Enterprises want AI. Regulated operations cannot pay for it with their data.
Banning AI removes visibility while usage continues. Approving it without governance removes control. Neither is defensible at audit.
See the Enterprise CaseSensitive knowledge is escaping controlled environments
Employees increasingly paste incident logs, configurations, customer records, internal procedures and source code into external AI tools — invisible to security, and irreversible once sent.
Generic AI lacks operational governance
A capable model is not enough when nobody controls which knowledge it uses, who may ask what, which actions are allowed, which sources count as valid, and which approval is required before its knowledge changes.
Enterprises cannot prove what happened
Without lineage, evidence and lifecycle control, an organisation cannot prove what the system knew, which version answered, which policy applied, who approved a change — or roll any of it back.
The mAIb approach
Private infrastructure. Governed knowledge. Verifiable evidence.
Three layers that turn a capable model into an operational system a regulated enterprise can defend.
Explore the Platform- 01
Private infrastructure
Local or customer-controlled deployment. Approved models behind a neutral adapter layer. Controlled connectors, data residency by construction, and network-boundary enforcement — with customer-held keys where supported.
- 02
Governed knowledge & execution
Source approval, classification, redaction and versioning. Permissions enforced inside retrieval. Human approval gates, policy controls and rollback for every change the AI depends on.
- 03
Verifiable evidence
Tamper-evident audit events, decision records, provenance for every answer, and evidence export designed for security review, internal audit and renewal decisions.
Flagship — Locs
Governed private AI for sensitive telecom operations.
Enterprise software you run on your own servers. Locs connects approved telecom knowledge to customer-controlled AI, answers with citations and confidence scores, refuses when it does not know, and records everything it does.
- Telecom-focused: BSS/charging, NOC and customer-care copilots
- Local deployment — hardened container package, air-gap capable
- Answers only from operational knowledge your administrators approved
- Governed knowledge updates with human approval and rollback
- Evidence centre your auditors can use
- A pilot-to-production path measured in evidence, not slideware
Telecom operations
Built where operational knowledge is most expensive to lose.
Every telecom function has its own failure mode. Locs is shaped around the four where a wrong answer costs the most.
Explore TelecomAssurance for the systems that bill.
Incident analysis, runbook retrieval, known-error matching, change-impact support and evidence-backed vendor escalations — grounded only in knowledge your administrators approved.
Explore Charging & BSS- Known-error matching
- Change-impact support
- Evidence-backed escalations
- Approved runbook retrieval
Context at the moment the alarm fires.
Alarm and incident context, SOP discovery, escalation support, shift-handover knowledge and root-cause investigation support — cited, confidence-scored, advisory only.
Explore NOC operations- Alarm & incident context
- SOP discovery
- Shift-handover knowledge
- Root-cause investigation
One answer, consistently, across every agent.
Governed agent assistance, approved policy retrieval, consistent operational answers and controlled knowledge updates — so care stops improvising and starts citing.
Explore Customer care- Governed agent assistance
- Approved policy retrieval
- Consistent operational answers
- Controlled updates
The knowledge itself becomes an audited asset.
Controlled ingestion, gap detection, review workflow, versioned knowledge packages, provenance and rollback — the lifecycle behind every answer the system gives.
Explore Knowledge assurance- Controlled ingestion
- Gap detection & review
- Versioned packages
- Provenance & rollback
How it works
Six steps from deployment to defensible evidence.
No professional-services maze. Your team installs it, your administrators approve the knowledge, your auditors read the trail.
Review Deployment- 01
Deploy within the approved environment
On-premises, private cloud or air-gapped — installed by your ops team on infrastructure you control.
- 02
Connect approved knowledge sources
Read-only connectors for SharePoint/M365, ServiceNow and file systems create governed drafts.
- 03
Classify, redact and govern
Secrets block ingestion outright; identifiers are redacted before embedding; humans approve activation.
- 04
Serve controlled AI experiences
Authorised users get cited, confidence-scored answers from approved knowledge — advisory only.
- 05
Apply policy, permissions and approvals
Role-based access enforced in-query; unsafe actions refused; changes pass approval gates.
- 06
Produce evidence, monitor, roll back
Tamper-evident audit lineage, exportable evidence, and tested rollback for knowledge and models.
0 uncontrolled data-egress paths by design
6 published security control domains
90 days from pilot start to evidence review
15 question readiness self-assessment
Security & trust
Built to be reviewed, not just believed.
Every control below is stated the way we would defend it to your security team — including current status and known limitations.
Request the SecurityArchitecture Pack
Deployment boundary & zero-egress design Identity & access — RBAC enforced in-query Knowledge governance — secret blocking & redaction Model governance — evaluated before use Audit & evidence — tamper-evident lineage Resilience — kill switch, restore drills, rollback Responsible disclosure Current assurance status
Framework alignment
Alignment stated precisely. Certification never implied.
We publish where we align, where we are on the roadmap, and where a control is a design decision rather than a certification.
Full Alignment Detail| Framework | Current position | Evidence available | Status |
|---|---|---|---|
| EU AI Act | Designed to support applicable governance requirements for high-risk AI use in enterprise operations | Internal control mapping in preparation; available under NDA on request | By design |
| NIST AI RMF | Architecture designed around the Govern / Map / Measure / Manage functions | Architecture-to-function mapping available on request | By design |
| ISO/IEC 42001 (AI management) | On the certification roadmap; no issued certification claimed | Gap assessment planned | Roadmap |
| ISO/IEC 27001 (information security) | Security controls designed in alignment with Annex A control themes; on the certification roadmap | Control alignment notes available under NDA | Roadmap |
| SOC 2 | On the certification roadmap; trust-service criteria inform the control design | No audit performed yet | Roadmap |
| GDPR / UK GDPR | Privacy-by-design principles; on-premises deployment keeps personal data in the customer environment | Privacy documentation; data-processing terms on request | Alignment |
| Regional telecom & data regulation (e.g. CITRA, TRA, central-bank circulars) | Regulatory mapping capability — packs can be mapped to applicable circulars per engagement | Mapping produced per customer engagement | By design |
mAIb Tech does not claim an issued certification unless explicitly stated. Frameworks listed reflect design principles, alignment work and roadmap goals — not certifications, audit results or regulatory approvals.
Readiness assessment
How ready is your organisation for private AI?
A 15-question self-assessment across data exposure, deployment boundaries, identity, knowledge governance, approvals, auditability, rollback and operational ownership. Immediate results — no email required for your score.
Approximately 5–8 minutes. A preliminary, non-binding self-assessment — not an audit, certification or legal advice.
- Data exposure & shadow AI
- Deployment boundaries
- Identity & access
- Knowledge governance
- Model governance & approvals
- Audit, evidence & rollback
- Operational ownership
- Regulatory accountability
The company
A focused company with an honest stage.
mAIb Tech LLC is a Delaware limited liability company building governed private AI infrastructure, designed from firsthand telecom and BSS operations experience. We are founder-led, pre-launch, and onboarding a limited design-partner cohort. We do not publish customer names or testimonials we cannot legally back.
- Legal entity
- mAIb Tech LLC (Delaware, USA)
- Stage
- Pre-launch · design partners onboarding
- Flagship
- Locs — governed private AI for telecom
- Foundation
- AOS-1 governance runtime · GAIO platform
- Contact
- support@maib.io