Platform

Crop Picker runs as a modern edge-first web application. This page describes the hosting and release posture for developers integrating with the platform.

#Hosting

• Application: Vercel with global edge caching and automatic HTTPS.
• Data: managed Postgres (Supabase) with PostGIS for geospatial queries.
• Analytics: first-party page-view analytics; no third-party trackers and no PII collection.

#Release process

The site deploys automatically on every merge to the main branch. Each deploy:

• Purges the edge cache so the next request to every URL fetches fresh content.
• Runs post-deploy health checks on the homepage, API, and sitemap.
• Produces a preview deploy on every pull request so changes are validated before going live.

#Availability

Public pages and the public API are served from Vercel's global edge network. Most responses are served from the CDN; true origin fetches happen only on cache miss or background revalidation. See Caching & Performance for the per-endpoint behavior.

#For developers integrating with the platform

• The public REST surface is documented in Crops API.
• All endpoints return JSON with a standard { "data": ... } envelope; see the API page for examples.
• Cache behavior is documented in Caching & Performance.
• The schema your API responses reflect is documented in Data Model & Schema.

#Feedback

Spot a data issue on a crop page? Each detail page's Sources section links back to the original source publication. If you think a number is wrong or out of date, please use the in-page feedback link or email hello@every.farm.