Route-first workflow
Recurring plans generate today’s route, preserve manual order, and keep skipped or rescheduled stops out of billing inputs.
Local-first outdoor service software
GreenKeeper
A route-first mobile app for lawn care, gardening, landscaping, pool service, snow, and similar outdoor providers who need offline visits, proof photos, and clean invoice records.
Built for the phone loop
Today route, visit proof, and billing records stay usable offline.
GreenKeeper is designed around the working day: open today, run stops, save notes, attach photos, generate invoices, and keep local records available even when the network is not.
Proof photos and notes
Visit checklists, internal notes, customer-visible notes, and before/after photos save locally before sync is attempted.
External payment boundary
Invoice PDFs can include your own cash, check, bank transfer, or static QR instructions. GreenKeeper does not process customer payments.
Premium architecture
Local by default, cloud sync only when enabled.
The mobile app uses local storage first. Premium sync uses Firebase Authentication, RevenueCat entitlements, FCM hints, a Rust API, PostgreSQL, and private media storage. Firebase is not used as the app data backend.
- Offline: critical field work writes to the device first.
- Media: photos and invoice PDFs stay private behind authenticated API routes.
- Privacy: analytics and FCM payloads avoid customer PII.
- Payments: manual external payment records only.