Domain projects
Relevant project experience in CEA, clearly attributed.
Domain evidence behind the Crop Urbanis Platform.
Crop Urbanis’s product model is informed by practical work across vertical farms, hydroponic greenhouses, crop systems, supplier information, feasibility, commissioning, protocols and optimisation.
Evidence categories
Five distinct evidence categories.
This page separates domain project experience, public case studies, product capability, private-beta evidence when publishable and research. Each category has a different relationship to the current product and a different publication threshold.
Product architecture
The Platform workflow, data model, module set and technical architecture.
Internal MVP
Operational product capabilities described by module and status without exposing confidential workspaces or project data.
Private beta
Selected organisational evaluations. Names or results are published only with permission.
Research
Methods, schemas, evaluations and non-confidential findings.
Archive boundary
Historical work provides context, not automatic product proof.
Retained case studies must state role, attribution and evidence category. Crop Urbanis does not invent testimonials, customer counts, measured outcomes, product deployments or partner relationships.
- Current product evidence
- Operational internal MVP and selectively scoped private-beta work are stated without exposing confidential product data.
Product evidence route
Read the product record alongside project context.
The Platform page, MVP & Private Beta record, technology page and technical brief describe the software workflow. Project pages remain explicit about historical relationship and publication permissions.
- Product
- Operational internal MVP and selected organisational private beta.
- Projects
- Attributed historical context and scoped evidence.
- Research
- Applied R&D and publishable validation routes.