Skip to main content

Platform overview

One record, and everything else hangs off it

Most farm software is a collection of tools that happen to share a login. This is a single record — customer, farm, barn, flock, week — that production data, feed analysis, alerts, diagnostics and reports all attach to.

The hierarchy

Structured the way an operation actually is

A company runs several farms. A farm has several barns. A barn houses one flock at a time and remembers every flock before it. Every week of data belongs to exactly one flock cycle.

  1. 01

    Customer company

    The tenant boundary. Everything below belongs to it.

  2. 02

    Farm / location

    A physical site, with its region and the species it runs.

  3. 03

    Barn / house

    A housing unit. One active flock at a time for layers.

  4. 04

    Flock

    Genetics, placement, production type, feed and lifecycle.

  5. 05

    Weekly data

    Performance, environment, diet name and comments.

What the platform does

Nine capabilities, one set of numbers

Data capture

The official Devenish template, saved mappings for the spreadsheet you already keep, or guided manual entry. Historical files can be uploaded in bulk.

Validation

Required fields, dates, duplicates, units, impossible values and statistical outliers — reported before anything is committed, never after.

Calculation engine

One authoritative service for every derived value. Dashboards, alerts, benchmarks, reports and the mobile app all read the same numbers.

Genetic standards

Administrator-managed, versioned and published. Old reports keep the standard that produced them.

Peer benchmarking

Anonymous like-for-like cohorts with a minimum size and direction-aware top-performer figures.

Alerts

Configurable rules against standards, peers, trends or missing data, with comments, assignment and resolution history.

Feed intelligence

Versioned formulations with tolerances, compared against uploaded laboratory results.

Reports

Generated from an immutable snapshot, so a report does not silently change when later data is corrected.

Diagnostics

A reusable framework for photo-based measurements that write back to the same flock record.

Design principles

Decisions we made early, on purpose

Raw and calculated data are stored separately

What you entered is kept exactly as you entered it, with its unit and its source. Derived values are stored alongside with the formula version that produced them. That is what makes recalculation safe and reports reproducible.

Species is configuration, not code

Metrics, units, plausibility ranges, standards, templates and alert rules are data. Adding broilers or swine is product work, not a rebuild of the foundation.

Nothing is half-imported

A file with a blocking error imports zero rows. There is no partial state to reconcile later.

Unapproved science is not presented as science

Where a formula, threshold or scoring method has not been approved by our nutrition team, the platform says so rather than filling the gap with a plausible guess.

Bring a spreadsheet. We will show you what it reads.

The most useful demo is the one that runs against your own tracker.