Smart technology. Sustainable food. Stronger communities.
Technology

Useful intelligence, with the grower still in control.

MarketBrug is evaluating a layered, vendor-neutral approach to smart irrigation for container gardens. Capability labels below distinguish pilot foundations from planned and future work.

01
Available at pilot

Plant and garden layer

Central Texas-adapted edible plants, appropriate containers or beds, growing media and supports configured for a named growing scenario.

Data and purposeGarden type, crop selection, planting date and grower observations.
02
Available at pilot

Drip-irrigation layer

Low-pressure drip lines, emitters and straightforward schedules designed around the containers or beds in the pilot configuration.

Data and purposeWatering schedule and grower-recorded irrigation actions.
03
Planned

Sensor layer

Tested third-party sensors may provide soil-moisture, temperature and sunlight readings as operational indicators rather than laboratory measurements.

Data and purposeTime-stamped sensor readings, device status and data freshness.
04
Planned

Controller and automation layer

Certified third-party timers or controllers may run bounded watering schedules. Manual operation and clear overrides remain part of the design.

Data and purposeSchedule settings, controller status and recorded watering events.
05
Planned

Data and alert layer

Readings and garden context may support condition-based alerts for stale data, unusual conditions and practical events that deserve the grower’s attention.

Data and purposeAlerts, acknowledgements and actions taken. Notifications are intended for useful events, not constant messaging.
06
Future development

AI guidance layer

AI-assisted care and problem diagnosis may combine approved crop playbooks with garden context to explain possible next steps, assumptions and confidence.

Data and purposeThe minimum context needed to create guidance. Photos and precise location would be optional if introduced.
07
Available at pilot

Grower control and manual override

The grower remains responsible for the garden. Basic irrigation and care must remain understandable when connectivity or a digital service is unavailable.

Data and purposeGrower preferences and optional feedback used to improve future guidance.
Responsible automation

Clear limits are part of the design.

AI may help explain conditions, seasonal choices and possible next actions. During the pilot, bounded controller rules—not AI—would govern any scheduled watering.

Low-confidence or contradictory conditions should ask for a grower check or human review. Basic irrigation must remain operable if the app, cloud service, AI provider or internet connection is unavailable.

Privacy by design

Collect garden data for a defined reason.

A connected pilot may use garden configuration, readings, device health, alerts and grower actions to provide guidance and evaluate reliability. Personal data should be minimized; photos and precise household location would remain optional if introduced.