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?
- We currently work in ports, manufacturing, forestry, and security. We assess fit after reviewing the available signals and operating conditions.
- How does a project work?
- We define what to sense, how to interpret it, and how operators will use the result. Signal processing, models, and the operator interface are designed together.
- 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 agree on when operating data is used for retraining and how a new model is deployed.
- 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 admin@xylolabs.com 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. We support handoff, monitoring, and model updates.