Planva can be deployed in an in-country cloud or on your own servers. Field records, agroplans and machine data stay where you choose. The field card also shows NDVI for each field.
Choose deployment against an actual requirement. Your team may need to retain field history in a chosen country, work inside its own infrastructure or keep a clear handover process at the end of the contract. Write those requirements down before comparing proposals.
Two deployment choices to discuss
| Choice | What it means | What to settle before onboarding |
|---|---|---|
| In-country cloud | Planva hosts the platform in an in-country cloud and runs updates and operations. Payment is by subscription. | The records covered, access requirements, backups and the support arrangement. |
| On-prem | A perpetual licence for Planva on the farm’s own servers, with no external cloud. | Infrastructure responsibilities, connectivity, maintenance and recovery arrangements. |
Data placement does not by itself establish a certification, a backup frequency or a recovery time. The data-placement page lists the operational questions to agree.
Inventory the records that matter
- Fields and seasons. Include field identifiers, rotation and the historical seasons the team needs.
- Plans and machine work. Identify the agroplans, machine tasks and plan-versus-actual records required for reporting.
- Exports. Boundaries export to KML and SHP. Agroplans and reports export to XLSX.
- End of contract. Agree which records you will receive, in which formats and who handles the handover.
Test one field before moving the archive
Use a known boundary, one agroplan and one machine task. Check that the agronomist and the dispatcher can do their part. Add a sample of historical records before accepting a larger move. A pilot runs for 2 to 4 weeks on your own fields and machinery, followed by launch with training and support.
Price and support
Pricing depends on acreage, modules, deployment model and implementation scope, and is fixed in the proposal and contract. Migration is included in the contract. The timeline depends on the volume and quality of your exports and is agreed before you sign. Support works 24/7.
Read the checklist for moving from another platform, then bring your data-placement requirements to a demo.
Who should not buy
Do not choose an on-prem deployment unless the infrastructure and maintenance responsibilities are agreed. If a certification or specific integration is mandatory, require evidence before committing.