I’m very new to FarmOS and still exploring its capabilities.
Is it possible for one self-hosted instance to serve two or more farms, such that users from one farm don’t see anything about the other farms?
If not, is that a Drupal limitation or a FarmOS limitation?
Hi @gmagnusson welcome to the forum!
Drupal has a concept of “multisite” installations, where a single codebase can serve multiple websites/domains, each with their own database. More info here: Multisite Drupal | Drupal | Drupal Wiki guide on Drupal.org
There has also been some discussion around a “multi-farm” farmOS instance, where multiple farms can have records in a single instance (under a single domain and database). But no development there yet. Here is the feature request: Multiple farms in one farmOS [#2940211] | Drupal.org
Hope that answers your question!
Thank you. Thats the conclusions I was slowly arriving at.
It looks like I can’t do what I was originally going for, but I think putting each farm on a separate sub-domain and with a separate database will work. I can work with that.
If you need help with hosting, feel free to DM me @gmagnusson. Farmier.com is set up to provide “group hosting” options as well. Shameless plug 
Since the beginning of Y2025, there has been some progress on this issue.
[pcambra] has started Farm multitenant project.based on Group module developed for Drupal.
pcambra has also started farmOS module developement for forest management:
co-maintained with “the boss” @mstenta you might also check out.
farmOS Forest.
My personal project (on of several, still in porogress) was to use Kubernetes/NGINX framework to cluster multiple farmOS instances (with or without Docker), on bare or non-bare metal cluster and shut the instance down when user signs off, and restart it when user logges in, so instance lives and occupies processor core only when needed, leaving cores for other instances to other users (other farmOS instances). Certain property (e.g. leased land from government could be leased to another farmer, or private land sold to another farmer, but could maintenain historical records in the farmOS, if import-export of all features of such plot per plot could be utilised). With central multi-tenancy this feature and managing multiple farms where plots also shift from “user to user”, e.g. for crop rotation…could be easier
About my projects I hope I will find time for proper posts soon.
Greetings
SF