The platform in figures and diagrams
Phoeniks has been available since 15 October 2026, with a new version every week. It runs in production as one platform in three layers (Distribution, Intelligence, Infrastructure). Its catalogue counts 440 features traced across business domains, of which 398 are implemented. A governed records engine holds the records a regulator or an auditor may verify: one person creates, another approves, and every step is written to an audit trail.
Range#
Distribution is what buyers, investors and agencies use: map-based land search, the diligence pack and the agency space. Intelligence produces the estimates: yield with a p10 to p90 band and its provenance, crop fit and land risk. Infrastructure is what institutions audit: governed records, provenance and licences, the audit trail and exports. Modules for EUDR, lending, insurance and carbon open per segment.
Feature coverage#
The architecture trace of 17 October 2026 maps 440 features to the code: 398 implemented, 19 partial, 11 in construction and 12 not yet traced. Each feature belongs to one business domain.
Simplified architecture#
Public sources and client data are imported only after their rights and licence are checked. They feed a governed land corpus, from which the intelligence is computed. Records that need approval go through the governed records engine. Users receive the result in the web application, as PDF packs, through the API or as a data feed. Isolation per organisation, data kept in its jurisdiction, access by role and logged actions apply at every step.
Evidence chain#
Every output resolves to one chain: source, dataset version, model version, run, output and export. Nothing is overwritten, and every export carries a fingerprint of its content.
Governed records#
- One maker, one checker: the person who creates a record cannot approve it.
- Every sensitive step asks for a reason; a rejection asks for a comment.
- Emergency access is limited to a few predefined reasons and always reviewed afterwards.
- The audit trail is checked every day; personal data can be erased without breaking it.
What this page does not claim#
Phoeniks holds no SOC 2 attestation and no ISO 27001 certificate today. Offers and prices are set per engagement and are not published here.
Frequently asked
- How many features does the platform have?
- 440 features are traced to the code; 398 are implemented, 19 partial, 11 in construction and 12 not yet traced (architecture trace, 17 October 2026).
- What is a governed record?
- A record created by one person and approved by another, whose every step is written to an audit trail that can be verified.
Related pages
Parcel search
Search a normalised farmland inventory built from public portals, with map results, filters, source provenance on every listing and shortlist comparison.
Yield prediction
Per-property yield estimates from APSIM, DSSAT and ORYZA where licensed, otherwise an FAO-type model; crop fit, scenarios and transparent scoring.
Evidence and diligence
Validation packs, evidence scoring levels, a reproducibility ledger, diligence PDF export and a pre-diligence room for reviewable farmland decisions.
Data and API
Sentinel-1, HLS, AgERA5, CHIRPS, France RPG, IBGE SIDRA and CIMMYT ingestion, exposed through a listing intelligence REST API and an institutional feed.
Carbon MRV evidence
Baseline reconstruction, monitored change with uncertainty and permanence-risk inputs for agricultural carbon projects and buyers.
Insurance analytics
Yield deviation, basis-risk analysis and parametric trigger design built on documented crop models and replayable weather scenarios.
Scope 3 agriculture
Sourcing-region evidence for food and CPG companies reporting agricultural Scope 3 emissions and land-use change.
Commodity intelligence
Regional production trajectories and in-season deviation signals for traders and analysts covering agricultural commodities.
Data sources
The families of data Phoeniks ingests: satellite, weather and reanalysis, soil, land registry, official statistics and market records.
Six journeys for five groups of target users
What each target user can do in Phoeniks V1: buyers, lenders and insurers, allocators, agencies and brokers, regulated operators, through six journeys.
See also
Request access
Institutional access. No self-serve trial.