Industries
Indoor & vertical farms
Several crop recipes, one ops backbone. Batches, inputs, and sales tied together.
Indoor farms juggle recipes. Khet treats each batch as its own run: nutrients, climate tasks, yield by rack. You still get one set of books when those batches become an order.
On this kind of farm
- 01Recipe-based batch production
- 02Nutrient and environmental logging
- 03Yield per rack or zone analytics
- 04CEA compliance and audit exports
In practice
Recipes, racks, and one set of books
Each batch is a run. Yield is per rack or zone. Sales still sees one product they can ship.
- 01
Start a batch from a recipe
Crop, zone, and the nutrient plan. The batch has an identity before the first harvest.
- 02
Log the environment work
Climate checks and nutrient tasks are jobs on that zone. Missed checks stay open.
- 03
Harvest by rack
Weight per zone, not one number for the whole room. You can see which recipe is actually paying.
- 04
Sell the finished lots
Orders pull from those harvest lots. Finance sees the cost of the batch, not a blended guess.
Details
Controlled environment, ordinary records
Batch production
Hydroponic, aeroponic, or aquaponic runs with their own recipe and dates.
Zone yield
Know which rack or room produced. A weak zone is visible before you replant the same way.
Inputs per batch
Nutrients and labor land on the batch that used them.
Audit exports
When a buyer wants the production record, you export the batch. You do not assemble it from sensor screenshots.
Questions
What people ask before they book
We have several recipes in one room. Does that fit?
Yes. Batches stay separate even when they share a room. Yield and cost do not have to be averaged together.
Does Khet replace our climate computer?
No. Khet keeps the tasks and the harvest record. The controller can keep running the room.
Can indoor production share finance with a field farm?
Yes, on one tenant. Zones and field blocks report separately and can roll up.