Our mission is to stop every piece of agricultural technology from creating its own version of the farm.
The information needed to run the property was spread across notebooks, spreadsheets, text messages, email, machinery portals, filing systems and individual memory. Each method had a purpose, but together they created more places to check, more information to enter twice and more uncertainty about which record was current.
The weakness became most obvious when we were away from the farm.
A machine would fail and somebody would need to order a part. We knew which machine it was, but not necessarily the model number, serial number, fitting size, filter type or exact component required. The useful detail might be on a plate attached to the machine, in an old invoice, in a photograph on somebody’s phone or in the memory of the person who repaired it last time.
The problem was rarely a complete absence of information. The problem was that the information was somewhere else.
Repairs created the same difficulty. A pipe might have an imperial fitting at one end and a metric fitting at the other because of work completed years earlier. Somebody on the farm might know why. There might even be a receipt or photograph. But there was no dependable repair history attached to that particular section of pipe.
The next failure therefore began with another investigation.
Adding technology did not always make the farm simpler. Quite often, it added another login, another database and another version of the operation.
That experience led to FarmCore.
.
Agriculture has no shortage of capable farmers, developers, researchers, universities and technology companies. The problem is that too much useful work is still done in isolation.
FarmCore is built around a shared foundation so each participant can contribute without recreating the same basic systems first.
Collaboration should make the next product easier to build, the next integration easier to complete and the next farm easier to support.
The aim is not to collect partners for appearance. It is to combine practical agricultural knowledge with technical capability in a way that produces working tools.
Farm information can be operationally, commercially and personally sensitive.
FarmCore should make ownership, access, consent and permissions clear. Developers and applications should receive only the access required and authorised by the farm.
Trust is not a policy page added after the product is built. It is part of the infrastructure.
Technology is useful only when it reduces the effort required to run the operation.
FarmCore is built around real agricultural work, not around what looks impressive in a product demonstration. Every feature should make information easier to find, work easier to coordinate or records easier to retain.
If the system creates more administration than it removes, it has failed.
Too much agricultural innovation is slowed by the need to rebuild the same foundations for every new product.
FarmCore is intended to reduce that delay. By providing the core platform, workflows and infrastructure already in place, developers can move more quickly from an idea to something farms can actually use.
The objective is not innovation for its own sake. It is to make useful agricultural technology faster to build, easier to test and simpler to deploy.
The idea is simple: agricultural technology should reduce the work required to operate a farm. It should not create more software for the farm to manage.
A farm asset register can appear unnecessary when the operation owns one tractor, one generator and a few tools.
Then the operation grows.
Before long, there may be five chainsaws, four generators, several pumps, three farm vehicles, multiple implements, irrigation equipment, trailers and tools spread across sheds, vehicles and different parts of the property.
At that point, apparently simple questions become difficult.
Which chainsaw was serviced last? What fuel mixture does it use? Which generator has the electrical fault? Where was the replacement belt ordered from? Does the vehicle need servicing by date, hours or kilometres? Which filter fits the pump? Who keeps track of the spare parts?
The answer is often a combination of memory, handwritten labels, receipts, messages and whichever person dealt with the asset most recently.
This may work until that person is away, leaves the business or simply cannot remember.
FarmCore is intended to give each asset a usable operating history. Identification details, photographs, manuals, faults, repair notes, service intervals, parts and completed work can remain connected to the machine or piece of infrastructure they describe.
The value is not merely knowing that the farm owns four generators. It is knowing which generator is where, what condition it is in and what must happen next.
The visible problem was scattered information. The deeper problem was fragmentation.
Most agricultural software is built to solve a particular problem. One platform manages machinery. Another records chemical applications. Another handles livestock, safety, irrigation, contractors or compliance.
Many of these products are useful. The difficulty is that each may arrive with its own users, permissions, maps, records, documents and workflows.
The farm is then represented repeatedly across several disconnected systems.
This is particularly difficult for mixed and multi-commodity farms.
A cattle operation may select livestock software as its principal system. That platform becomes the place where the business keeps animal records, staff information, property details and some operating data.
If the same farm also grows crops, it may need a separate cropping platform. The cropping system may have its own paddock maps, users, records and workflows. It may not communicate with the cattle platform.
Add irrigation, machinery maintenance, workplace health and safety, biosecurity or contractor management, and the farm can end up with several systems, each containing part of the same operation.
The farm must effectively nominate one commodity-specific product as the master system, even though no single commodity describes the whole business.
That is a structural problem.
A farm is not merely a cattle enterprise with cropping attached, or a cropping enterprise with livestock attached. It is one operating business containing shared people, places, machinery, infrastructure, documents, tasks and responsibilities.
FarmCore is being built to represent that common operating layer first.
Commodity-specific and specialist applications can then extend the farm without each creating a separate version of it.
FarmCore brings the common elements of farm operations into one operating environment.
These elements include properties, paddocks, locations, people, roles, contractors, machinery, infrastructure, tasks, records, photographs and documents.
A task can remain connected to the paddock, person or machine it relates to. A maintenance record can stay with the asset rather than disappearing into a spreadsheet. Instructions, photographs and evidence can be captured while the work is being completed instead of reconstructed later.
A repair to an irrigation line can retain the location, photographs, fittings used, supplier, responsible person and work completed. The next person dealing with that line does not need to rediscover that one end uses an imperial fitting and the other uses metric.
A tractor record can retain its serial number, service history, filter details, manuals and previous faults. If a part must be ordered while the owner is away from the farm, the information should already be available.
This creates a more useful operational history of the farm.
FarmCore is also intended to provide the foundation on which specialist agricultural applications can be built. A livestock application, cropping tool, biosecurity system or irrigation application can use the existing FarmCore structure rather than creating another separate version of the property.
The aim is not to replace every useful agricultural product. It is to give those products a common environment in which to operate.
Software that performs well in an office can fail quickly in a paddock, workshop or machinery cab.
Farm work is seasonal, mobile and frequently interrupted. Connectivity varies. Contractors and employees need different levels of access. Instructions may need to be understood quickly, with gloves on, in poor weather or beside operating machinery.
A minor inconvenience in an office can become a serious reason not to use a system in the field.
FarmCore is therefore being shaped around practical agricultural conditions. The platform is intended to favour clear navigation, fast data entry, useful defaults, mobile operation and records created through normal work.
This matters because farms do not usually fail to keep information through neglect. They fail because the method of recording it requires a separate administrative effort after the practical work has already been completed.
A repair record is more likely to be retained when it forms part of closing the repair task. A service history is more reliable when it updates as the service is completed. A photograph is more useful when it remains attached to the asset, location or fault it documents.
The measure of useful farm technology is not how many functions it contains. It is whether people will use it when the work is actually being done.
FarmCore begins with task management and asset management because nearly every agricultural operation depends on both.
Farm task management provides a practical way to create work, assign responsibility, attach instructions and connect a job to the relevant property, paddock, location or asset.
Agricultural asset management provides a structure for machinery, vehicles, implements, pumps, irrigation infrastructure, sheds, fencing and other operating assets. Maintenance records, faults, manuals, photographs and service histories can remain attached to the equipment they describe.
These initial functions address ordinary but consequential questions:
What needs doing?
Who is responsible?
What information do they need?
Which asset or location does the work relate to?
What was done last time?
Which part was used?
When is the next service due?
Where is the evidence that the work was completed?
These are not glamorous technology problems. They are the problems that determine whether the operation runs smoothly.
Task and asset management also establish the common operating structure required for later applications, integrations and artificial intelligence capabilities.
FarmCore will expand through specialist applications that farms can add according to their enterprise and requirements. A mixed farm should not be forced to choose between a cattle system and a cropping system as the master record of the whole operation.
The common farm should come first. Commodity-specific applications should connect to it.
Many agricultural technology teams begin with a genuine industry problem but must first build the systems surrounding it.
They need user accounts, authentication, permissions, farm profiles, maps, records, notifications, document storage and reporting before their specialist application can become useful.
That duplication consumes development effort and produces more disconnected products for farms.
FarmCore is intended to provide this underlying infrastructure.
Developers can concentrate on the agricultural function that gives their application value, rather than repeatedly rebuilding the basic operating structure around it. A cattle application can focus on livestock. A cropping application can focus on agronomy and paddock operations. An irrigation application can focus on water.
Each can work with the same underlying property, people, assets, permissions and operating records where the farm has authorised that connection.
This is especially important for multi-commodity operations. The farm should not have to maintain several conflicting versions of the same paddock, employee, vehicle or piece of infrastructure simply because different applications serve different enterprises.
Farmers must retain control over their operational information. Access, permissions, portability and consent are not secondary administrative details. They are part of the product.
FarmCore is being developed by Havoc Ventures.
The development program combines practical agricultural operating problems with software, data and artificial intelligence capability. FarmCore is also being developed through supervised student-development programs involving Queensland University of Technology, Griffith University and the University of Sydney.
These collaborations provide a pathway for students, researchers and technical teams to work on defined agricultural problems with practical commercial application.
FarmCore remains a commercially directed Havoc Ventures product. University participation should not be interpreted as ownership, formal endorsement or funding unless a specific arrangement states otherwise.
Artificial intelligence is often presented as though it can solve agricultural administration by itself.
In practice, artificial intelligence becomes useful when it can work with reliable information about a particular farm.
FarmCore is being designed to provide that context.
Over time, artificial intelligence may help users locate records, summarise maintenance histories, identify overdue work, prepare task lists, extract information from documents and answer questions about the farm’s own operating history.
A user might ask:
Which generators are due for servicing?
What parts were used in the last irrigation repair?
Find the model and serial number for the pump at the northern dam.
Which farm vehicles have unresolved faults?
What work was completed on this paddock last season?
Which assets do not have a current service record?
Those questions become easier to answer when the information is structured around the actual farm.
The purpose of artificial intelligence is not to replace farmers, agronomists, veterinarians or other qualified professionals. Its purpose is to reduce administration and make existing farm information easier to use.
An intelligent answer is only as dependable as the operating information beneath it.
FarmCore is being developed in Australia and initially shaped around Australian agricultural conditions.
That includes large and dispersed properties, mixed enterprises, seasonal labour, contractors, machinery-intensive operations, variable connectivity and limited time for administration.
The platform is intended to support different agricultural sectors and operating models as it develops.
Its initial focus is local and practical. Its longer-term opportunity is broader.
We are not trying to persuade farms to adopt technology for its own sake.
The objective is more specific.
Work should be easier to assign and verify. Records should remain connected to the people, places and assets they describe. Operational knowledge should not disappear when a staff member leaves. The details needed to order a part should still be available when the person who knows the machine is away.
A repair completed today should make the next repair easier, rather than leaving the next person to solve the same mystery again.
A multi-commodity farm should not need to choose one specialist platform to act as an imperfect master record for the entire business.
Useful applications should be able to connect without forcing the farm to rebuild itself inside another system.
FarmCore should make it clearer what needs doing, what has been completed and where the relevant information belongs.
For developers, it should reduce the amount of basic infrastructure that must be recreated before a useful agricultural product can be built.
For farms, it should mean that new technology extends the operation rather than fragmenting it further.
Every proposed function is tested against one practical question:
Does this reduce the work required to operate the farm, or does it merely create more software to manage?
That question matters because the apparent product is technology, but the real value is usually less chasing, less repetition and less uncertainty.
FarmCore is being built to provide one dependable operating foundation for agriculture.
One system for running the farm.
The infrastructure that allows the next thousand agricultural technologies to work.
FarmCore remains under active development.
We are interested in hearing from farmers, farm managers, agricultural technology developers, universities, researchers, industry organisations and strategic partners who have a practical use case or contribution to make.
Run your farm on FarmCore
Explore how FarmCore is being developed for farm operations.
Build on FarmCore
Explore the platform for agricultural technology developers and partners.
The strongest new material is the mixed-farm problem. It explains why FarmCore needs to exist beneath livestock, cropping and other specialist systems, rather than competing as another commodity-specific application.