Entalinity, Explained.

Entalinity is an AI operations layer for telecom operators and other infrastructure teams that run on many disconnected tools. It does the work your engineers spend most of every incident on: searching tools, reconciling records, chasing evidence and updating customers. It has two products. Overlay does the tier 1 NOC engineer work and Inlay does tier 2 and above. Both connect to the tools you already run, without replacing any of them.

Entalinity starts with telecom operators, where a single core link failure can set off dozens of alarms and the tools rarely agree. The same pattern applies to ISPs, data centres, IT service desks, utilities and any operations team running on many disconnected tools.

Entalinity is based in Fourways, Sandton, in Johannesburg, Gauteng, South Africa. It was founded by Bheki Ntando Ngwenya and built from inside a network operations centre. You can reach the team at info@entalinity.com or +27 79 739 4470.

Overlay does the work of a tier 1 NOC engineer. It investigates alarms, correlates them to a single root cause, gathers evidence such as packet loss and the time the fault started, checks external factors such as weather, identifies which customers are affected, logs and updates tickets, and keeps customers informed. When records conflict it does not pick a winner: it attaches every version and escalates to tier 2 with the evidence. Like a human tier 1, it never changes the network or your systems of record.

Inlay does tier 2 and above work. It takes escalations with a complete case file, performs the deeper technical analysis, proposes fixes, corrects systems of record such as inventory, and makes network changes only where you have authorised it.

Yes. You can buy Overlay for tier 1 work, Inlay for tier 2 and above, or both. Bought together, the handoff between tier 1 and tier 2 stops losing information: Overlay builds the case file and escalates, and Inlay picks it up with nothing missing. Both run on the same data layer and intelligence store.

The moment Overlay knows which customers sit behind a fault, it sends them a holding message that carries no uncertain facts. Detailed updates wait until the facts are confirmed. When tier 2 corrects a record, Overlay works out the affected customers again from the corrected mapping and sends the full update.

No. Entalinity's data layer connects to your existing monitoring, inventory and ticketing tools, converts their formats into one consistent shape and links records that refer to the same thing. It keeps a synced mirror, a history and an audit trail, but takes no actions itself. Your own systems remain the owners of the data and nothing in your stack is ripped out.

Only within the authority you set. Each product holds the authority of the human role it supports, and that authority widens only as trust is earned. Overlay holds tier 1 authority and raises requests instead of making changes. For Inlay, authority depends on the risk of the action and the impact on the customer: low-risk actions on non-critical customers can run automatically with a log, higher-risk ones need one-tap approval, and the highest need a named senior engineer and a rollback plan. Every action is logged with who or what approved it and why.

A hybrid approach, routed by difficulty. Routine tier 1 correlation and normalisation runs on open-source models. Advanced reasoning, ambiguous cases and tier 2 escalations go to frontier models from labs such as Anthropic (Claude) and OpenAI (ChatGPT). Entalinity chooses and manages the models, so you never have to evaluate them yourself, and the model layer can run in-country or on-premise where sovereignty requires it.

Rules are cheaper and more predictable where data is clean, so connectors, ID normalisation, linking and sync are ordinary, deterministic software. AI is used where rules break: inconsistent alarm formats across vendors, free-text ticket notes, undocumented dependencies, conflicting records and cascades nobody anticipated.

You keep ownership of your data and your systems. The data layer reads and mirrors; your systems stay the record. What the system learns about your network is kept in an intelligence store that is versioned, inspectable, reversible and owned by you. Entalinity documents how to leave from day one.

A pilot runs with one operator on one incident type, in three phases. First, success is agreed and the data layer is connected to the tools behind that incident type with read access only. Second, Overlay works your real incidents with tier 1 authority: case files, tickets and customer updates. Third, results are measured: time from alarm to case file, duplicate tickets avoided, conflicts confirmed, customer-identification accuracy, time to first update and cost per incident. Then you decide whether to widen it, add Inlay or stop.

Start with a call or meeting with the founder, Bheki, about how your incidents run today. You get a plain answer on whether Overlay, Inlay, both or neither fits. If it does, you receive a scope with measurable targets within 5 business days. Contact info@entalinity.com, call +27 79 739 4470 or use the form at entalinity.com/contact.