KeeperOS
A season runs from pairing to sale in one record, with the genetics maths and the incubation log attached to the animals you already track.
A breeding season is a long chain of small commitments, and it breaks at the joins. You pair two animals in February and the question in June is what you actually put together, at what weight, on which dates. You candle a clutch and the number matters only against the number you expected. You hatch nine and the interesting question is whether the ratio told you something about a het you were not sure of.
Most collection apps handle breeding as a second module bolted beside the care one, so the animal you have been logging feedings against for two years arrives in the breeding section as a fresh name with no history. That break is where the useful comparisons die: weight against last season, refusal patterns before a pairing, which female took which male and what came of it.
KeeperOS keeps the chain in one place. Pairings, clutches, incubation and sales attach to the same animals the care log already knows, so nothing restarts and every question you ask in June can reach back to February.
Projects hold the intent. A project groups the pairings you mean to make this season, and the genetics engine gives you the odds before you commit an animal to a tub — the offspring distribution for that pairing, with each outcome's probability, rather than a spreadsheet of Punnett squares you maintain by hand.
Clutches carry the season's facts: laid date, egg count, and a candle status that moves from uncandled through candled to fertile or infertile. The incubator dashboard tracks temperature readings over time against each clutch rather than as a single number you typed once, which is what makes a bad week visible after the fact instead of merely suspected.
When it hatches, the scoring is the point. The engine compares what actually came out against the distribution it predicted, so an outcome that should have been rare and was not is flagged rather than admired. That is also how proven-het discovery works: a het you were carrying as unconfirmed becomes confirmed by the offspring you produced, derived from real results instead of asserted in a notes field.
Hatchlings become animals in the same collection, with the clutch as their origin, so the care log starts on day one and their growth curve sits alongside their parents'. Sales records and animal transfers finish the chain — a transfer moves the record into the buyer's own account with a permanent origin ID and a frozen snapshot, and you can print a certificate or a batch of labels for the ones going out the door.
The genetics depth is Western Hognose specifically: 319 curated morph records with 185 slug aliases, so the name a seller used and the name you use resolve to the same morph. Other species get the full pairing, clutch and incubation workflow without the morph engine.
If the animals you are pairing are snakes, the snake breeder page covers the hognose genetics depth and the selling end — MorphMarket export, transfers, certificates — rather than the season mechanics described here.
The sharpest alternative for a breeder-first workflow is ReptiDex, which ships multi-user roles, five-generation pedigrees and a native iOS app that we do not have; our comparison with them leads with those. For ball pythons specifically, THE RACK is built for that species alone and our genetics engine is not.
Actively built: 39 dated updates since June 2026, most recently See what changed, right in the app on Sep 9. See everything that has shipped →
The comparisons. A notebook holds what happened; software is worth paying for when it can put what happened next to what you expected — this clutch against your predicted distribution, this female's weight against last season, this het against the offspring that would confirm it. Recording is the easy half.
No. Breeding is a tier, not a mode. The base product is husbandry, and pairings, clutches and incubation attach to those same animals when you are ready. A keeper who never breeds never sees the module, and one who starts does not migrate anything.
You pick the two animals and it resolves their genotypes against the curated morph catalogue, then returns the offspring distribution with a probability against each outcome. Because it reads the animals' own recorded genetics rather than a form you fill in each time, the odds stay correct as you refine what you know about a het.
A het you are carrying as suspected can be confirmed by what you produce. When a clutch hatches an outcome only possible if a parent carried the gene, the engine surfaces that rather than leaving you to notice it. It is the one place breeding records pay you back for having been careful.
Yes, as readings over time against the clutch, not a single set figure. The incubator dashboard shows the series, which is what lets you connect a slow hatch to the week the room got cold.
A transfer moves the record into the buyer's own KeeperOS account under their login, keeping a permanent origin ID and a frozen snapshot of the history at handover, with per-field toggles for what you share. You can print a certificate for it, or a batch of labels for a table at a show.
The demo needs no signup. The free tier needs no card, and we don't sell your data.
