01Prototype stage
Temperature
Track heat and cold as the foundation of cold-chain observation.
PRECISION IN EVERY JOURNEY.MULTI-SENSOR LOGISTICS / PRODUCT VISION
SMALL FORM. SERIOUS HARDWARE.
Small tag.
Every journey.
From changing cargo conditions to your team’s next move.
More ways to sense. One system for every journey.
+ KAPIBARA TAG Enclosure concept · Not final hardware
±0.5°C
Board-level accuracy target
30days
Offline recording target
Compact
Designed to travel with cargo
Design targets, pending prototype validation. Accuracy is provisionally assessed at 0–50°C without condensation; offline recording assumes one reading every 10 minutes.
01 / SENSING THE JOURNEY
Beyond temperature.
Sense more of the journey.
Our vision combines single- and multi-sensor tags around the needs of each cargo type.
02Planned
Humidity
Observe moisture conditions around humidity-sensitive cargo.
03Planned
Light
Capture light exposure events to inform transport reviews.
04Planned
Shock & vibration
Observe mechanical stress during handling and transport.
05Planned
CO₂
Explore richer environmental records for specialized cargo.
Temperature leads prototype validation. Other sensors and combinations are planned in stages, not fitted to every current tag. Light alone does not establish opening; shock alone does not establish damage.
02 / INDUSTRIAL DESIGN
Less bulk.
More thought.
Compactness is a series of considered choices.
Thoughtful engineering. A lighter presence on every journey.
FORM FOLLOWS PURPOSE.ENCLOSURE STUDY / GRAPHITE
- Sensor Tag size
- To be announced
Compact from within.
Compact and easy to place, bringing environmental records closer to cargo. Final form and dimensions will follow product validation.
Closer to the true temperature.
Every reading matters. Whole-device validation will assess measurement performance, building a sound basis for understanding transport conditions.
Made for another journey.
Maintenance and reuse are considered from the start. Each deployment is designed with the next journey in mind; actual service life remains to be validated.
03 / ONE CONNECTED SYSTEM
From one shipment.
To your whole team.
Sense. Connect. Analyze. Act. A system envisioned for the entire journey.
PLANNED ARCHITECTURE · DATA OUT, ACTION BACK
SENSE. CONNECT. ACT.
Planned system · illustrative flow
From cargo tags to cloud intelligence, then to your team.
Alerts travel back along the same chain; execution receipts return to the cloud.
Select a node to explore its roleSensor Tag
Single or multiple sensors. Local records. Mesh relaying as needed.
Hub · optional
Optional local aggregation, storage and forwarding.
Connector
An authorized phone or dedicated connected device links field and cloud.
Backend
Data ingestion and storage, with identity, shipment and command management.
Data Engine
Apply user-defined rules, analyze data, generate alarms and warnings.
Portal · App · Notifications
Give teams records, notifications and a way to acknowledge and follow up.
Bring the alert back to the cargo.
Cloud events route through Backend, Connector and optional Hub to the target tag’s red LED; execution acknowledgments return to the user interface. Software evaluates rules; tags display the result.
Offline need not mean unrecorded.
Planned local storage and recovery sync preserve records. A phone receiving data can use cached, supported rules for local alerts; remote cloud alerts require connectivity.
Start light. Extend with purpose.
The first phase uses a phone Connector without a standalone Hub. Dedicated devices and optional Hubs follow evaluation; no reachable path means no promise of live remote alerts.
04 / BUILT FOR WHAT COMES NEXT
Different cargo.
Its own rules.
Turn sensor data into events teams can follow up. Transport information for real decisions. Platform capabilities below are planned.
Configure by product
Planned templates bind rules to products, boxes or pallets, combining thresholds, duration and trends with preserved rule versions.
Add location context
Planned location rules use valid Connector positions for zone entry, exit, dwell and later route checks. Tags have no onboard GPS; offline tracks are not invented.
From alerts to follow-through
Planned Portal, mobile and notifications bring together charts, gaps, alarms and warnings, with event acknowledgment, handovers and report exports.
Long-term vision
More journeys. One continuous story.
A phased vision for road, sea and air, with reuse and a 180-day service-cycle target. Cryogenic and specialized life-science uses need separate validation. The cycle target is not proven battery life; air-transport suitability also needs confirmation.
Use cases
Every sensing point.
A clearer journey.
Six use cases. One monitoring vision connecting cargo, field operations and teams.
All use cases ↗05 / RESEARCH CASE STUDIES
Real challenges.
Ideas worth testing.
From food cold chains to life sciences, understand what cargo faces along the way.
These are published research cases, not completed Kapibara customer projects. Product directions are proposals awaiting pilot validation; software will follow its product definition.
01Food cold chains
One truck. More than one temperature.
Research finding
Citrus transport research observed temperature differences across cargo positions. One sensor may not represent the whole load, and air temperature is not fruit-core temperature.
Kapibara’s proposed direction
We propose comparing readings from several positions with reference instruments to explore local excursions a single point might miss.
02Loading & handovers
Keep the journey connected.
Research finding
Food supply-chain research identified issues with loading, temperature fluctuations in transport and data sharing. A reading at arrival cannot reconstruct the full journey.
Kapibara’s proposed direction
We propose testing offline recording and continuity across authorized handovers, keeping any gaps clearly visible.
03Vaccine transport & storage
Too warm. Too cold. Both matter.
Research finding
A vaccine study in Mexico observed exposure to low temperatures. An excursion alone does not establish vaccine failure; quality assessment remains product-specific.
Kapibara’s proposed direction
We propose retaining evidence of high temperatures, low temperatures and missing readings to support quality investigations, without automatically deciding product usability.
04Clinical samples
Temperature tells only part of the story.
Research finding
A US blood-shipping study found that temperature and exposure time affected some cell measures studied. The results do not generalize to all clinical samples.
Kapibara’s proposed direction
We propose linking temperature records with collection, handover and processing times in a parallel pilot, with rules defined by the laboratory protocol.
Life-science uses require product-specific validation. The current temperature concept does not establish drug-release suitability or cryogenic, vibration or CO₂ monitoring capability.