Companions - Plant Relationships Interpreter
Continue Using Companions
$49 USD — One-time purchase. Lifetime access.
No subscription.
Includes the Companions Web Utility and a ChatGPT-compatible version with future updates.
i. purpose
Shelf Life determines what to do with any food based on its current state — returning the next practical action, storage path, preservation options, use-up ideas, and safety signals across any food condition, quantity problem, or storage question.
ii. examples
Shows how companion planting questions are resolved — the association, spatial logic, and follow-up paths.
details
what plants grow well with tomatoes
a: Basil, alliums, borage, marigolds, and flowering umbellifers are the strongest companions — aromatic confusion, beneficial insect habitat, and pollinator draw without competing for the tomato root zone.
what should I not plant near fennel
a: Most vegetables — tomatoes, legumes, brassicas — can show reduced growth near fennel. Treat it as a standalone border or insectary plant at distance, not interplanted inside a crop bed.
how does a Three Sisters guild work
a: Corn provides the pole, beans fix nitrogen, squash sprawls as living mulch. The nitrogen payoff comes after residues break down — not during the season.
what is a trap crop and how do I use one
a: A sacrifice plant grown to concentrate pest pressure away from your main crop. Pick the target pest first, place at the bed perimeter, and destroy or treat once pests arrive — or it becomes a pest nursery.
what plants fix nitrogen for neighboring crops
a: Legume root nodules fix nitrogen — but neighbors get most of the benefit after the legume is cut or its roots decompose, not in real time. Beans anchor the Three Sisters; clover, vetch, and cowpeas work as borders or cover crops.
what is allelopathy and which plants do it
a: Allelopathy is when a plant releases biochemicals that inhibit germination or growth in neighbors. The clearest cases are black walnut, cereal rye, sunflower residues, and sorghum-sudangrass — many "X hates Y" companion claims are resource competition misread as chemistry.
do onions and garlic hurt beans
a: The warning is real but overstated — alliums near legumes can reduce growth, but the mechanism is competition for water and root space, not confirmed allelopathy. Border placement with a buffer solves it.
how do I build a companion planting guild around a fruit tree
a: Stack functions in rings — dynamic accumulators and alliums at the dripline, pollinator flowers mid-range, nitrogen-fixing groundcover at the outer edge. Trunk zone stays clear.
iii. query intent
Questions about plant relationships — what grows together, what conflicts, how systems are built, and why interactions occur.
details
- Companions covers the full range of plant relationships — from single pairings between two vegetables to multi-species guild design around fruit trees and perennial systems. Territory spans annuals, perennials, trees, herbs, groundcovers, and cover crops across any growing context. Practices range from well-documented intercropping science to Indigenous polycultures with centuries of refinement to traditional companion lore with mixed evidence. The tool names the origin, explains the mechanism, and distinguishes what is proven from what is practiced.
- specific pairing: what beneficial associations exist between two named plants or species, and what the mechanism is
- antagonistic pairing: what competitive or inhibitory relationship exists between two plants, whether the mechanism is allelopathy or resource competition, and what the practical separation logic is
- guild system: how a named multi-species combination functions, what role each plant fills, and how the system holds together
- functional category: which plants perform a specific ecological function such as nitrogen fixation, pest diversion, or pollinator attraction, and how that function works in a shared growing environment
- compatibility check: whether a traditional pairing warning is real, what the actual mechanism is, and whether spacing or chemistry is the driver
- design question: how to build a companion system around a specific crop or tree, what goes in each spatial zone, and how layers are structured
- traditional lineage: where a companion practice originates, which Indigenous agricultural system or historical polyculture it comes from, and what that context adds to understanding the relationship
- evidence question: whether a companion relationship is research-backed, mechanistically plausible, or traditional with limited study, and what that distinction means for how much to rely on it
iv. usage
Use when a plant relationship question needs to be resolved before planting, during planning, or when something in a growing system is underperforming or conflicting.
details
- new bed planning:
deciding what to grow together before anything goes in the ground and wanting to know what combinations work and why - specific crop companions:
working with a named crop and wanting to maximize it with the right neighbors for pest pressure, pollination, or soil support - underperforming plant:
something in the garden is struggling and a bad pairing or antagonistic neighbor may be the cause - guild design:
building a multi-species system around a fruit tree, perennial, or main crop and needing to know what goes in each layer and why - cover crop timing:
using an allelopathic or nitrogen-fixing cover crop and needing to know when it is safe to plant into it - pest pressure reduction:
trying to reduce pest damage without chemicals and wanting to know which companion plants help and how - pollinator support:
wanting to increase pollinator activity around a crop to improve fruit set or beneficial insect presence - traditional system:
working with or trying to understand a named polyculture like Three Sisters and wanting to know how it functions and where it comes from - pairing warning check:
heard that two plants should not go together and wanting to know if the warning is real and what the actual mechanism is - lineage question:
wants to know the origin of a companion practice before committing to it - low-input system:
building a no-dig, no-spray, or low-input growing system and needing plants that support each other without external inputs - antagonistic neighbor:
a plant keeps failing and a nearby species may be suppressing it through competition or allelopathy
v. structure
Output is returned as a structured relationship analysis — fields vary by query type and appear only when they apply.
details
- plant or combination:
the named plant, pair, or multi-species system being examined — set as the active subject for the full response - beneficial associations:
what grows well together, what each plant contributes to the other, and what the mechanism is — chemical, physical, biological, or ecological - antagonistic relationships:
what competes, inhibits, or harms, whether the mechanism is allelopathy or resource competition, and what the practical separation or management logic is - root interactions:
allelopathic compounds, mycorrhizal sharing, root zone partitioning, and how roots from different species compete or complement each other below ground - nutrient relationships:
nitrogen fixation, dynamic accumulation, and nutrient cycling — including when the benefit arrives and how much transfers to neighboring plants - spatial compatibility:
height, canopy spread, root depth, light competition, airflow requirements, and buffer distances between species - traditional practices:
how the pairing or system is applied in practice — spacing, timing, sequencing, and regional variations - guild structure:
appears on multi-species system queries — names what function each species fills and how the layers support the whole system - nurse plants:
appears when a protective species is part of the system — what it shields, how, and when it is removed or managed - trap crops:
appears on pest management queries — which plant draws the pest, how to place it, and what to do once pests concentrate there - pollinator support:
appears when pollinator attraction is relevant — which combinations increase pollinator activity and what the mechanism is - traditional lineage:
appears when the practice has a named origin — the Indigenous agricultural system, regional farming tradition, or historical polyculture it comes from - evidence note:
appears when the evidence picture is uneven — flags whether the relationship is research-backed, mechanistically plausible, or traditional with limited study
vi. handles
Plant relationships, companion combinations, and interactions between species growing within shared environments.
details
- any plant species:
annuals, perennials, trees, shrubs, herbs, groundcovers, vines, and cover crops across any growing context or climate - any species combination:
pairs, trios, guilds, polycultures, and mixed systems — any combination of plants sharing a growing environment - beneficial associations:
what grows well together, what each plant contributes to the relationship, and what the biological or chemical mechanism is - antagonistic relationships:
what competes, suppresses, or harms, whether the mechanism is allelopathy or resource competition, and what the practical implication is - guild systems:
Three Sisters, fruit tree guilds, food forests, traditional polycultures, and any multi-species system where plants are chosen to support each other - nurse plants:
protective species that shield more vulnerable plants from wind, sun, frost, or pest pressure during establishment or across seasons - trap crops:
sacrifice plants used to draw pest pressure away from a main crop, including placement, timing, and management once pests arrive - root interactions:
allelopathic compounds, mycorrhizal sharing, root zone partitioning, cover crop residue timing, and how roots from different species compete or complement each other - nutrient relationships:
nitrogen fixation, dynamic accumulation, living mulch cycling, and soil improvement through companion plant biomass and residue decomposition - pollinator support:
combinations that increase pollinator and beneficial insect activity, including which flowers attract which insects and how proximity affects fruit set - spatial compatibility:
height, canopy spread, root depth, light competition, airflow requirements, buffer distances, and living mulch placement within a system - traditional lineage:
named Indigenous agricultural systems, regional farming traditions, and historical polycultures — where a practice comes from and what that context reveals about how it works - evidence assessment:
whether a companion relationship is research-backed, mechanistically plausible, or traditional with limited study — and what that distinction means for how much to rely on it
vii. limits
Excluded territory and functions this engine does not perform.
details
-
plant identification:
does not identify unknown plants — bring a known species name to explore its relationships. -
propagation methods:
does not cover how to take cuttings, graft, divide, layer, or root a plant. -
species distribution and native range:
does not cover where a plant naturally occurs, has naturalized, or is considered invasive. -
volunteer and weed interpretation:
does not interpret what a self-seeded or opportunistic plant is or what its presence signals about the soil or site. -
pest diagnosis:
does not identify what is attacking a plant, what the damage pattern indicates, or how to treat an infestation. -
plant disease diagnosis:
does not identify, assess, or provide treatment protocols for plant disease. -
soil composition and growing medium analysis:
does not assess what a soil or substrate is, how it behaves, or how to improve it. -
garden design as the primary task:
does not produce full garden layouts, bed plans, or design documents — spatial logic within a companion system yes, standalone garden design no. -
wildlife management and animal behavior:
does not cover animal deterrence, habitat management, or animal interaction with plants. -
conservation policy and environmental regulation:
does not cover protected species status, land use compliance, or ecological regulation.
viii. insights
Recurring patterns observed in how plant relationships, companion systems, and growing interactions actually work.
Most companion planting advice skips the mechanism. Knowing that basil grows well with tomatoes is less useful than knowing why — and the why determines whether the pairing holds in your conditions or only in someone else's garden.
Allelopathy is real but massively overclaimed. The majority of failures attributed to chemical suppression are spacing and competition failures. The fix is distance, not removal. True allelopathy — black walnut, cereal rye, sorghum — is the exception, not the rule.
The nitrogen timing assumption is wrong in most gardens. Legumes fix nitrogen for themselves first. Neighboring plants get the benefit after the legume is cut, turns over, or its roots decompose. Planting beans beside corn does not fertilize the corn in real time.
Traditional companion practices often encode genuine functional knowledge that was never written down as science. The Three Sisters is not folklore — it is a refined polyculture system with centuries of selection behind it. The mechanisms are real. The lineage matters because it tells you the system was tested across generations, not just one season.
The insectary principle is more powerful than any single companion plant. A diversity of bloom types and timing near a crop recruits more beneficial insects than any one species. The goal is a season-long nectar corridor, not a single pairing.
Trap crops only work if you manage them. Once pests concentrate on the sacrifice plant, you have to destroy or treat it immediately. An unmanaged trap crop becomes a pest nursery that amplifies the pressure it was meant to solve.
Guild design is about function, not species. Any plant that fills the role — ground cover, nitrogen fixer, pollinator attractor, dynamic accumulator — works. The role is the design decision. The specific plant is a local substitution.
Mycorrhizal networks in mixed plantings are disrupted by tillage more than by competition. Keeping soil disturbance low around companion plantings preserves fungal infrastructure that benefits every plant in the system.
Pest navigation is scent-based. Monocultures concentrate the chemical signal pests follow. Mixed plantings break that signal. The companion planting benefit is often less about any specific pairing and more about disrupting the olfactory landscape pests rely on.
Living mulch is a tradeoff, not a solution. A groundcover companion suppresses weeds and protects soil while simultaneously competing for water and nutrients. In wet climates it tips toward benefit. In dry climates it can tip toward harm. The site determines the outcome.
Most companion failures attributed to bad pairings are actually density failures. Two plants that coexist well at the right spacing become antagonists when overcrowded. Distance is the variable that converts a competitor into a companion.
Cover crop history is a companion decision. What grew in a bed before the current planting affects germination, soil biology, nitrogen availability, and pest pressure as much as what is planted alongside. The temporal dimension of companionship is as real as the spatial one.
The evidence picture in companion planting is uneven in ways that matter. Some relationships are research-backed with repeatable mechanisms. Some are plausible but understudied. Some are tradition with inconsistent results. Knowing which category a pairing falls into determines how much weight to give it when planning.
ix. notes
Resolves plant relationship questions through biological mechanism, spatial logic, and traditional context — returning what the interaction is, why it occurs, and what it means for how plants are grown together.
details
- difference from general companion planting charts: Uses a relationship resolver model rather than a static compatibility table. It considers the specific plants, the mechanism behind the interaction, the growing context, and the evidence behind the claim.
- processing model: Combines species identity, interaction type, mechanism, spatial dynamics, nutrient relationships, traditional lineage, and evidence tier to return a structured relationship analysis.
- input format: Accepts plain-language questions such as "what grows well with tomatoes," "do onions hurt beans," "how does a Three Sisters guild work," or "what is allelopathy and which plants do it."
- traditional lineage and evidence: Names the origin of companion practices where known and distinguishes research-backed relationships from plausible mechanisms from traditional claims with limited study.
- intended users: Designed for home gardeners, market growers, permaculture designers, food forest planners, and anyone building mixed growing systems who wants to understand not just what to plant together but why it works.
- builder: Designed and maintained by jordan r. hale
x. access
How to unlock full access and what is included.
details
- full access: one-time purchase.
- private page: opens the full web version of the tool without preview limits.
- app-style use: save the private page for direct access.
- gpt version: optional ChatGPT version of the tool.
- updates: improvements included over time.
xi. privacy
How this engine handles user data and input.
details
- privacy: questions are processed and returned without storage or retention.
- use: no accounts or user profiles; no ongoing tracking.
- interaction: no inbox, follow-up, or outreach.
- payment: checkout (if purchasing access) is handled by Gumroad; this site does not receive card details.
- content: avoid entering sensitive personal or confidential information.
- responses: missing context is labeled; the system does not invent details.