Integrations
Integration readiness and data posture.
AcreFrame is designed to pull from existing systems, not replace them. This page documents what is available now, what requires design partner collaboration, and what is planned for production.
Integration matrix
Third-party names are descriptive examples only. No affiliation implied unless separately stated.
| Source category | Example systems | Available now | Design partner mode | Planned production | Data types | Risk controls | Notes |
|---|---|---|---|---|---|---|---|
| Manual / CSV / PDF / email intake | Spreadsheets, PDF prescriptions, email attachments, scanned labels | Yes | Primary mode | Supported indefinitely | Plans, prescriptions, labels, scouting notes, receipts | File type validation, size limits, human review required | Most pilots start here. No API required. |
| Weather APIs | NOAA, private weather services (descriptive examples only) | Partial | Manual + API hybrid | Multi-source weather with inversion risk | Wind, precipitation, temperature, inversion indices | API timeout/retry, source attribution, human override | No affiliation implied with named services. |
| Farm management systems | FMIS platforms (descriptive examples only; no affiliation implied) | No | CSV export / manual ingest | API connectors where available | Field boundaries, season plans, task lists | Schema validation, artifact source tracking, human review | Third-party names are descriptive only. |
| OEM / fleet / telematics | Equipment manufacturers (descriptive examples only) | No | Manual status input | Telematics ingestion from mixed fleets | Machine location, hours, maintenance status, calibration | API allowlist, timeout/retry, data validation | No OEM partnership or live integration exists today. |
| Imagery / sensors | Satellite, drone, soil sensor platforms (descriptive examples only) | No | Manual file upload | Signal ingestion as task triggers | NDVI, soil moisture, thermal, scouting imagery | File type validation, metadata extraction, source tagging | No live sensor feed integrations exist today. |
| Accounting / inventory | ERP, inventory systems (descriptive examples only) | No | Manual cost input / spreadsheet | Invoice/cost cross-reference via API or file | Input costs, invoices, lot tracking, inventory levels | Schema validation, reconciliation review, no write-back without approval | Read-only or file-based initially. |
| Agronomy / scouting | Scouting apps, agronomy platforms (descriptive examples only) | No | Manual note / image upload | Structured scouting signal intake | Observations, recommendations, imagery, pest pressure | Human review before task creation, source attribution | No live agronomy platform integrations exist today. |
| Work-order / dispatch systems | Dispatch platforms (descriptive examples only) | No | Manual queue export | Bidirectional queue sync where APIs exist | Work orders, assignments, completion status | API allowlist, conflict resolution, human approval | Future production capability. |
Data validation model
File type validation: only accepted formats are processed
Schema validation: structured data must match expected shape
Artifact source tracking: every document is tagged with origin and date
Human review: all ingestion outputs are reviewable before use
API timeout/retry/allowlist: no blind external calls
No blind redirect following: external links are not automatically traversed
No unsafe scrape ingestion: data is only ingested from user-uploaded files or approved APIs
Robots/ToS-aware public source policy: public data ingestion respects robots.txt and terms of service
Security and data boundary
- All data in transit is encrypted via TLS 1.2+
- Farm data is not sold or shared with third parties
- API keys and tokens are stored in environment variables, never in client code
- File uploads are scanned for type and size; malware scanning is planned for production
- Integration tokens will be stored in a secrets manager for production deployments