OpenFieldPro
github.com
- Free plan
- Web
- iPhone and iPad
- Android
- API
- Self-hosted
What OpenFieldPro is
OpenFieldPro is free, open-source field-service management software that can be self-hosted for operations from lead through payment. Its workflows include CRM, customer and property records, equipment histories, scheduling, dispatch, work orders, estimates, invoicing, payments, documents, service plans, reviews, and reporting. Technicians have mobile workflows with offline foundations. Payment capabilities include line-item estimates, invoices, offline payments, optional Stripe checkout, and Stripe webhook processing. A plugin registry, scoped API tokens, and outbound events form part of its integration surface. The repository includes helpers for installation, updates, backup, and restore. The listed stack combines a Next.js web frontend, Fastify API, React Native Expo mobile app, and PostgreSQL database. The README describes production checks for JWT secrets and CORS configuration, as well as bounded route-level rate limits for selected functions. It also describes no telemetry or phone-home licensing, with optional entitlements verified locally. The core is licensed under GNU Affero General Public License version 3, with no stated limits on users, technicians, customers, jobs, invoices, locations, or core operational features. The project is undergoing release-candidate hardening; production release still requires its release checklist gates.
Who it suits
OpenFieldPro suits field-service teams seeking a self-hosted system spanning customer records, dispatch, work orders, estimates, and payments. Its mobile workflows with offline foundations may also suit technicians working away from the office.
Good to know, and what to watch
- Covers CRM through invoicing, payments, and reporting.
- Technician mobile workflows have offline foundations.
- Includes self-hosting helpers for install, backup, and restore.
- No stated limits on core users or operational records.
- Optional Stripe checkout and webhook processing.
- Project is still undergoing release-candidate hardening.
- Production release still requires release checklist gates.
- Support questions and ideas go to GitHub Discussions.
Plans
Every plan and priceSelf-hosted AGPL core
Free plan
Getting started
- Open the OpenFieldPro GitHub repository
- Choose a web, Android, iOS, API, or self-hosted deployment
- Use the repository's self-hosting helpers for installation
- Configure production JWT secrets and CORS settings
- Set up records, scheduling, work orders, estimates, invoices, and payments
Limits to check
The Self-hosted AGPL core plan costs nothing and lists no limits on users, technicians, customers, jobs, invoices, locations, or core operational features.
The Club's review
OpenFieldPro is an open-source field-service management system covering lead-to-payment work in a self-hostable deployment. It is aimed at contractors and service teams that want control of their data and infrastructure rather than a hosted subscription. The broad workflow coverage and unlimited core records are its strongest advantages, while release-candidate hardening makes production adoption a calculated decision.
Overview
The system brings customer and property records, equipment history, scheduling, dispatch, work orders, estimates, invoicing, payments, documents, service plans, reviews and reporting into one operational flow. That scope is useful for businesses that would otherwise combine CRM, job management and billing tools. It is less compelling for organizations that require a mature, vendor-operated service with established production support.
OpenFieldPro is licensed under GNU Affero General Public License version 3. The repository describes release-candidate hardening still in progress, with production release dependent on remaining checklist gates. Teams should therefore be comfortable managing release risk and their own deployment.
Key features
Office staff can manage leads through customer and property information, equipment history, estimates, work orders, scheduling and dispatch. The dispatch board, online booking and estimate builder address the core coordination tasks of a field-service business, while invoicing, document handling, service plans, reviews and reporting extend the system beyond basic job tracking.
Technician workflows are delivered through a mobile app with offline foundations. That is particularly relevant for sites with unreliable connectivity, although the project does not promise that every mobile action remains fully available offline. Payment handling includes line-item estimates, offline payments, optional Stripe checkout and Stripe webhook processing, covering a practical quote-to-payment path without implying support for every payment provider.
For integration work, OpenFieldPro describes a plugin registry, scoped API tokens and outbound events. Those give an internal development team ways to connect other systems while retaining token scope. Self-hosting helpers cover installation, updates, backups and restores, reducing the amount of deployment tooling a small team must assemble itself.
The listed architecture combines a Next.js web frontend, Fastify API, React Native Expo mobile app and PostgreSQL database. Production startup rejects default or short JWT secrets and wildcard or missing production CORS settings. Bounded route-level rate limits apply to authentication, public booking, uploads and checkout. The project also describes no telemetry or phone-home licensing, with optional entitlements verified locally, which suits organizations that want tighter control over operational data.
Pricing
Self-hosted AGPL core — free. The free plan has no limits on users, technicians, customers, jobs, invoices, locations or core operational features. It includes the mobile app, dispatch board, online booking, estimate builder, work orders and invoice payments. This is an unusually permissive baseline for a team able to provide its own hosting, maintenance and support.
There are no cheaper tiers to compare, and the zero price does not remove the operational work of running a self-hosted application. Support is community-oriented: bugs and feature requests go to GitHub Issues, while questions and ideas belong in GitHub Discussions.
Platforms
OpenFieldPro provides Android and iOS mobile access, a web frontend, an API and self-hosted deployment. The combination supports technicians in the field, browser-based office work and teams that need to connect external systems through an API.
Who it's for
It is a strong fit for plumbing and other field-service businesses that want one system for dispatch, work orders, estimates, billing and technician mobility, and that have the skills or willingness to self-host PostgreSQL-backed software. The unlimited records and AGPL licensing also suit growing teams that want to avoid per-seat or per-job restrictions.
Look elsewhere if your priority is a hosted service with a vendor responsible for uptime, upgrades and production support, or if your organization cannot accept a release-candidate platform. Teams seeking a narrowly focused tool may also find its broad scope more operational responsibility than they need.
Pros and cons
- Pro: Unlimited users, technicians, customers, jobs, invoices and locations remove common growth caps.
- Pro: CRM, dispatch, work orders, estimates, payments and reporting are joined in one workflow.
- Pro: Offline-oriented mobile foundations help technicians working beyond reliable connectivity.
- Pro: Install, update, backup and restore helpers make self-hosting more practical.
- Con: Release-candidate hardening is unfinished, so production teams must accept and manage that risk.
- Con: Self-hosting shifts infrastructure, upgrades and operational support to the customer.
- Con: Payment connectivity centers on offline payments and optional Stripe features rather than a stated broad provider catalogue.
Alternatives
Opsler is the better starting point for a small team wanting a hosted freemium option: its Budding plan is free forever for two seats and 50 jobs per month, with unlimited customers and 100 inventory items.
ServiceM8 suits a solo operator who prefers a paid platform with a free tier limited to one user and 30 jobs per month, plus per-SMS charges.
FieldBench is a fit when a hosted web and mobile product with a defined entry cap is preferable; its free plan allows one user and up to 20 jobs per month.
Contractor+ targets businesses starting with a free-forever plan limited to 250 leads and clients and five estimates or invoices per month.
Tradify is for teams ready to pay for a hosted, cross-platform job-management service; its Lite plan is $47 per user per month.
Jobber offers a paid hosted alternative with online booking and scheduling in its Core plan, priced at $29 a month when billed annually.
Fergus is another paid field-service platform with quoting, job cards, GPS tracking, timesheets and recurring jobs in its Essentials plan.
Joblogic is suited to buyers seeking a paid, annually billed service with customer, site, asset and job management in its Standard plan.
The Plumbing Software category is useful when comparing more tools built for plumbing operations.
Verdict
Choose OpenFieldPro if you want an AGPL-licensed, self-hostable field-service system with unlimited core records, mobile workflows and a complete path from booking and dispatch to payment. Look elsewhere if release-candidate status or the responsibility of hosting and supporting your own production system is unacceptable; a mature hosted alternative will be the safer operational choice.
The verdict
OpenFieldPro offers a broad set of field-service workflows in a self-hostable AGPL-licensed core. Its release-candidate status is important to weigh for production use.
Questions people ask
Is OpenFieldPro free?
Yes. The Self-hosted AGPL core plan is free.
Which platforms does it support?
OpenFieldPro supports Android, iOS, web, API, and self-hosted deployments.
Is OpenFieldPro open source?
Yes. The repository uses the GNU Affero General Public License version 3.
Does it include mobile technician workflows?
Yes. Mobile technician workflows are available and have offline foundations.
Can it process payments?
It supports estimates, invoices, offline payments, optional Stripe checkout, and Stripe webhook processing.
What the maker publishes
- Core workflows
- It provides CRM, customer and property records, equipment history, scheduling, dispatch, work orders, estimates, invoicing, payments, documents, service plans, reviews, reporting, and technician mobile workflows. source
- Integrations
- The project describes a plugin registry, scoped API tokens, outbound events, and an integration surface. source
- License
- The repository license is GNU Affero General Public License version 3. source
- Payments
- The project describes estimates, line items, invoices, offline payments, optional Stripe checkout, and Stripe webhook processing. source
- Privacy
- The README describes the project as having no telemetry or phone-home licensing and says optional entitlements are verified locally. source
- Product
- OpenFieldPro is open-source, self-hostable field-service management software for lead-to-payment operations. source
- Release status
- The README describes the project as undergoing release-candidate hardening and says production release still requires its release checklist gates. source
- Security
- The README says production startup rejects default or short JWT secrets and wildcard or missing production CORS configuration, and applies bounded route-level rate limits to authentication, public booking, uploads, and checkout. source
- Self-hosting
- The repository includes self-hosting install, update, backup, and restore helpers. source
- Support
- The support guide directs users to GitHub Issues for bugs and feature requests and GitHub Discussions for questions and ideas. source
- Technician workflows
- The technician mobile workflows have offline foundations. source
- Technology
- The listed stack includes a Next.js web frontend, Fastify API, React Native Expo mobile app, and PostgreSQL database. source
Checked against the maker's pages on 2 Oct 2026.