The
Technology Landscape.

01Why this page exists.

A grower looking for monitoring and control technology walks into a room full of options that do not announce what they are. A sixty-thousand-dollar commercial control system and a twenty-dollar BLE temperature sensor look identical on a sales sheet — each claims to help you monitor your greenhouse. They are not the same thing. They do not belong to the same category. They do not fit the same operation.

The sales pitch will not tell you this. The vendor's job is to sell what the vendor sells. Every vendor believes their product is the right answer. Some of them are right, for some growers. None of them are right for every grower. The grower who cannot tell the shapes apart ends up buying something that does not fit, or buying nothing because the confusion is too much, or paying for something they cannot afford because the cheaper option looked untrustworthy.

The grower who understands the landscape picks what fits. That grower evaluates options not by which brochure looks most professional, but by which shape solves their problem at a cost they can afford, with a level of ownership and maintenance they can sustain. Sometimes the answer is a commercial system. Sometimes it is a subscription product. Sometimes it is a handful of sensors and a small computer. Knowing which is which is the knowledge this page shares.

02The four shapes of agricultural technology.

Agricultural monitoring and control technology divides into four broad categories. The lines between them are not perfectly clean — a few products straddle boundaries — but the four shapes capture ninety percent of what a grower will encounter. Each has its own economic logic, its own customer base, its own strengths, and its own limits.

### 1. Legacy commercial control systems.

These are the established brands that have served commercial horticulture for decades. The technology is mature, the hardware is industrial-grade, and the service networks are professional. A grower who installs one of these systems gets hardware designed to last fifteen or twenty years, climate algorithms refined over thousands of deployments, redundant sensors, uninterruptible power considerations, and a technician who drives out when something breaks.

The business model is proprietary. The hardware is the vendor's. The software is the vendor's. The data typically lives on the vendor's cloud or on a local server the vendor installed. Service contracts are annual. When a component fails, the grower calls the vendor. When the grower wants to change how the system behaves, the grower calls the vendor. When the vendor releases a software update, it runs on the vendor's schedule.

This shape is appropriate for operations where scale justifies the investment. A hundred-thousand-square-foot tomato operation cannot afford for the climate to go wrong, cannot afford to have untrained staff troubleshooting hardware, and cannot afford the liability of a system it does not understand. The commercial vendor takes that liability off the grower's plate. Downtime costs thousands of dollars an hour in an operation that size. A fifty-thousand-dollar system that prevents one bad night pays for itself.

This shape is inappropriate for smaller operations, for growers who want to own their systems end to end, for growers who cannot absorb annual service contracts, and for growers whose operations are not standardized enough to fit the vendor's model. A grower with two high tunnels and a passion greenhouse cannot buy this shape of technology — or if they do, they discover quickly that the tool does not fit the job.

Who this shape fits:

Large commercial growers, industrial-scale CEA operations, operations with standardized infrastructure, operations where downtime cost exceeds the cost of the system, and operations with staff trained to work with commercial vendors.

What the grower gives up:

Ownership of the system. Direct access to the data. The ability to modify behavior without the vendor. Continued operation if the vendor changes pricing, gets acquired, or discontinues the product line. The savings that come from owning instead of subscribing.

### 2. IoT subscription products.

The newer shape. A wave of companies has entered agriculture over the past ten years selling sensor products with monthly or annual subscriptions. The hardware is often clever, the apps are usually slick, and the onboarding is designed to take minutes rather than days. A grower buys a few sensors, creates an account, pairs them with an app, and gets readings on their phone within an hour. Many of these products work well for what they promise.

The business model is recurring revenue. The sensors themselves are often sold near cost, sometimes at a loss, because the money is in the subscription. The grower pays monthly or annually for access to the app, the cloud storage, the alerts, and any analytics the company offers. If the grower stops paying, the sensors stop being useful. The hardware is sometimes technically capable of being used without the service, but doing so usually requires reverse-engineering that is not supported.

This shape is appropriate for growers who want something they can buy, install, and stop thinking about. It is appropriate for growers who are comfortable with recurring costs, who do not need to customize or extend the system, and who accept that the data lives on someone else's servers. Many small and mid-scale growers use these products and get real value from them. They trade ownership for simplicity, and the trade makes sense in their context.

This shape is inappropriate for growers who want to own their systems, growers for whom the subscription math does not work over time (ten years of monthly fees often exceeds the cost of a comparable owned system by an order of magnitude), growers whose operations need customization the product cannot accommodate, growers who want their data to live locally, and growers who want a system that keeps working if the company is acquired, pivots, or closes. History tells us some of the companies selling these products today will not exist in five years. A grower whose monitoring depends on those products loses their monitoring when that happens.

Who this shape fits:

Growers who want a turnkey solution, growers who value simplicity over ownership, growers with predictable operations that do not require customization, and growers who prefer monthly costs over capital expense.

What the grower gives up:

Ownership. Data that lives under their control. Continued operation independent of the vendor. Long-term cost predictability (subscriptions tend to go up, not down). The ability to extend or customize the system beyond what the vendor offers.

### 3. Do-it-yourself and hobbyist systems.

The third shape is not a product category at all — it is a community. An idea and an Arduino board. A grower with some knowledge, time, curiosity, and patience can assemble a monitoring system for a few hundred dollars in components, learn enormous amounts in the process, and build something that does exactly what they want.

Who this shape fits:

Students, researchers, makers, hobbyists, growers with technical backgrounds, and growers who treat their systems as part of what they enjoy rather than as infrastructure they need to work.

What the grower gives up:

Time. A lot of it, up front and ongoing. Certainty that the system will work when they need it. Support when something breaks at midnight. The ability to hand the system off to someone else without a long explanation.

### 4. The collective approach.

The shape this site is built around. It draws on the strengths of the other three and avoids their main weaknesses. The hardware is commodity-priced, like the DIY shape, so the cost stays accessible. The software is mature and actively maintained by a large community — Home Assistant, running on a small computer, has been used in millions of homes and businesses worldwide, the project is over 12 years old — so the grower gets production-grade reliability without paying for it. The configurations and recipes are shared through the collective, so the grower does not have to reinvent what other growers have already figured out. The data lives on the grower's equipment, under their control, in open formats that will outlive any one company.

The economics are straightforward. Hardware costs are one-time, in the range of one hundred to five hundred US dollars for most small and mid-scale operations, depending on how many sensors are needed. Software costs are zero. Ongoing costs are the electricity to run a small computer — typically less than five dollars a month — and occasional replacement components as sensors wear out or get damaged. There are no subscriptions. There is no vendor that can raise prices or shut off the service. If the grower stops maintaining the system, it keeps working until a component physically fails.

The knowledge is not owned by any company. Home Assistant is open-source software maintained by a community of thousands of developers. The sensor hardware uses standard protocols. The configurations that make everything work for agricultural purposes are shared through the OpenAgTech collective and other open communities. When a grower builds a system using the collective approach, they can hand that system to another grower in ten years, or teach their kid how to maintain it, or walk a neighbor through building one of their own. The knowledge transfers because nothing is proprietary.

This shape is appropriate for small and mid-scale growers who want ownership without the learning curve of pure DIY, for growers who want production-grade reliability at commodity prices, for growers whose operations need some customization, for growers who want their data to live locally, for growers who refuse to pay monthly subscriptions for something that should be owned, and for growers who are part of or want to be part of a community that shares knowledge freely. It is the shape that fits most of the growers the first three shapes do not serve well.

This shape is inappropriate for growers who want a vendor to call when something breaks (though collective members and independent consultants can help), for growers whose operations are so large and critical that a commercial service contract is genuinely necessary, and for growers who have no interest in understanding how their own technology works.

Who this shape fits:

Small and mid-scale growers, cooperative operations, educational institutions, extension programs, research operations that need reproducibility and transparency, growers in regions where commercial vendors do not operate, and growers for whom ownership of their tools is a matter of principle as well as economics.

What the grower gets:

Ownership. Data that lives on their own equipment. A system that keeps working regardless of what any company does. Long-term cost predictability (a component might fail every five or ten years; otherwise costs stay flat). The ability to extend, customize, and adapt the system as their operation changes. A knowledge base that belongs to them. The right to own, maintain and repair what is yours.

03Comparing the shapes.

A comparison across the four shapes, in plain terms:

Who owns the hardware.

Legacy commercial: vendor-specific hardware, grower owns it but usually cannot service it without vendor support. IoT subscription: grower owns the hardware but it is often useless without the subscription. DIY: grower owns everything, sources parts directly. Collective: grower owns everything, sources parts directly, configurations shared openly.

Who owns the data.

Legacy commercial: typically the vendor, with access provided through their interface. IoT subscription: typically the vendor's cloud, with grower access through the app. DIY: grower, on their own equipment. Collective: grower, on their own equipment, in open formats.

What happens if the company disappears.

Legacy commercial: service ends; hardware may continue to function in degraded mode; replacement parts may become unavailable. IoT subscription: hardware often stops working entirely or loses most features. DIY: nothing changes; grower owns it all. Collective: nothing changes; grower owns it all; community continues.

Upfront cost for a small operation.

Legacy commercial: typically ten thousand to one hundred thousand US dollars depending on scale. IoT subscription: low upfront cost, typically fifty to five hundred dollars in hardware. DIY: one hundred to five hundred dollars in parts. Collective: one hundred to five hundred dollars in parts plus a small computer.

Ongoing cost per year.

Legacy commercial: typically two to ten thousand US dollars in service contracts. IoT subscription: typically one hundred to six hundred dollars depending on features and number of devices. DIY: essentially zero except for replacement parts. Collective: essentially zero except for replacement parts and electricity.

Time to first working system.

Legacy commercial: weeks to months, with professional installation. IoT subscription: hours to a day. DIY: days to weeks, depending on skills and ambition. Collective: hours to days, using shared configurations.

Customization.

Legacy commercial: limited to what the vendor offers; custom work requires vendor engineering. IoT subscription: limited to what the app offers; little or no grower customization. DIY: unlimited; grower can do anything. Collective: unlimited; grower can do anything, and can start from configurations others have already built.

Reliability.

Legacy commercial: very high when installed and serviced properly. IoT subscription: generally good, depends on the company. DIY: depends entirely on the grower. Collective: high, because the underlying software (Home Assistant and its ecosystem) is used in millions of deployments and matures continuously.

04Where the collective fits.

The collective exists for the growers; the first three shapes do not serve well. A commercial system is too expensive. A subscription product does not give enough ownership or control. Pure DIY is not possible for someone whose full-time job is already growing food.

Most small and mid-scale growers fall into that gap. A grower with one greenhouse, three high tunnels, a few acres of row crops, a container farm, or a small commercial operation does not fit the economics of commercial control systems and does not want to spend their evenings troubleshooting embedded code. A subscription product gets them started but costs them more every year than the system is worth. The collective fits precisely there. Production-grade technology, commodity prices, shared knowledge, owned by the grower.

The collective is not against the other shapes. A grower who needs a commercial control system and can afford one should buy one — those systems exist because they fit a real need. A grower who wants a subscription product and gets value from it is making a reasonable choice. A grower who enjoys DIY should keep building. The collective is for the growers for whom none of those answers are the right answer. That is a lot of growers — globally, it is most of them.

The collective does not compete. It creates. It puts together pieces that were already available but required expertise to combine, documents the combinations, shares what works, and teaches other growers how to do the same. The hardware manufacturers make money selling components. The software communities get contributors and users. Growers get systems that fit. Nobody loses when the collective succeeds — including the companies in the other three shapes, because the collective serves growers those companies were not going to reach anyway.

05How to choose your shape.

Before spending money, a grower benefits from answering a few questions honestly.

How critical is the monitoring?

If the difference between working and not working is a six-figure crop, the answer probably leans toward commercial. If the difference is a meaningful but recoverable loss, the collective or subscription shape fits. If the difference is convenience, DIY or collective works.

What is the total budget over ten years?

Capital cost plus ten years of ongoing costs. A subscription product that costs two hundred dollars upfront and thirty dollars a month costs thirty-eight hundred dollars over ten years. The collective approach costs three hundred dollars upfront and sixty dollars over ten years in electricity. The commercial system costs thirty thousand dollars upfront and sixty thousand dollars in service. Each makes sense for different operations.

How much ownership matters?

Some growers do not care whether the vendor owns the data, as long as the app works. Other growers care intensely about owning every byte of information their operation produces. The answer to this question alone often eliminates two of the four shapes.

What happens when the system fails?

If the grower can troubleshoot it themselves, the collective or DIY shape works. If they need to call someone, commercial or subscription shapes work. The collective has a middle ground — independent members and consultants can help, but the grower typically needs some technical engagement to operate a collective system.

How customized does the operation need to be?

A standardized greenhouse growing a single crop fits the assumptions commercial and subscription products make. A diversified operation with a mix of crops, structures, and workflows often does not. The more unusual the operation, the more the collective or DIY shapes make sense.

A grower who answers those five questions honestly usually discovers which shape fits. Sometimes the answer is clear — a one-greenhouse herb operation should not buy a commercial system, and a twenty-acre CEA tomato operation should not build its climate control from ESP32 boards on a Saturday afternoon. Sometimes the answer is mixed — the grower wants commercial-grade reliability in one area and collective-grade ownership in another. That is fine. Real operations often use combinations. A grower might use a commercial system for climate in the main production houses and a collective-built system to monitor the propagation area, the curing room, and the well pump. The four shapes are not exclusive. They are tools.

06A note on the vendors we have not named.

This page describes four shapes of technology without naming specific companies. That is deliberate. The point is to give growers a framework they can apply to any product they encounter, not to praise or criticize particular brands.

The commercial control system space includes companies that have served growers excellently for decades. The IoT subscription space includes companies doing genuinely useful work at reasonable prices. The DIY space includes thousands of makers whose contributions have raised the whole field. Every one of them has a place. The grower evaluating an option should apply the framework — how does this product fit my operation, my budget, my need for ownership, my capacity for self-service — and decide based on the answer, not based on marketing.

The collective approach is not a product. It is a way of putting together components that already exist. When a grower reads a review of a commercial control system or a subscription IoT product, the review is evaluating a specific vendor. When a grower reads about the collective approach, they are reading about a pattern. The pattern can be executed with different components, at different scales, by different people, in different places. That is its strength.

\[FAQ — JSON-LD to be generated from these Q&A pairs.\]