A record that grows with you
The current app introduces grow journals with notes, photos and plant metrics. Richer timelines, media context and connected environmental history remain part of the Trellis development direction.
Rooted in the grow. Built by Cadela.
Grow with
a clearer picture.
Trellis by Canopy
Your plants, your notes, your next grow. Cadela Grow is running today. Trellis by Canopy is the broader direction we’re developing around grow records, soil tools and a more connected grow room.
Cadela Grow is online · Sign-in and account creation at app entry.
trellisConcept preview
A little context. A better grow.
Sample journal
One plant.A whole story.
Notes, photos & the recipe that started it.
Transplant day
JournalA new pot. A note for the next grow.
Keep the recipe in context
RecipeSoil mix, amendments & observations.
Designed around the details worth keeping.
01
Cadela
The development brand behind the work.
02
Trellis
The developing software direction, building on Cadela Grow.
03
Canopy
The planned connected grow-room ecosystem.
Trellis by Canopy / The software
Less scattered.
More connected to your grow.
Running app · Development ongoing
Cadela Grow is online. Its public welcome screen introduces journals, photos, a grow feed and soil calculations. Trellis by Canopy is the wider direction for bringing that work and future connected capabilities together.
From a soil recipe to a repeatable process
Soil recipe scaling is presented in the current app. The wider tools roadmap brings recipes and practical measurements into context, with inventory and shopping lists among the development goals.
Knowledge worth passing on
A grow feed and sharing are introduced in the current app. Recipe discovery and broader community knowledge remain areas to develop as the Trellis experience takes shape.
The app opens to a welcome screen with sign-in and account creation. Feature descriptions reflect that public introduction; availability behind sign-in is not confirmed here. Roadmap items remain development goals.
Canopy / The connected environment
A fuller picture.
From plant to room.
Planned ecosystem
Canopy is the connected hardware and automation direction: sensors, environmental telemetry and history, controllers, and rules for the grow room.
The intended bridge into Trellis would put environmental changes alongside plant notes and photos—so growers can review the room and the grow together.
You set the rules.
Automation is intended to be deterministic, bounded and user-controlled. AI may help interpret information and suggest actions; it is an advisory layer, not autonomous hardware control.
How the pieces are intended to connect
Your grow environment
Sensors · Environmental readings · History
Readings inform rules you define
Canopy
Controllers · Bounded automation rules · Hardware integrations
Planned connection to your grow records
Trellis
Plant timelines · Context · Review and understanding
Planned intelligence / Local-first, not local-only
Local first.
Frontier intelligence when it earns its place.
Trellis is being designed for optional, provider-flexible AI. Local and self-hosted models would support everyday work, with external APIs available for selected tasks that benefit from stronger capabilities. This planned layer is separate from the running grow app.
Local execution
Models running on suitable user hardware, for routine, privacy-sensitive or latency-sensitive assistance. Capability depends on the device and model.
Intended for everyday, lower-cost tasks.Self-hosted inference
Models on privately operated infrastructure, with room for workloads beyond a single device. Self-hosted processing may happen on a server, away from your device.
A separate deployment path from local execution.Extra capability, by choice
Selected, user-approved tasks could use frontier models for long grow histories, stronger image understanding, or synthesis across recipes, logs and future sensor history.
Provider-flexible. No single provider required.A deliberate data boundary
The intended design makes cloud AI optional and requires approval of the data shared for a task. Logs and images should not be sent to external AI automatically. These consent controls are planned, not released. Any future opt-in training use would require a separate choice from inference.
Useful assistance, with clear limits
AI is planned to support review and understanding, not guarantee cultivation diagnoses. Local-first does not mean the whole app is offline: community features need networked services. External processing would depend on the selected provider’s terms.
The development direction
Build the useful things.
Grow from there.
A direction of travel, with each layer to be proven before it is presented as available. No release dates or completed milestones are implied.
- Ongoing development
From Cadela Grow to Trellis
Build on the running app’s journal and soil-tool direction. Richer context, inventory and shopping lists remain development goals.
- Planned expansion
Shared growing knowledge
Extend the app’s introduced grow-feed direction with recipe discovery and broader community knowledge. Future scope and availability will be confirmed as work progresses.
- Planned
Hybrid intelligence
Optional local, self-hosted and external API assistance for grow history review, image interpretation and knowledge synthesis.
- Planned
The Canopy environment
Sensors, environmental history, controllers and user-defined automation, with a bridge into Trellis.
Further possibilities include product links, local vendors and community listings. These remain exploratory.
Behind the work
One development brand.
Room to keep building.
Cadela is the broader home for practical apps, tools, games and connected systems. Trellis by Canopy is the grow-focused work taking shape within it: software grounded in the day-to-day, with a longer view of what a connected environment can offer.