four system types · one connection.
Every operation has systems that already work. AstreaIoT connects without asking you to replace them.
from AstreaIoT to your system, every few minutes.
The connection sends AstreaIoT data to your system. The other direction is built only if your project needs it:
from AstreaIoT to your system
Alerts, events, readings and reports go straight to your ERP, HIS, WMS or BI. Your team does not export files by hand.
signed events · CSV · API or MQTT per project
from your system to AstreaIoT
If you want your catalogs, locations or people in charge to reach the platform from your system, we build it inside the integration project. It does not come out of the box.
catalogs · locations · people in charge
Your team keeps working where it already works, and the data arrives there.
four phases · three to six weeks typical.
technical scoping
Session with your IT team · systems mapping · endpoint identification · field documentation · scope agreement.
design + proposal
Integration architecture · message specification · API contract · detailed quote with locked scope.
development + testing
Implementation · staging environment · joint testing with your team · validation against real loads before production.
production + operation
Production deployment · go-live support · integration monitored as any other operational component.
Standard integrations (common ERP, standard HIS, commercial WMS) typically 3-6 weeks. Higher-complexity integrations (legacy systems, regulatory validation, enterprise security) quoted per scope.
one-time to build · monthly to operate.
The one-time payment covers the engineering work, with no billable hours or surprise adjustments. The monthly fee covers keeping the connection alive while you use it.
when you do not need to integrate.
Not every customer needs it. We tell you when not:
if your team already operates well with the dashboard
AstreaIoT includes web dashboard + mobile app + WhatsApp/email alerts. If your team operates fine with that, you don't need to connect to more systems. Starting with the platform alone is fine.
if your data volume is small
With 1 to 3 sites and few alerts a month, exporting reports from the panel may be enough. Integration makes sense when the volume justifies it.
if your central system has no API or is heavily legacy
Integration may be more complicated than the value it delivers. We tell you before quoting, not after starting the project.
If any of these apply, we tell you before quoting.