Operate
Pricing and field slots
Compare the free Sandbox with the $49 Founder Pilot and understand exactly how field-slot usage is counted.
Two plans
- Sandbox — $0, no card, no expiry, 5 field slots, data export, Expo starter, and SDK; intended for evaluation and internal prototypes
- Founder Pilot — $49 USD per month, 100 field slots, six-hour weather freshness, weekly satellite monitoring when suitable imagery is available, durable history, export, and email support
- Neither plan has automatic overages. A limit returns a structured error instead of creating a surprise charge
How field slots are counted
- One connected Polygon up to 25 hectares uses one field slot
- Each additional 25 hectares, rounded up, uses another slot
- Each disconnected MultiPolygon component is calculated separately and uses at least one slot
- Editing a field recalculates its slot use; seeded Sandbox fixture fields consume zero slots
- The mapper previews projected use before save, and the API rejects a save that would exceed the plan
Technical fair use
Field slots are the front-facing plan meter. Monthly API and write limits remain as technical guardrails so a bug cannot create uncontrolled upstream cost.
- Sandbox: 10,000 requests and 2,000 writes per UTC month
- Founder Pilot: 50,000 requests and 20,000 writes per UTC month
- GET /api/v1/usage reports field slots, fair-use allowances, reset time, and provider refresh activity