ON DEVICE
No link needed.
Threshold checks, safety interlocks, local filtering, immediate alerts.
EDGE & CONNECTED SYSTEMS
Connect physical operations to intelligence and action.
Stacx24 engineers edge intelligence, telemetry and connected software systems that transform physical events into useful operational information.
Edge intelligence, telemetry and connected operational systems. We do not manufacture electronic products.
EDGE SYSTEM · ILLUSTRATIVE
Twenty-second silent sample with on-screen text: focused AI agents; connected applications and workflow automation; sensors, edge processing and telemetry; human approval and measurable outcomes.
Video playback is unavailable. Download the sample film.
EDGE PROCESSING
Process information where it makes operational sense.
Not every reading needs to travel to the cloud, and not every decision can wait for it. We place processing on the device, at the site gateway or in the cloud according to what the operation needs: how fast the response must be, how much the link can carry, what happens when it drops, and what should never leave the building.
AT THE EDGE
Site-wide context.
Aggregation, local models, buffering through outages, privacy-preserving processing of camera data.
IN THE CLOUD
Fleet-wide intelligence.
Trends across sites, model training, dashboards, integration with operational applications.
LOCAL DECISIONS
Act on site without a round trip.
REDUCED LATENCY
Reduce response delays by processing close to the source.
BANDWIDTH
Send summaries and exceptions, not raw streams.
INTERMITTENT LINK
Keep operating and buffer until the uplink returns.
LOCAL FILTERING
Discard noise at the source so what arrives means something.
FASTER ALERTS
The person on site hears first.
PRIVACY
Process camera and personal data locally; transmit only derived events.
TELEMETRY
Telemetry turns physical behaviour into operational context.
A sensor reading on its own is a number. Classified into the right kind of signal and placed next to the records of the operation, it becomes something a rule, a model or a person can act on. We design the telemetry model before the first device is installed.
- STATE: What is it right now? On, off, open, closed, running, idle. ILLUSTRATIVE SAMPLE · EDGE NODE 03: pump_02.state = RUNNING. ROUTES TO: DASHBOARD.
- EVENT: What just happened? A door opened, a cycle completed, a threshold crossed. ILLUSTRATIVE SAMPLE · EDGE NODE 03: door_dock_3 OPENED 09:14:02. ROUTES TO: RULES · WORKFLOW.
- HEALTH: Is the device itself well? Heartbeat, power, storage, firmware. ILLUSTRATIVE SAMPLE · EDGE NODE 03: node_03 heartbeat OK · 41 d uptime. ROUTES TO: FLEET MONITORING.
- ERRORS: What has gone wrong? Sensor offline, out of range, comms lost, faults. ILLUSTRATIVE SAMPLE · EDGE NODE 03: probe_b7 NO READING 120 s. ROUTES TO: ALERT · OWNER.
- MEASUREMENT: How much? Temperature, pressure, flow, count, level. ILLUSTRATIVE SAMPLE · EDGE NODE 03: boiler_b7.temp = 71.4 °C. ROUTES TO: DATA · INTELLIGENCE.
- CHANGE: What is different from before? A setpoint, a schedule, a configuration. ILLUSTRATIVE SAMPLE · EDGE NODE 03: setpoint 70.0 → 68.0 by j.okafor. ROUTES TO: AUDIT LOG.
- TREND: Where is it heading? Drift, degradation, seasonal pattern. ILLUSTRATIVE SAMPLE · EDGE NODE 03: temp +0.3 °C / wk over 6 wk. ROUTES TO: INTELLIGENCE · REVIEW.
STATE
What is it right now? On, off, open, closed, running, idle.
pump_02.state = RUNNING · routes to DASHBOARD
EVERY SIGNAL IS TIMESTAMPED, ATTRIBUTED TO A DEVICE AND JOINED TO AN OPERATIONAL RECORDLAST SIGNAL 0 S AGO · 0 FAULTS
ENGINEERING CAPABILITIES
From the sensor to the decision.
Listed by layer, in the order a signal travels: IoT and edge systems engineering from sensor to edge AI to the cloud. We select, integrate and program these components; we do not manufacture them.
- 01 · SENSE: Capture the physical event. Sensors, Cameras.
- 02 · DEVICE: Read, control, run local logic. ESP32, Microcontrollers, Device Control.
- 03 · EDGE: Process and buffer on site. Raspberry Pi, Edge Linux, Local Processing.
- 04 · TRANSPORT: Move signals reliably. MQTT, Telemetry, Cloud Ingestion.
- 05 · DECIDE: Turn signals into decisions. Rules, AI-Assisted Decisions, Alerts.
- 06 · OBSERVE: See the system and the operation. Dashboards, Observability.
01 · SENSE
Capture the physical event
- Sensors
- Cameras
CORE SYSTEM MODEL
The system is the product. Technology is a component.
- Not every step needs AI.
- Some need rules.
- Some need software.
- Some need edge processing.
- Some need people.
We engineer the right combination.
Research assistance
IN THE OPERATION
A document arrivesFrom the research team
01 / 08EVENT
A new document arrives
Field study notes
- Source document received
- Original retained
- Ready to review
Received
A research document starts the work. The original stays available throughout.
02 / 08CONTEXT
Bring the background together
Document + background
- Source details attached
- Related records found
- Approved labels loaded
Context attached
Existing records, source details and the approved label list give the document context.
03 / 08PROCESSING
Check the details first
Document checks
- Duplicate check complete
- Required details present
- Text ready for review
Checks complete
Software checks for duplicates and missing information before any AI suggestion.
04 / 08INTELLIGENCE
Suggest a label, within scope
Suggested label
- Field study
- Supporting passage highlighted
- Awaiting researcher review
Suggestion only
AI proposes a label from the approved list. It cannot publish the label itself.
05 / 08DECISION
A researcher makes the decision
Label review
- Source passage checked
- Suggested label reviewed
- Field study approved
Reviewed by researcher
The researcher reads the supporting passage and approves or corrects the suggestion.
06 / 08ACTION
Update the research record
Research record
- Label: Field study
- Source linked
- Review retained
Saved to record
Only the approved label enters the record, alongside its source.
07 / 08OBSERVATION
Record what actually happened
Activity record
- Suggestion recorded
- Reviewer decision recorded
- Save confirmed
Outcome recorded
The system records the suggestion, the review and the saved result so the team can inspect them.
08 / 08IMPROVEMENT
Review the labelling rules
Next-cycle guidance
- Review corrections
- Agree guidance changes
- Use approved guidance next time
Feedback to the next event
The team reviews corrections and agrees changes to the guidance before the next document.
Each outcome informs the next cycle.
- 01 · EVENTA new document arrives
A research document starts the work. The original stays available throughout.
- 02 · CONTEXTBring the background together
Existing records, source details and the approved label list give the document context.
- 03 · PROCESSINGCheck the details first
Software checks for duplicates and missing information before any AI suggestion.
- 04 · INTELLIGENCESuggest a label, within scope
AI proposes a label from the approved list. It cannot publish the label itself.
- 05 · DECISIONA researcher makes the decision
The researcher reads the supporting passage and approves or corrects the suggestion.
- 06 · ACTIONUpdate the research record
Only the approved label enters the record, alongside its source.
- 07 · OBSERVATIONRecord what actually happened
The system records the suggestion, the review and the saved result so the team can inspect them.
- 08 · IMPROVEMENTReview the labelling rules
The team reviews corrections and agrees changes to the guidance before the next document.
Everyday operations
IN THE OPERATION
A request arrivesFrom the operating team
01 / 08EVENT
A request starts the work
New work request
- Request received
- Source application linked
- Handoff opened
Received
An incoming request starts a handoff between the tools your team already uses.
02 / 08CONTEXT
Attach the details once
Request background
- Existing record attached
- Current state checked
- Owner identified
Context attached
The system brings together the request, existing records and its responsible owner.
03 / 08PROCESSING
Let the rules route the work
Connected applications
- Request inbox → work queue
- Required details checked
- Work queue → owner workspace
Handoff prepared
Defined rules check the request and pass its details between connected applications.
04 / 08INTELLIGENCE
Rules are enough here
Routing rule
- A required detail is missing
- Exception route selected
- Named owner notified
No AI needed
This example needs no AI decision. Defined rules identify an exception and send it to its owner.
05 / 08DECISION
The owner resolves the exception
Exception review
- Exception opened
- Missing detail supplied
- Owner confirms next step
Reviewed by owner
A named person supplies the missing detail and confirms that the work can continue.
06 / 08ACTION
Complete the handoff
Completed handoff
- Confirmed details transferred
- Next application updated
- Owner notified
Handoff complete
The confirmed information reaches the next application and the work continues.
07 / 08OBSERVATION
Keep the outcome visible
Activity record
- Exception recorded
- Resolution recorded
- Handoff confirmed
Outcome recorded
The system records completion and exceptions so the team can see what happened.
08 / 08IMPROVEMENT
Review the handoff rules
Next-cycle guidance
- Review recurring exceptions
- Agree routing changes
- Apply approved rules next time
Feedback to the next event
The team reviews repeated exceptions and approves rule changes for future requests.
Each outcome informs the next cycle.
- 01 · EVENTA request starts the work
An incoming request starts a handoff between the tools your team already uses.
- 02 · CONTEXTAttach the details once
The system brings together the request, existing records and its responsible owner.
- 03 · PROCESSINGLet the rules route the work
Defined rules check the request and pass its details between connected applications.
- 04 · INTELLIGENCERules are enough here
This example needs no AI decision. Defined rules identify an exception and send it to its owner.
- 05 · DECISIONThe owner resolves the exception
A named person supplies the missing detail and confirms that the work can continue.
- 06 · ACTIONComplete the handoff
The confirmed information reaches the next application and the work continues.
- 07 · OBSERVATIONKeep the outcome visible
The system records completion and exceptions so the team can see what happened.
- 08 · IMPROVEMENTReview the handoff rules
The team reviews repeated exceptions and approves rule changes for future requests.
Connected fields
IN THE OPERATION
A field reading arrivesFrom a connected sensor
01 / 08EVENT
A sensor reads the field
Incoming field reading
- Sensor reading received
- Field identified
- Reading time attached
Received
A new field reading starts the cycle, connecting conditions on the ground to the system.
02 / 08CONTEXT
Put the reading in context
Field background
- Field history attached
- Recent readings loaded
- Current conditions attached
Context attached
Field history and recent conditions help the team interpret the new reading.
03 / 08PROCESSING
Check the signal near the field
Edge processing
- Local checks run
- Incomplete readings flagged
- Relevant readings forwarded
Local checks complete
Local edge checks validate readings before relevant information reaches the monitoring application.
04 / 08INTELLIGENCE
Prepare a suggested response
Response proposal
- Field context considered
- Suggested response prepared
- Sent for agronomist review
Suggestion only
The system uses the checked information to propose a response within its defined scope.
05 / 08DECISION
The agronomist reviews
Agronomist review
- Conditions reviewed
- Proposal checked
- Response approved
Reviewed by agronomist
The agronomist checks the proposal and approves or adjusts it before it reaches the operator.
06 / 08ACTION
Send the approved proposal
Operator work item
- Approved proposal attached
- Instructions available
- Delivered to operator
Ready for the operator
The approved proposal reaches the operator with the instructions they need.
07 / 08OBSERVATION
Keep watching the conditions
Field activity record
- New readings recorded
- Operator reports attached
- Outcome ready for review
Observation continues
New readings and operator reports help the team understand what happened next.
08 / 08IMPROVEMENT
Review the next field cycle
Next-cycle guidance
- Review field observations
- Agree guidance changes
- Use approved guidance next time
Feedback to the next event
The agronomist reviews the observations and agrees guidance for the next cycle.
Each outcome informs the next cycle.
- 01 · EVENTA sensor reads the field
A new field reading starts the cycle, connecting conditions on the ground to the system.
- 02 · CONTEXTPut the reading in context
Field history and recent conditions help the team interpret the new reading.
- 03 · PROCESSINGCheck the signal near the field
Local edge checks validate readings before relevant information reaches the monitoring application.
- 04 · INTELLIGENCEPrepare a suggested response
The system uses the checked information to propose a response within its defined scope.
- 05 · DECISIONThe agronomist reviews
The agronomist checks the proposal and approves or adjusts it before it reaches the operator.
- 06 · ACTIONSend the approved proposal
The approved proposal reaches the operator with the instructions they need.
- 07 · OBSERVATIONKeep watching the conditions
New readings and operator reports help the team understand what happened next.
- 08 · IMPROVEMENTReview the next field cycle
The agronomist reviews the observations and agrees guidance for the next cycle.
Read the complete system model
- EVENT
Something happens in the operation.
- CONTEXT
Records, history and state are attached.
- PROCESSING
Rules, software and integrations do the deterministic work.
- INTELLIGENCE
One bounded AI component, where judgement can be modelled.
- DECISION
A named person decides where it matters.
- ACTION
Something changes in the world.
- OBSERVATION
Telemetry and monitoring record what happened.
- IMPROVEMENT
The loop feeds back into the next event.
RELIABILITY
Designed for the day the link drops.
Physical systems fail in physical ways: power, weather, a cable, a moved router. The system is engineered to keep operating, tell someone, and recover without a site visit.
Connectivity loss
Local logic keeps running. Alerts raise on site first.
Local buffering
Readings are stored at the edge and forwarded in order when the uplink returns.
Retry behaviour
Backoff, deduplication and idempotent delivery. Nothing is sent twice or lost.
Device health
Heartbeat, temperature, storage and firmware state reported per device.
Recovery
Watchdogs, safe restarts and remote recovery without a site visit.
Authentication
Per-device identity and credentials. Unknown devices are refused.
Encrypted communication
TLS between device, edge and cloud. Keys rotate.
Monitoring
Fleet and site state observable in one place, with an owner for each alert.
Failover
Secondary uplinks and redundant gateways where the operation justifies them.
Related work
AI + Edge Agriculture
Field sensors and edge inference feeding irrigation and crop-condition decisions, buffered through intermittent connectivity, with an agronomist approving changes before they reach the field.
SENSOR · EDGE · TELEMETRY · AI AGENT · HUMAN APPROVAL
NEXT STEP
Have a physical operation that needs better visibility or intelligence?
Tell us what happens on site and what you cannot see today. We will propose where to sense, where to process and who should act.
Discuss an Edge System
No technical specification required. Start with what happens on site.