Supported species

Layers today. The foundation is not layer-shaped.

It is easy to build a poultry product and then discover that adding swine means rewriting identity, farms, imports, reporting and permissions. We built the shared foundation first and made the species-specific parts configuration.

Layers

Available

Phase 1. Weekly production, environment, genetic standards, peer benchmarking, feed analysis and reporting.

Broilers

Planned

The hierarchy, imports, calculation engine and reporting are already shared. Species configuration and screens follow.

Turkeys

Planned

Same foundation, different metric set and standards.

Swine

Planned

Requires its own lifecycle vocabulary; the tenancy, access and audit layers do not change.

Ruminants

Planned

Longer cycles and different environmental factors, on the same record structure.

Future diagnostics

Planned

The diagnostic framework is species-agnostic by design — a new module is configuration plus a result contract.

What “species-aware” actually means

The honest version

Some vendors say “multi-species” and mean a dropdown. Here is precisely what is shared and what still needs building.

Shared, and already built

Customer, farm, barn, flock and weekly-record structure
Identity, invitations, roles and access scopes
Import pipeline, mapping library and validation
The calculation engine and unit conversion
Standards versioning and publication
Benchmark cohorts and privacy rules
Alerts, reports, notifications and the audit trail

Still product work, per species

The metric set, with units, precision and plausibility ranges
Which direction is better for each metric
Genetic and production standards, and the aliases that map to them
Upload templates and legacy mappings for that species
Alert rules and thresholds, approved by a nutritionist
Dashboards where the workflow genuinely differs