Skip to main content
Menu
Private Beta FR

Product status

Operational internal MVP. Selective private beta.

Crop Urbanis considers selected organisations for private-beta access. Access is not public or self-service and is governed through a separately agreed scope covering data, confidentiality, authorised users, responsibilities, support and evaluation criteria.

Last updated:

Request private-beta considerationExplore the Platform
Current stage
Operational in internal MVP Internal MVP — the core workflow exists and is operational inside Crop Urbanis.
Selective private beta Selective private beta — a limited number of qualified organisations can be considered through direct contact.
In validation Cloud beta preparation — secure organisational deployment, tenant separation, workflow monitoring, data controls and production hardening are the next stage.
Selective private beta Individually scoped beta terms — access and support are defined individually while initial workflows are validated.
Module status

Public access is not required for a module to be operational. The current status below distinguishes the internal MVP from scope-dependent beta work and later roadmap capability.

Project Brief and Data Room

Workflow role
Create one controlled CEA project record from a brief and permitted source material.
Current operation
Structure source links, versions, evidence gaps and access notes.
Controlled output
A traceable brief and evidence register.

Requirements and Constraint Model

Workflow role
Turn project inputs into explicit, source-aware requirements and constraints.
Current operation
Normalise terms, units, owners, conflicts and validation questions.
Controlled output
A requirements and gap/conflict record.

Crop and Production Configuration

Workflow role
Make crop, system and production assumptions comparable before a project direction is selected.
Current operation
Record crop, capacity, cycle and operating assumptions as controlled alternatives.
Controlled output
Comparable configurations and explicit assumptions.

Supplier and Equipment Intelligence

Workflow role
Compare supplier and equipment information against defined project requirements.
Current operation
Extract, map and compare permitted supplier information with source references.
Controlled output
A source-aware comparison record.

Scenario and Economics Engine

Workflow role
Compare production and financial options through controlled assumptions and deterministic calculations.
Current operation
Keep formula ownership, assumptions, sensitivities and changes explicit.
Controlled output
A reviewable scenario and decision record.

Delivery and Decision Control

Workflow role
Govern project choices, dependencies, changes and decision gates across a defined delivery scope.
Current operation
Record owners, dependencies, risks, changes, approvals and unresolved actions.
Controlled output
A controlled decision and responsibility record.

Commissioning and Handover Pack

Workflow role
Turn an approved configuration into controlled readiness, commissioning, training and handover inputs.
Current operation
Organise readiness checks, dependencies, initial protocols and acceptance conditions.
Controlled output
A controlled handover-pack structure.

Operations Feedback Layer

Workflow role
Feed operating evidence and qualified learning back into later project and protocol decisions.
Current operation
Prepare a governed model for KPI records, issue histories and reviewed feedback.
Controlled output
A later feedback layer for governed learning.

Crop Urbanis considers selected organisations for private-beta access. Access is not public or self-service and is governed through a separately agreed scope covering data, confidentiality, authorised users, responsibilities, support and evaluation criteria.

What each module actually is today

Project Brief and Data Room

Operational in internal MVP
Current capability
Operational in the internal MVP.
Available to
Internal teams and selected private-beta partners under agreed scope.
Public evidence
Private workspaces and project data are not published publicly.

Requirements and Constraint Model

Operational in internal MVP
Current capability
Operational in the internal MVP.
Available to
Internal teams and selected private-beta partners where appropriate.
Public evidence
Individual project records remain confidential.

Crop and Production Configuration

Operational in internal MVP
Current capability
Operational in the internal MVP with expert review.
Available to
Internal teams and selected beta scopes.
Public evidence
Project-specific assumptions remain confidential.

Supplier and Equipment Intelligence

Operational in internal MVP
Current capability
Operational in the internal MVP.
Available to
Internal teams and selected private-beta partners under data terms.
Public evidence
Supplier documents and commercial terms are not published.

Scenario and Economics Engine

Operational in internal MVP
Current capability
Operational internally and expert-reviewed in selected beta scopes.
Available to
Internal teams and selected private-beta project scopes.
Public evidence
Scenario inputs and commercial information are not published.

Delivery and Decision Control

Operational in internal MVP
Current capability
Operational in the internal MVP.
Available to
Internal teams and selected partners within agreed responsibilities.
Public evidence
Decision histories and dependencies remain private.

Commissioning and Handover Pack

Operational in internal MVP
Current capability
Operational in the internal MVP and continuing through scoped validation.
Available to
Internal teams and selected beta scopes where responsibilities are agreed.
Public evidence
Commissioning materials and approval chains are not published.

Operations Feedback Layer

Roadmap
Current capability
Roadmap and scoped validation, not a public operations dashboard.
Available to
Later beta scope after governed operating-data conditions are in place.
Public evidence
Operating records and private-beta learning remain confidential.
What private beta means
Selective private beta Suitable organisations CEA developers, hydroponic greenhouse developers, operators, investors, suppliers, integrators, engineering and delivery partners, research organisations and corporate innovation teams can be considered.
Selective private beta Selection criteria Crop Urbanis reviews the objective, module relevance, source rights, named reviewers, confidentiality needs, success criteria, realistic scope, timing and potential product learning.
Selective private beta Possible scope A defined scope can cover one organisation or project workspace, permitted data categories, selected modules, controlled outputs, named responsibilities, support, feedback and retention terms.
Selective private beta Access decision Submission does not guarantee access. Crop Urbanis may propose a private-beta scope, a project-development engagement, research or technical collaboration, later follow-up, or no engagement where the use case is outside current scope.

Business model

Software access, private deployment and implementation.

The model is built around recurring Platform access, private organisational deployment, fixed-scope onboarding and optional expert support for agronomy, implementation, validation and customer success. During private beta, terms are defined individually; standard plans follow validation of the initial workflows.

Platform access
Recurring organisational workspaces and project records.
Private deployment
Specific data, integration or governance needs.
Onboarding and support
Configured initial information, validation and implementation support.
Cloud deployment priorities
In validation Secure workloads Application compute, managed database, object storage, document versioning, document-processing workers, model inference, vector retrieval and orchestration queues.
In validation Governed access Authentication, tenant separation, audit logs, secrets management, backups, recovery, monitoring and alerts.
In validation European deployment EU-region deployment and controls appropriate to selected organisational beta scopes.
Continuing controls and scope by module

Project Brief and Data Room

Known limitation
Public self-service is not offered.
Review owner
Named project and professional reviewers retain responsibility.
Next validation
Extend controlled organisational workflow coverage.

Requirements and Constraint Model

Known limitation
The Platform does not replace professional approval.
Review owner
Qualified reviewers approve within their scope.
Next validation
Broaden beta workflows and evaluation criteria.

Crop and Production Configuration

Known limitation
No yield, cost or performance guarantee is made.
Review owner
Qualified agronomy and engineering reviewers own applicable assumptions.
Next validation
Evaluate broader controlled project contexts.

Supplier and Equipment Intelligence

Known limitation
It does not confirm warranties, compliance or procurement decisions.
Review owner
Supplier, engineering and procurement authorities remain responsible.
Next validation
Extend permitted-document workflows under review.

Scenario and Economics Engine

Known limitation
It is not investment advice and does not guarantee forecasts or returns.
Review owner
Qualified financial, agronomic and engineering reviewers own applicable decisions.
Next validation
Continue controlled evaluation across selected use cases.

Delivery and Decision Control

Known limitation
It does not transfer legal, engineering or delivery authority.
Review owner
Named project and partner decision owners remain accountable.
Next validation
Refine controlled roles, auditability and handover criteria.

Commissioning and Handover Pack

Known limitation
It does not certify construction, installation, safety or commissioning acceptance.
Review owner
Qualified delivery, commissioning and operating parties approve their duties.
Next validation
Extend controlled beta evaluation of handover workflows.

Operations Feedback Layer

Known limitation
No public operating-performance, image or sensor claim is made.
Review owner
Responsible operating teams and qualified agronomic reviewers govern future use.
Next validation
Establish governed data, review and evaluation conditions before expansion.
Product roadmap
Operational in internal MVP Phase 1 — Internal MVP Project data model, core document workflow, deterministic scenario services, review and decision record, and controlled outputs.
Selective private beta Phase 2 — Selected organisational beta Secure hosted environments, user and organisation controls, scoped workspaces, beta support, data lifecycle controls, workload monitoring and output evaluation.
Roadmap Phase 3 — Product hardening Standard integrations, reusable templates, enterprise administration, deployment automation, reliability and cost optimisation, and standard commercial plans.
Roadmap Phase 4 — Expanded intelligence Operating feedback, image and sensor workflows, advanced analytics and cross-project learning under governed data conditions.

Growth plan

From internal MVP to organisational beta and commercial scale.

Crop Urbanis is expanding product engineering, AI and data, cloud and security, CEA science and validation, implementation, and customer deployment and support. Crop Urbanis plans to seek external startup financing to accelerate this expansion.

Product engineering
Workflow, interface and deployment capability.
AI, data and cloud
Governed intelligence, evaluation and secure operations.
CEA validation and deployment
Professional validation, implementation and customer success.

Product record and boundaries

These public routes explain the Platform, its technical approach and public-form boundary. They do not create an account or authorise confidential data exchange.

Product Overview Technical Brief Security and Data Boundaries Product FAQ

Provide high-level organisational and project context. Crop Urbanis will review fit and respond with the appropriate route. Do not send confidential files through the public form; product access and data exchange begin only after a separate scope is agreed.

Request private-beta considerationDiscuss a CEA project