Telecom software · Build · Deploy · Operate

We build, deploy, and run the systems that keep operators' networks on the air.

KJOO works inside live carrier environments — TR-069 and USP device management at scale, fleet simulation against a live ACS, and the subscriber-facing platforms that sit on top of them.

01 How we work

One engagement, not three contracts.

Most vendors hand off at go-live. We stay on the system we wrote.

  1. Build

    Design and development against your actual data models and interfaces — not a reference architecture that assumes a greenfield network.

  2. Deploy

    Integration into a network that is already carrying traffic. Staged rollout, rollback path defined before the first change window.

  3. Operate

    Monitoring, maintenance, and capacity work after go-live. The people who answer the page are the people who wrote the code.

02 Products

Built for operators, running in operators' networks.

TR-069 · USP over MQTT

CPE Cluster

Rehearse the network before you have to run it. CPE Cluster drives genuine protocol conversations built from real device data models — not replayed packets — so you can load and fault-test an ACS at population scale before it meets subscribers.

Controller + SDK · Self-care & field ops

Edge Mobility

The middleware between your mobile app and your CPE management platform. A controller that bridges to your ACS, topology and WiFi-optimisation backends, plus an SDK that gives app teams one integration surface instead of four — WAN and VoIP status, LAN hosts, WiFi networks and clients, per-band quality, bandwidth tests, reboot and factory reset.

Need something that isn't on this list? Most of our work starts that way — tell us what the network needs.

03 Why KJOO

What you get that a generalist shop can't give you.

We already speak the protocols

TR-069, USP, MQTT, the Broadband Forum data models, and the Axiros stack. No ramp-up period billed to you while a team learns what a CPE is.

We work in live networks

Change windows, rollback plans, and staged rollouts are the normal shape of our work, not an exception handled by a separate team.

Small enough to reach

You get the engineers who built the system. Escalation is a conversation, not a ticket queue with a tier structure.

We stay after go-live

Operating what we build keeps us honest about how we build it. The maintenance cost lands on us too.

04 Contact

Tell us what the network needs to do.

A short conversation with an engineer, not a discovery call with a sales team.

Talk to us