ZeroFarm

Urban farming in Southeast Asia is fragmented: small city farms grow without consistent buyers, restaurants source produce through traditional distributors with multi-day delivery chains, and agronomists have no channel to monetize remote expertise.

ZeroFarm connects all three on one platform. Farms publish growing capacity and crop types. Restaurants post RFQs with delivery specs — nearby farms respond with quotes. Geo-matching surfaces the closest verified farm, so fresh produce travels hours instead of days. Agronomists join as specialists: they review farm journals and environmental logs directly in the platform, assign corrective tasks, and deliver guidance without an on-site visit.

Platform modules, by role:

Farmers get a growing recipe library (20+ validated blueprints for arugula, basil, spinach — with phase-by-phase temperature, humidity, CO2, and nutrient targets), crop cycle tracking tied to active orders, a worker portal for daily task assignment, an auto-populated planting calendar derived from accepted orders, and AI climate guidance that works from manual log entries or live sensor data.

Buyers (restaurants, stores) get the produce marketplace with standing orders for recurring supply, farm profiles with ratings, and real-time order tracking from planting through harvest and delivery.

Agronomists get a remote consultation interface: annotated task lists, environmental log access, and utilization analytics.

No hardware required to start. The platform runs on manual log entries — IoT sensor integration is an optional upgrade. Thailand is the target market; the first pilot is planned for Phuket.

ZeroFarm is backed by CimpleO Group.

Engineering at a glance

• Stage: in development. ZeroFarm is an affiliated company. We list engineering facts only.
• Backend: Fastify 5 on Node with strict TypeScript, zod for validation and the OpenAPI document, Prisma 7 on PostgreSQL through the pg driver. The separate backend repository holds 630 commits.
• Database: the new baseline has 20 tables, two database roles (migrator and application) and a generated row-level policy on 10 tables. It has 14 migrations; 35 migrations of the earlier schema are frozen.
• Migration: the Next.js app is moving from direct Supabase calls to our own API, with a self-hosted PostgreSQL on a VPS as the target.
• Web app: Next.js with PWA support and Leaflet maps.

Questions about the engineering behind ZeroFarm? Contact us.