a recipe is the minimum unit of deployment.
It's not a standalone sensor or a generic dashboard. It's the pre-wired combination of five pieces:
sensor
Specific to the use (submersible temperature, three-phase sub-metering, multi-parameter CO₂, etc.) — from the curated AstreaIoT catalog, not generic. See the full catalog at /sensores.
threshold
Calibrated to your real operation, not factory defaults.
alert routing
WhatsApp + email + push, with recipients by role and schedule.
report
Formatted per the applicable regulation or audit (NOM-059, NOM-036, FEUM, NOM-251, NOM-007-SSA3, etc.).
escalation chain
Who responds, in what order, how long before levelling up.
Each recipe lives in our canonical catalog, ready to deploy. You combine them per site based on your operation.
the eleven capability families.
four examples · one bundle per customer.
Recipes aren't sold individually. They're assembled into per-site bundles based on your operation:
a chain pharmacy
3-5 cold chain + 2 energy + 1 access protection + 1 IAQ
a supermarket branch
8-12 cold chain + 4 energy + 2 people + occupancy + 1 panic protection
an industrial site
3-5 energy + 2 water/leaks + 1-2 IAQ + 2 gas protection + BMS integration if applicable
an Airbnb property
1 climate + 1 people/occupancy + 1 leak protection
a mid-market hotel · hospitality
4-6 kitchen cold chain + 3 energy + 2 conference IAQ + 1 pool/spa + 1 backup generator
across twenty physical magnitudes.
Every recipe combines one or more curated sensors from the AstreaIoT catalog — twenty magnitudes (temperature · humidity · CO₂ · gases · sub-metering · water · presence · vibration · tilt · GPS · and more) across ~45 curated hardware families + extended LoRaWAN ecosystem. The full catalog, magnitudes, and sensor → recipe → cluster logic live on their own page.