Industries / Industry and infrastructure

Network software changed with approval and on record.

A telecom module is in development. Today, Build and Govern give network software teams governed AI assistance, named approvals and an audit record.

Standards
TL 9000
Works with
Your repositories, CI and the AI tools your teams use
Agent policy
Rules you write per team and project
Deployment
Self-hosted, your cloud or air-gapped

What your team gets

What Build and Govern give a network software team today.

Governed AI codingEditor, Agents and CLI with the models your organisation approves. Claude Code, Codex, Cursor and GitHub Copilot CLI are governed at the level each tool allows.
Production out of agents' reachAgent rules can deny commands against production clusters and leave infrastructure changes to your pipeline.
Named approvalsPushes to protected branches wait for a named approver, through one inbox and your email, chat and paging channels.
Every change on recordA tamper-evident audit log with signed exports your auditor can verify offline.
Your network, your modelsSelf-hosted or air-gapped, with models served inside your network.

Who uses it

For the engineers who change the network and the people who answer for it.

Network software engineersWrite and review code and configuration with AI assistance under your policy.
Platform engineersKeep agents away from production clusters and infrastructure.
Security teamsGovern every AI tool in one place, ours and third-party.
Quality and auditExport the record of changes and approvals for TL 9000 audits.

Tools and formats

What works today, and what does not.

RAN and core tooling is in development. What follows is what the general Editor and Govern do today.

Code and configurationNetwork function code, data models and deployment configuration edited and reviewed as text. No NETCONF client, YANG validation or RAN tooling.Text files · git
Agent rules for your toolingShell rules match commands such as kubectl, helm or ansible-playbook; network rules match destination hosts; push rules match branches.shell · network · git_push · mcp_tool
Third-party AI toolsEach at its stated control level: enforced, managed configuration or monitored.Claude Code · Codex · Cursor · Windsurf · GitHub Copilot CLI · Gemini CLI

Product names belong to their owners. Tell us which tools your team runs, and we will say plainly what works today.

How a change moves

A person decides before anything leaves the desk.

  1. Propose
    An engineer or agent drafts a change to network software.
  2. Verify
    Your CI builds and tests it.
  3. Approve
    A push to a protected branch waits for a named approver.
  4. Record
    Change, results and approval kept together in the audit record.

Standards

Evidence for your quality system. The certification is yours.

TL 9000Evidence toward TL 9000: each change kept with its reason, test and approval, in a record your auditor can verify offline.

Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor.

Rules you work under

What they ask, and what Neural Inverse gives you toward them.

We produce records your assessors and regulators can use. We never say a product makes you compliant; that stays with your organisation.

[Draft: to be approved by legal counsel before publication]

UK Telecommunications (Security) Act 2021What it asksPublic telecoms providers take the security measures set by the Electronic Communications (Security Measures) Regulations 2022. Ofcom measures Tier 1 and Tier 2 providers against the Telecommunications Security Code of Practice, revised as version 1.1 on 14 July 2026, with measures due by 31 March 2027, 31 March 2028, 31 December 2028 and 31 December 2029.What Neural Inverse gives youNeural Inverse Govern gives approvals by named people for pushes to protected branches, agent rules that keep agents away from production clusters, and a tamper-evident audit log with signed exports your auditor can verify offline.
NIS2 DirectiveWhat it asksProviders of public electronic communications networks and services in the EU are in scope. They manage cyber risk, including in their supply chain, and report significant incidents: an early warning within 24 hours, a notification within 72 hours and a final report within a month, under their national law.What Neural Inverse gives youAccess control, approvals by named people and a tamper-evident audit log you can export when you report.
India Telecom Cyber Security Rules, 2024What it asksUnder the Telecommunications Act, 2023, the Telecommunications (Telecom Cyber Security) Rules, 2024, notified on 21 November 2024, require telecom entities to appoint a Chief Telecommunication Security Officer and report security incidents to the central government within six hours, with details within 24 hours.What Neural Inverse gives youAn audit log that runs on your own servers or in a cloud region in India, which you can search and export when you report.

Questions

What telecommunications teams ask us first.

Does it work with our network tooling?

There is no telecom module yet; one is in development, and there is no NETCONF client, YANG validation or RAN tooling. Neural Inverse Govern works today: agent rules match commands such as kubectl, helm or ansible-playbook, and Claude Code, Codex, Cursor and GitHub Copilot CLI are governed at the level each tool allows.

Can agents change production?

Agent rules can deny commands against production clusters and leave infrastructure changes to your pipeline. A push to a protected branch waits for a named approver.

Can it run on-premises or air-gapped?

Yes. Neural Inverse runs self-hosted or air-gapped, with models served inside your network. Run each release on a host with no route out before you rely on it.

Is Neural Inverse certified to TL 9000?

No. Govern gives evidence toward TL 9000: each change kept with its reason, test and approval, in a record your auditor can verify offline. Certification stays with your organisation and its assessor.

Talk to our team.

Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.

Telecommunications · Neural Inverse