Eywa connects the sensors and valves you already own to an AI agronomist your farm can actually talk to — over WhatsApp or Telegram, in Malayalam, Hindi or English. One Go binary. Runs on your own hardware. Keeps thinking offline.
Every sensor vendor ships its own closed app. Every irrigation controller wants its own login. A working farm ends up with seven dashboards nobody opens — because farmers don't open dashboards. They open WhatsApp. Eywa is the missing layer: one open runtime that speaks every device's protocol on one side, and the farmer's own language on the other.
Signals travel up from the soil; language travels back down to the farmer. Everything in between is open — and everything below is running code, not roadmap.
MQTT today — credentialed, TLS-ready, with a YAML topic-mapping DSL. A full simulated Kerala pepper farm ships in the binary (eywa sim), so the whole loop runs with zero hardware.
A persistent SQLite memory of devices, readings, events, conversations, grants and the audit chain. The agent never starts a conversation from zero — and never loses history to a reboot.
Anthropic, or any OpenAI-compatible endpoint including local Ollama — stdlib HTTP, no SDKs. Hard per-farm daily token budgets are enforced in code, not policy.
Telegram and WhatsApp Business, in Malayalam, Hindi or English. Farmer identity is platform-verified and bound at pairing — it's what action confirmations check against.
The founding principle, and the load-bearing design (ADR 0009): an agent that will tell you anything, instantly — and only touches the physical farm through a deterministic rule engine, with your explicit permission, inside limits you set.
Disease risk at 2 am, irrigation math mid-harvest, a market question in Malayalam. Advisory is unlimited within the farm's own token budget — no gatekeeping between a farmer and an answer.
No action runs without a live, operator-issued grant. Every actuation asks the bound farmer identity first, runs inside hard limits (duration, per-day, time-of-day), and lands in a hash-chained audit log that is never pruned. The permit type has no public constructor — possession is proof the engine approved it.
Open, versioned playbooks in a SKILL.md format with a deterministic trigger evaluator — no LLM in the decision path. Written to be reviewed by agronomists, not just engineers.
Early warning for Phytophthora foot rot from soil moisture and humidity patterns. Ships in the repo today, marked PROVISIONAL until an agronomist signs off on the thresholds — the caveat is part of the advisory.
A skill is one SKILL.md file: crops, required sensors, trigger thresholds, and the advisory text in each language. Fork the pepper skill and adapt it — the evaluator does the rest.
Pre-pilot. Engineering is complete through v0.4 — the repo is green end to end (race-tested, linted, safety-fuzzed) and every feature above is demoable today with eywa sim, no hardware needed. Field work is what stands between here and a real farm.