Skip to content

Frequently asked questions

Questions we often get about deployments and collaboration. For anything else, use the contact page.

What does Xylolabs do?
We read sound, vibration, and ultrasonic signals to catch equipment issues and environmental changes early. One team owns the system from sensor to operator screen.
What industries do you work in?
Mostly ports, manufacturing, forestry, and security. If the problem shows up in acoustic or vibration signals, the approach usually transfers.
How are you different from an SI?
An SI builds to spec. We help define what to sense, how to interpret it, and how operators will use it. One team handles signal processing, AI, and the interface.
Does it work with existing PLCs and SCADA?
Yes. We plug in via OPC-UA, Modbus, and MQTT, all standard protocols. No need to rip out existing equipment; we just add a monitoring layer on top.
Does it work offline or air-gapped?
Yes. Inference runs on local gateways or edge devices. Data stays on your side. No cloud dependency required.
Does our data leave the site?
No. Your data stays in your infrastructure or your designated cloud. Nothing flows to us automatically. If we need access for model work, we agree on that separately.
How does retraining work?
We set up a retraining loop on your operating data. Labeling rules, triggers, and deploy steps are documented when we hand over.
Do you make hardware too?
Yes. We design and build sensors and gateways in-house. We also mix in off-the-shelf gear when it makes sense.
How do we get started?
Email [email protected] or use the contact page. Tell us what is happening and what you want to fix, and we will set up a call.
How long does a pilot take?
Usually 4-8 weeks to a first result. Main variables: how quickly we can access your data and equipment.
How does pricing work?
Pilots are fixed-fee. After that, it's usually a subscription or maintenance contract. We size it to scope.
Do you support it after launch?
Yes. Handoff, monitoring, and model updates are all included. We stay involved until the system runs on its own.