Skip to content

Systems · What we build

Built for no signal, gloves on, and records that hold up.

Mule builds custom data systems for livestock operations and the companies that move and buy their animals. Every build starts from your operation, not from a product we need to sell you.

Start a projectSee the work

01What we build

Eight kinds of system, one record underneath.

Descriptive labels, not products. Every build is custom, and most projects combine several.

01 · Records

One record per animal, with provenance on every fact.

Identity, origin, growth, health, movement and outcome for each head. Every fact is tagged scanned, imported or inferred, and a missing fact stays visible as a gap.

EID · SIRE · BRIX · ADG · WITHDRAWAL

02 · Field apps

Phone and tablet apps for the alley, the chute and the cab.

Built to work with no signal and sync when the crew is back in range. Large targets, one-hand flows, EID readers over Bluetooth, readable in sun and in a dark barn.

OFFLINE · QUEUED · SYNCED

03 · Hauling

Orders, dispatch, counts and signatures on every load.

Yards order, dispatch fills the week, drivers deliver, and every head is counted at pickup and at the gate, with a signed bill of lading frozen at delivery.

BOL · ETA · 28 H

04 · Portals

One place for buyers, growers, yards or vets to see their part.

Each party sees what it is allowed to see and nothing else. Permissions live at the data layer, so a report and a screen can never disagree about who may see a row.

ROLES · SHARING · AUDIT

05 · Dashboards

Figures with lineage, not decoration.

Closeouts, cost per head, outcome by source or sire, loads on time. Every number can be traced back to the records it was built from.

CLOSEOUT · COG · ON-TIME

06 · Integrations

Market data in, accounting out, registries next.

USDA market reports and accounting exports today. Herd software, Sanitel and RVO I&R are planned and listed as planned until they are built.

AMS · CSV · API

07 · Data infrastructure

Pipelines, the animal record and the history behind it.

Imports from paperwork and spreadsheets, matching by EID, append-only history, nightly replicas for reporting, and exports in open formats whenever you ask.

LINEAGE · REPLICA · EXPORT

08 · Hardware, with the tag

Readers, field devices and the Biometric EID Tag.

Reader integrations and field devices today. The Mule tag is in development, with pilot farms from 2027.

BLE · EID · PILOT 2027

02 · Built for the field

Works where the animals are.

Barns, hutches, chutes and trailers have poor signal and busy hands. Mule field apps keep working offline, queue every action with its own timestamp, and sync when the crew is back in range.

Device state · example

  • Offline-first

    Reads, counts and treatments are saved on the device first, then synced.

  • EID readers

    Bluetooth wand and panel readers feed the record directly. No retyping of 15-digit numbers.

  • Gloves-on interface

    Large targets, high contrast, one-hand flows, nothing that needs a fine tap.

  • One template for paper and screen

    Where paper stays, the printed sheet and the screen hold the same fields in the same order.

03Automation

The office stops retyping.

Most of the work in livestock paperwork is copying the same fact from one sheet to another. Mule systems read birth lists, scale tickets, settlements and closeouts onto the right animals by EID, and fill the reports you already use in the layout you already use.

  • Imports matched by EID, with lineage back to the source line.
  • Reconciliation at every handoff, with a reason required for any difference.
  • Scheduled reports and alerts by email, at the time your crew needs them.
  • Exports in the same columns as the spreadsheet they replace.

04Data you can prove

Records that hold up to a buyer, a vet or an auditor.

Lineage
Every figure on a report links back to the records it came from, and every record says how it is known.
Append-only history
Changes are added, never overwritten. Device time and server time are both kept, so actions taken offline stay honest.
Permissions at the data layer
Who may see what is enforced in the database itself, not only in the screens.
Exports anytime
Your data leaves in open formats whenever you ask. A standard export is always free.

Fig. 04.1 · How a Mule system is put together

IN THE FIELDField appsOFFLINE QUEUE · TIMESTAMPSEID readersBLUETOOTH · WAND · PANELPaperwork importsBIRTH LISTS · TICKETS · CSVTHE RECORDPermission layerROLES ENFORCED IN THE DATABASEOne record per animalPROVENANCE · APPEND-ONLY HISTORYEU OR US HOSTING · DAILY BACKUPSOUTPortalsBUYERS · YARDS · VETSReports, dashboardsNIGHTLY REPLICA · LINEAGEExportsOPEN FORMATS · ANYTIMESYNCMATCH BY EIDINTEGRATIONSUSDA MARKET REPORTS IN · ACCOUNTING EXPORTS OUT · HERD SOFTWARE, SANITEL, RVO I&R PLANNED

Field devices work offline and sync to one record store. Permissions are enforced at the data layer; reports read from a nightly replica; exports leave in open formats.

Schematic · not to scale

05How we build

Six steps, visible in your portal.

Each step has an approval, and every approval is recorded in the Mule Portal with the progress bar and a written update.

  1. 01

    Discovery

    We walk the operation with you, on site or by video, and map where each animal's data starts, moves and gets lost.

  2. 02

    Design

    Screens, records and reports drawn around the way your crew already works, reviewed with the people who will use them.

  3. 03

    Build

    Short cycles with working software you can try. Every milestone shows in your portal with a progress bar and a written update.

  4. 04

    QA on a real farm

    Tested in the alley, the chute and the cab, with gloves on and the signal off, before anything goes live.

  5. 05

    Launch

    Training for the crew, a printed field card where it helps, and a planned switch from paper or spreadsheets.

  6. 06

    Operate

    Hosting, monitoring, backups and small fixes under a monthly retainer, with usage and cost visible in the portal.

Data and trustIntegrations

FAQ

Questions

Do you sell an off-the-shelf product?

No. Every system is built around your operation. Parts are reused across projects, which keeps builds faster, but nothing is forced on you.

Does it work without signal?

Yes. Field apps save every action on the device first and sync when they are back in range, with device time and server time both kept.

Who owns the code and the data?

You do. On completion and full payment the project is yours, and your data can be exported in open formats at any time.

Can you work with the software we already use?

Usually. Tell us what you use. Accounting exports and USDA market data work today; herd software and registry connections are planned per project.

Where is the data hosted?

In the EU or the US, chosen per project, under the rules of the country the animals are in.

Start a project

Tell us what happens to your animals today.

Tell us about your operation and what you want to fix. We reply within 1 business day.

Start a project

Or write directly

juastins@icloud.com

Replies within 1 business day. No phone line; every conversation is in writing and in your portal.