One suite for the whole carrier network.
CraftWorldis MatreComm’s carrier operations suite. Mobility, transport and access run by declared goals — availability, MTTR, subscriber experience — held true by the Ritam platform underneath.
Ritam is the platform. CraftWorld is the product.
One name for each layer, so there's no guessing what you're buying.
Ritam — the platform →
The autonomous AIOps engine: watches telemetry across every vendor, diagnoses one root cause, plans the safest fix and executes it. Every MatreComm product runs on it.
CraftWorld — the carrier suite
What carrier operations teams deploy: domain applications for mobility, transport and access, each with its own goals, consoles and runbooks — sharing Ritam’s core, data graph and on-prem AI.
Pick a domain. Prove it. Extend.
Each domain deploys on its own; all three share one engine, so proving one is most of the work of running all three.
Mobility
5G core, RAN & subscriber edge — session, QoE and slice SLA.
Explore →Transport
Optical & IP backbone — five-nines availability, latency, protection.
Explore →Access
FTTx, PON & fixed wireless — provisioning, fibre MTTR, per-sub SLA.
Explore →Frequently asked questions
What is CraftWorld?
CraftWorld is MatreComm's carrier operations suite — mobility, transport and access networks run by declared goals such as availability, MTTR and subscriber experience, on the Ritam AIOps engine. CraftWorld is multi-vendor, deploys on-premises, and is built for carrier-grade scale, in three domains: CraftWorld Mobility, CraftWorld Transport and CraftWorld Access.
What is the difference between Ritam and CraftWorld?
Ritam is the platform — the AIOps engine. CraftWorld is the product carriers buy: three operational domains, Mobility, Transport and Access, that run on that engine. The same engine also underpins MatreComm's enterprise products.
Do we have to deploy all three CraftWorld domains at once?
No. Each CraftWorld domain deploys independently, and all three share one engine — so proving out one domain is most of the work of running all three. The usual approach is to start with whichever domain carries the most operational pain, then extend.
Who is CraftWorld for?
CraftWorld is built for telecom operators and carriers running multi-vendor networks across mobile, optical/IP backbone and fixed access — organisations that want operations driven by declared goals rather than by alarm queues.
Start with one domain.
Keep the same engine for all three.
A scoped demo on your own topology — bring the domain that hurts most.