Question 1

What kind of problems does Xylolabs solve?

Accepted Answer

We build AI systems that catch early anomalies in equipment and environmental conditions by reading acoustic, vibration, and ultrasonic signals that are easy for people to miss. One team covers the work from sensing input to the operating interface.

Question 2

Which industries and domains do you focus on?

Accepted Answer

Our main domains are port and logistics, manufacturing, forestry and environment, and security and control. When the problem depends on acoustic, vibration, or ultrasonic signals, our approach can transfer across industries.

Question 3

How are you different from a traditional systems integrator?

Accepted Answer

A traditional SI usually starts from a written specification. We start by defining what needs to be sensed and how the result should fit into operations. Because signal processing, AI models, and operator UX are designed by the same team, context is preserved all the way through delivery.

Question 4

How does your system integrate with existing PLCs or SCADA?

Accepted Answer

We connect through standard protocols such as OPC-UA, Modbus, and MQTT. That lets us add a monitoring layer without requiring a full replacement of field equipment. When needed, we also acquire analog signals directly.

Question 5

Does it work in offline or air-gapped environments?

Accepted Answer

Yes. The system is designed to operate without an external internet connection when needed. Inference runs on field gateways or edge devices, and data stays inside the customer environment.

Question 6

Where is data stored? Does it leave the site?

Accepted Answer

Data is stored only in customer infrastructure or in customer-designated cloud storage. Field data does not automatically flow into Xylolabs systems. If access is needed for early model development, that is handled separately through agreement.

Question 7

How does model retraining work?

Accepted Answer

We design a retraining loop around operating data. Labeling standards, retraining triggers, and deployment procedures are documented as part of operational handoff.

Question 8

Do you supply hardware?

Accepted Answer

We develop and manufacture sensors and gateways in-house, tailored to field conditions. Where it makes sense, we also integrate off-the-shelf equipment.

Question 9

How do we get started?

Accepted Answer

Reach out through admin@xylolabs.com or the contact page. If you share a brief description of the field situation and the problem you want to solve, we can review the context and arrange an initial discussion.

Question 10

How long does a pilot take?

Accepted Answer

Depending on scope, most pilots can produce a first result within 4 to 8 weeks. The biggest variables are data access and equipment readiness on the customer side.

Question 11

How is pricing structured?

Accepted Answer

Pilot work is usually priced as a fixed project fee. After operational adoption, the structure typically shifts to a subscription or maintenance agreement. We shape pricing around scope and scale.

Question 12

What does ongoing support look like?

Accepted Answer

Support covers operational handoff, ongoing monitoring, and model updates after the pilot. The goal is a system that remains maintainable after delivery.

Frequently asked questions