Good farming starts with a clearer picture
Every field has a story. Mothmr brings satellite observations, weather and daily farm work into one place, so you can spot changes, plan the next visit and keep your team moving together.
Start with your own fields. Bring in your team when you need to.
From the first observation to the completed job, keep the field, the person and the record connected.
Built around the way work happens in the field.
A little more clarity, every day
Less information scattered across messages and notebooks. One connected workflow for the observations you make, the work you assign and the results you review.
Compare dated satellite observations and available vegetation indices. Add weather context to decide where a closer inspection would be useful.
Turn a field observation into a clear task. Set the location, responsible person, due date and the photos or notes needed to review the work.
Review submitted photos and notes before accepting the job. Keep a field history that explains what happened, who did it and what still needs attention.
A closer look
Explore how your field information becomes useful, practical work.
Keep field names, crops and areas together, with a direct path to their work.
Draw a boundary or import existing parcels. Keep crops, areas and work records connected to the right place.
Sign up
Use dated observations and available indices to guide field inspection.
Dates and usable coverage stay visible. An observation helps guide a visit; it does not replace your knowledge of the land.
Sign up
The Day Suitability Index scores today’s weather, ground, satellite and probe readings against the crop you recorded, and names the factor holding the score back.
A source with nothing current is left out and says so. The score is a starting point for the day, not a crop-health grade.
Sign up
Wind, gusts, humidity and rain hour by hour at the field’s own coordinates, drawn against the wind limit your farm set for field work.
Hours without a forecast stay blank. This is context for planning, not a spraying window or a safety sign-off.
Sign up
Connect the field, person and due date. Review photos and notes when work is submitted.
A submitted task is not yet a verified task. Make the handover from field crew to supervisor clear.
Sign up
Work due today, overdue, blocked and awaiting verification, counted across the fields you supervise, with the jobs behind each number one click away.
These are counts of recorded work, not hours or capacity.
Sign up
What the satellite saw
Not photographs of farming — the product’s own output. Each of these is a parcel Mothmr monitors, drawn from the same satellite bands its readings are computed from, on the date printed beneath it.
Smallholdings a few hundred metres across, packed between canals and villages. The parcel boundary is the unit of work here, not the farm.
An irrigated basin where the crop calendar and the water rota decide everything. Readings here are read against the rotation, not against a season.
Centre pivots on reclaimed desert, each circle its own field. At this scale a supervisor cannot walk the block, which is the case this product was built for.
True-colour imagery at 10 m, the finest the satellite publishes. Parcels Mothmr monitors for its own demonstration records; not customer land and not customer results.
The whole product
One product, every part of it reading the same fields. Where a reading has a limit, the screen that shows it says so.
Where each parcel is, and what the satellite and the sensors recorded there — always with a date.
Draw a boundary on the map, enter its coordinates, or import CSV, GeoJSON, KML or KMZ starting from a downloadable template. Every proposed parcel is previewed before it is saved, and duplicate, invalid or failed rows are listed with their reasons — nothing is discarded quietly. Saving a field starts preparing its satellite history, with the progress shown on its record.
Search fields by name, reference or crop and filter by crop, or find them on an interactive map. Totals show how many fields and how much area you hold, which already have imagery and which are awaiting their first image. Each field shows its crop and stage, its open tasks and attention items, and its latest satellite reading with its date and the share of the field it could assess.
Overview, Weather, Crop monitoring, Satellite analysis and History — with Field sensors when a device is connected — keep the field’s name, crop, stage, area and season in view on every tab. The overview gathers today’s advice, what needs attention, headline readings and the weather; the history sets the work, its evidence, the satellite passes, recent weather and the season in date order, so a handover starts from what actually happened.
Every satellite pass over your field is recorded with its acquisition date and how much of the field it actually covered; a pass the cloud hid stays on the record as exactly that. Choose a year, a day and a pass to see the field in true colour with its boundary drawn on, filter the archive by period, coverage or cloud, and open any pass for its time, cloud figures, resolution and plant-reading statistics.
Dated series for plant vigour, canopy moisture and a chlorophyll-sensitive reading, each with its latest value, the change since a comparable earlier pass and a recent baseline. A sharp drop is told apart from a decline that persists over successive passes, you choose the window, and the measurements behind every comparison — coverage and usable pixels included — are one click away. A change is a reason to visit, not a diagnosis.
Readings in three groups, computed from the same cloud-masked imagery: plant, for the vigour of the canopy; water, for the moisture the crop holds; and soil, for the condition of exposed ground. Map overlays are drawn at true 10 m wherever the bands allow it.
Switch on zone borders over a reading’s map to see where the field is much lower, lower, typical, higher or much higher than the rest of it on that pass, with the strongest outlines around the areas that differ most. Each class shows its average reading, its share of the field and its approximate hectares, and a field that reads evenly is reported as even. Zones point a visit at a place; they are not a treatment map.
One score out of 100 for how today’s conditions suit the crop you recorded, drawn as a flower in which each petal is a factor: temperature, heat and frost, rain, soil and terrain, canopy vigour and canopy moisture — and, with a probe, soil water and soil salt. The weakest factor is named, every reading sits beside its reference range, and a factor with no current data is shown as left out rather than guessed. A daily conditions indicator, not a crop-health grade or a yield forecast.
Where a device is connected to a parcel: soil water content and matric potential, soil temperature and electrical conductivity; air temperature, humidity, dew point, leaf wetness, pressure, rain, wind, gusts and solar radiation; water flow, volume, line pressure and valve or pump state; and battery. Each reading shows its units, depth, measurement and receipt times, freshness and quality flags. Read-only: no device is ever sent a command.
Weather, conditions and advice, each shown beside what it was drawn from.
Current conditions, the next twelve hours of rain and cloud, a five-day forecast and the past ten days, all for the field’s own coordinates, charted beside detailed tables that show the observation time and the forecast location. Official warnings are relayed when the provider supplies them, and a provider we cannot reach is shown as unreachable rather than as no warnings.
Step through the coming hours for wind, gusts, humidity, rain and temperature, with the wind direction and the selected hour’s exact values. A reference line marks the farm’s wind limit for field work — and the crop’s heat limit where it matters — with the hours each is crossed, and hours with no data stay blank rather than reading as calm. Weather context for planning the work, not a spraying window or a safety sign-off.
Daily and seasonal advice for the crop and the growth stage you have recorded, shown beside the readings and thresholds it was drawn from. These are rules, not a language model: the same inputs always produce the same answer, and it guides an inspection rather than replacing it.
With a probe connected and its reference range reviewed, prompts can join the signals: low soil water beside a falling canopy-moisture trend, with heat when it applies; low flow or pressure after a recorded irrigation; plants declining although the probe shows water; a planned irrigation after recorded rain. Device faults are kept apart from field concerns, and each prompt sends someone to look — it does not diagnose a pipe or prescribe water.
Where the crop model covers your region, compare crops by suitability score and class, with the factor that limits each — temperature, rain, soil depth or another soil constraint — and the modelled sowing and harvest timing. A shortlist of up to four alternatives for the coming seasons carries the evidence behind each, with the model’s version and scenario stated. Planning estimates, not a planting guarantee.
Each season is planned, active, completed or cancelled, and its growth stages — from land preparation and planting through flowering and fruit set to harvest, post-harvest and dormancy — carry their dates. Work orders link to the season and stage they belong to, and activating a prepared season previews the tasks it will create, and those it will skip, before anything is made. Stages are configurable per crop and per organization.
From the item that needs review to the verified job and the report that records it.
Detectors read the observation series, the forecast and the task table and raise what deserves a closer look, without repeating a finding you have already acknowledged. Notifications climb a ladder your organization configures instead of piling up unread.
Turn an observation into a task carrying its field, its person, its priority, its due date, its instructions and the proof it requires, across fifteen kinds of work from irrigation checks and scouting to spraying, pruning and harvest. The crew submits photos and notes from a phone; a supervisor verifies the work or sends it back with a reason. The status lifecycle is enforced on the server, so no screen can skip a step.
Assign a job to one or more people, a crew and a responsible supervisor while seeing what each person already has outstanding. Queues for due today, overdue, blocked and awaiting review sit beside the day’s shifts and the fields they cover, with workload by crew, supervisor or crop. Overlapping assignments and shift conflicts are flagged, and going ahead anyway records the reason. These are counts of recorded work, not hours or payroll.
Notes, photos previewed before they are sent, files, measurements with their units, quantities and checklists — and, only with the worker’s consent, the current location. The task shows which required proof is attached and which is still missing, and cannot be completed until it is all there; the supervisor then reviews it beside the original instructions.
Task actions and evidence, photos included, wait on the device and are sent when the connection returns — even after the tab is closed, if the browser keeps its storage. Each item reads saved on this device, waiting to sync, sent or needs attention, and sent is never confused with verified. It covers work pages already opened, not every map and report, and acceptance on real handsets in the field is still pending.
A report for each field and season — its details, satellite record, weather, work, evidence and attention history — and ten organization reports: crop summary, workforce, portfolio health, supervisor workload, task completion, overdue and blocked work, shift performance, attention response, season progress and parcel exceptions. Download CSV, or print and save as PDF from the browser. Every report carries the parcel scope of whoever asked for it, so nobody downloads a field they could not open.
Each person sees their own part of the farm, and your other systems can see it too.
A grower’s home opens on their land and today’s priorities; an owner’s on activity across the organization; a supervisor’s on their fields and the work awaiting review; a worker’s on their own tasks. Due, overdue and blocked work stands out, field priorities come with their reasons, and every figure opens the list of tasks behind it.
An in-app inbox for twelve kinds of notice: a task assigned, due soon, overdue, blocked, awaiting review or reopened; a shift changed; an attention item assigned; severe weather, a plant decline, a new satellite pass or a gap in imagery. Each opens the record it is about, unread notices stand out, and you can mark one or all as read. Notices stay in the app; farm alerts are not sent by SMS or WhatsApp.
An organization workspace holds administrators, supervisors, field workers and viewers, each one scoped to named parcels. A supervisor sees the fields assigned to them and a worker sees the tasks assigned to them — decided on the server, never by hiding a button.
Bizra — بذرة, “seed” — is the guide inside the app. Choose a field and Bizra opens its advice and the evidence behind it, its weather or its tasks, or explains why a recommendation appeared, answering from the records you can access through set menus rather than free conversation. Getting-started steps for each role grow from seed to sprout, plant, flower and fruit as you complete them, and can be dismissed at any time.
For customers who work through an integration, a versioned API with scoped credentials reads fields, satellite observations, weather, advice, activity, reports and operational figures, and accepts field imports, seasons, periods, shifts, tasks and attention items. Signed webhooks report tasks, attention, weather, observations and shifts, retrying a bounded number of times. Provisioned with your team; access stays within the organization and its fields.
An organization can present the web workspace with its own name, logo and colour theme, so the people who use it every day see a tool that is recognisably theirs. It is set up with your team as part of an integration-led delivery, and it brands the web workspace; it is not a separate app in the app stores.
Sensor platforms Mothmr reads from
Each adapter is written against that platform’s published documentation and tested against payloads from it. None has yet been run against a live account, so none of these is a certified integration or a partnership — the setup screen says so on every connection until somebody completes a real connectivity test.
Also in the product
Give each person the context they need, without asking everyone to manage everything.
See what needs your attention across your fields today, with the readings, the weather and the priorities behind it, and keep a practical record of what was done.
See which fields and teams need follow-up: unresolved and overdue work, what has been verified, and reports that show progress with the records behind it.
Coordinate assignments across your fields. See what is due, what is blocked and which completed tasks are ready for review.
Find the right task and its field. Read the instructions, record progress and attach the photos or notes your supervisor needs.
Review what changed, what supports the reading and what was done: dated measurements, crop context, field history and reports, within the fields you have been given access to.
Bring field records, observations and work events into your own systems through the partner API, and present the workspace under your own name and colours.
Make it your own
Choose the start that fits how you farm.
Create your account and add your first field. Explore satellite history, available weather information and your own work records, all linked to the land you manage.
Create an account Continue with GooglePlan a demonstration around your fields and your workflow. We agree the roles, field access and review process with you before setting up your organization workspace.
Request a demoBefore you get started
A useful tool should be clear about what it can do, and where your judgement still matters.
Request a demoNo. The satellite passes every few days, and clouds can hide the ground. Each reading shows its acquisition date and usable coverage. When a pass is obscured, the last usable reading remains dated and visible.
Weather is a point estimate for the field’s coordinates, not a measurement within every part of it. Some layers and official alerts need a configured provider. Unavailable information is marked as unavailable.
No. It scores, out of 100, how today’s available conditions — weather, the ground, recent satellite readings and any connected probe — suit the crop you recorded. It is not a measure of crop health, a season forecast or a yield prediction. Factors without current data are left out and listed, so compare two scores only with their inputs in view.
No. A falling reading, a zone lower than the rest of the field or a low probe value is a reason to inspect, shown with the dates and figures behind it. Mothmr does not diagnose pests or disease, prescribe a product or a dose, or calculate an irrigation amount — the person in the field decides.
Task updates and evidence can queue on the device until connectivity returns, where supported. They remain labelled as waiting to sync. Real-handset field acceptance is still pending; confirm the workflow on your devices before relying on it.
Yes. Draw boundaries on the map or import CSV, GeoJSON, KML or KMZ files. Review the proposed parcels before saving them. Each new field enters its own processing queue.
Access follows workspace membership, role and assignment. Supervisors see their assigned fields, and workers see the tasks assigned to them. Organization access is configured with your team.
There is no published price list yet. For a team pilot, we agree the fields, workflow, duration and scope with you before discussing the price. Tell us what you need through the enquiry form.
Tell us a little about your farm and the work you want to coordinate. We’ll use these details to understand the demonstration you need.
