We build the control plane that private 5G deployments don't ship with
Signalweft was founded in Denver in 2024 to solve a specific problem: industrial campuses deploying CBRS radios had no vendor-neutral way to enforce SLA policies across mixed-vendor RAN infrastructure.
The problem we saw
When CBRS unlicensed spectrum became generally available, manufacturers and logistics operators moved quickly to deploy private 5G. The hardware got better every year. The RAN vendors — Celona, Ericsson, Nokia DAC — each shipped capable radios. But every vendor's management console was a silo. An OT director with a mixed deployment had no single view of coverage, SINR, or device connectivity across the floor. SLA policy was either applied inconsistently or not at all.
We saw the same pattern across half a dozen industrial deployments: well-specified RAN hardware running on underspecified orchestration. The AGV vendors were specifying sub-10 ms latency requirements. The network was delivering best-effort. Nobody had a system that could prove the gap — let alone close it.
What we built
Signalweft is a control-plane software layer. We sit above the RAN vendor's equipment and provide a unified view of coverage, SINR, device association state, and SLA compliance across your entire deployment. We integrate with each vendor's management API to normalise telemetry, and we enforce QoS policy at the device class level — not as a best-effort configuration, but as a guaranteed parameter set.
We started with manufacturing because that's where the SLA stakes are highest. An AGV that loses its control channel stops the line. We've since expanded to logistics and energy, where the patterns are similar — deterministic connectivity requirements, heterogeneous device fleets, and minimal tolerance for downtime.
How we operate
Signalweft is bootstrapped. We have no VC pressure to land enterprise logos before the product is ready. Our first customers are industrial operators who agreed to pay for the software before it was finished because they needed it to exist. That relationship — operator as design partner, not just paying user — defines how we build.
We're based in Denver, which puts us close to the manufacturing and energy operations in Colorado and the broader Mountain West. We work on-site with customers during deployment and stay involved through production. We don't hand off to a channel partner and disappear.
The people building Signalweft
Priya Sharma
CEO & Co-founder
Eight years designing private wireless networks for manufacturing facilities before co-founding Signalweft in Denver in 2024. Watched operations teams fight per-vendor NMS tools to answer two questions — "where is the coverage gap?" and "why did the AGV drop?" — and built the control plane layer she wished had existed all along.
Marcus Dellantonio
Head of RF Engineering
10 years designing cellular networks for industrial and public safety deployments. Previously built RF planning tooling for a network infrastructure firm specializing in CBRS. Developed Signalweft's material attenuation modeling profiles from walktest data across manufacturing and logistics sites.
Kezia Abubakar
Head of Product
OT software product background spanning network management, SCADA HMI, and industrial IoT. Focused on making operator-grade complexity navigable without stripping the depth that network engineers need.
Principles that shape the product
Honest about what we are
We're a 2024 company. We don't claim certifications we don't hold. We describe what Signalweft does today, not what we're planning to announce. Our security page is a design statement, not a marketing claim.
Design partner model
Every customer in our first cohort was a design partner before they were a paying customer. We worked on their specific deployment before we asked for a contract. We still operate that way with new industrial segments.
On-site accountability
We deploy with you and stay in production. Our team has been on factory floors at 2 AM when a firmware update caused a connectivity issue. That context is what separates us from vendors who ship hardware and move on.
We'd like to understand your deployment
Whether you're evaluating private 5G for the first time or you're already running CBRS and hitting orchestration limits, we'll give you a straight technical answer.