Open-source field service management that's fast and easy to use.
Customers, service locations, dispatch board, estimates, invoices, service agreements and billing, plus a customer portal and a public booking page — in a keyboard-friendly UI. Self-host for free, or use Tredaro Cloud.
- Customers: searchable roster with CSV import/export + merge, residential/commercial, service locations with equipment records, documents, per-customer balances and portal invite links
- Jobs & dispatch: unscheduled queue, technician board, status events (dispatched → en route → on site → done), priorities, job types with colors + material kits, helper techs, recurring jobs, reschedule/cancel request triage, GPS ping, per-tech iCal feeds
- Estimates: line-item builder with good/better/best option groups, revisions, shareable public approve/decline links (
/e/[token]) with viewed-tracking; approval converts to a job; follow-up reminders - Billing: invoices from completed jobs, charges, payments with oldest-first allocation, refunds, customer balances; Stripe Checkout/Connect for online card payments with tips and receipts; payment-history timeline, statement export, late-fee + overdue reminders
- Service agreements: monthly/annual plans, initial fees, auto-charge + renewal flow, auto-generated maintenance visits
- Pricebook: flat-rate items with cost + category + tax flag, CSV import/export, bulk price adjustments
- Inventory: stock items with reorder points + par levels, purchase orders (draft → ordered → partial receive → paid) with printable supplier POs, truck stock per tech, job materials, low/out-of-stock alerts, CSV import/export
- Team: member profiles with documents (licenses/certs + expiry alerts), time clock, PTO/availability, per-tech tips + commissions, payroll export, staff SMS/email alerts
- Customer portal: scheduled visits, open balance + pay online, pending estimates, agreements, equipment, documents, statement download, request-service form, review + confirm/reschedule/cancel flows
- Public booking page (
/book/[company]): job types, preferred tech + time slots, blackout dates + advance-notice rules, booking deposits, waitlist, anti-spam — lands in the unscheduled queue - Reports: revenue, utilization, margins (labor-inclusive), tips per tech, taxes, payables, CSV exports (incl. QuickBooks + Xero formats)
- Notifications: email + SMS (Twilio) for every customer touchpoint with quiet hours, staff alerts, dedupe log; two-way inbound SMS (confirm/reschedule flows)
- Documents: printable invoice, estimate, work order, purchase order, dispatch day plan and My Day sheets
- Command palette (⌘K),
g d/g p/g j/g c/g e/g b/g a/g k/g r/g tnav shortcuts - REST API + API keys (
td_), signed webhooks (x-tredaro-signature), and an MIT SDK inpackages/sdk - Basic SAML/OIDC SSO and passkeys: included in the free self-hosted core; connect your own identity provider
- BYOK AI: included in the free self-hosted core; use your own API key or a compatible local model endpoint
Webhooks + the REST API are the integration surface.
Tredaro is open core: the core is licensed under MIT, with separately licensed enterprise features. Copy .env.example to .env for self-hosted setup. Report vulnerabilities privately through SECURITY.md.
cp .env.example .env # set a persistent random BETTER_AUTH_SECRET (32+ characters)
# In .env set DATABASE_URL=postgres://tredaro:tredaro@localhost:5432/tredaro
# This database password is for local development only.
docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d db
pnpm install
node --env-file=.env scripts/migrate.ts
pnpm devOpen http://localhost:5173, create an account, then click Explore with demo data.
| Target | How |
|---|---|
| Docker | BETTER_AUTH_SECRET=$(openssl rand -hex 32) docker compose up -d |
| Railway | Manual setup: deploy the Dockerfile with railway.json, add PostgreSQL, and configure DATABASE_URL and BETTER_AUTH_SECRET. |
| Vercel | Button above. Uses @sveltejs/adapter-vercel automatically when VERCEL=1. Migrations run during the build. |
| Render | Button above. render.yaml provisions a Docker web service and a Postgres database. |
| Koyeb | Manual setup: deploy the Dockerfile, add PostgreSQL, and configure DATABASE_URL and BETTER_AUTH_SECRET. |
| DigitalOcean | Button above. .do/deploy.template.yaml creates the app and a dev Postgres on App Platform. |
| Hostinger | Manual VPS Docker Manager setup: deployment guide. |
| Any VPS | docs/deploy-vps.md — same compose file on a ~$4 Hetzner VM or Oracle's always-free tier. |
| Fly.io | docs/deploy-fly.md — fly launch using fly.toml, scales to zero when idle. |
| PikaPods | Not yet in their app catalog — once submitted, a Run on PikaPods badge goes here (~$1.50/mo managed). |
Environment variables are documented in src/env.ts.
Basic SAML/OIDC SSO, passkeys and BYOK AI are included without an enterprise key or Cloud subscription. See the configuration guide. You supply your identity provider and any model-provider credentials; provider usage fees are separate. Credentials stay on the server. Public demos continue to block SSO/passkey configuration.
Set TREDARO_PROFILE_URL to a Leroa Profile service origin (e.g. https://id.leroa.com, or any install running LEROA_PROFILE_HUB=true, including a self-hosted one) to get:
- Continue with Leroa on the login page — unified sign-in across the product suite via the hub's
identityscope (OAuth 2.0 + PKCE; the install's own origin is its client ID, nothing to register). - Connect your Leroa profile in the customer portal — customers share contact details with consent, pick which linked companies stay in sync (
customer.profile_sync), and the daily cron plus portal visits refresh them.
Agreement billing (posting each period's charge and marking overdue charges) runs whenever someone opens the app. The same endpoint also sends automated reminders: appointment reminders to customers (email + SMS, jobs starting within 36h), follow-ups on sent estimates idle for a week, and a morning digest of today's schedule to each technician. To run it on time every day, set CRON_SECRET and call GET /api/cron with Authorization: Bearer $CRON_SECRET. On Vercel, the cron in vercel.json does this for you. Elsewhere, use any scheduler, for example:
curl -fsS -H "Authorization: Bearer $CRON_SECRET" https://dispatch.acme-hvac.com/api/cronKeys are created in Settings → API and are org-scoped, with per-resource read/write grants. GET /api/v1/openapi.json serves a machine-readable spec.
curl -H "Authorization: Bearer td_..." https://dispatch.acme-hvac.com/api/v1/customersWebhooks (Settings → Webhooks) are signed with HMAC-SHA256 in x-tredaro-signature (Standard Webhooks style; see packages/sdk).
MIT for the core, including basic SSO, passkeys and all current BYOK AI features. packages/sdk is MIT. The enterprise license in ee/LICENSE is reserved for future files under src/lib/server/ee/ or marked /* @license Enterprise */; no current application feature requires an enterprise key.
This is pre-1.0 software. Start with a disposable evaluation and check your workflows before using real customer data. Review SECURITY.md, test your identity provider and payment webhooks, verify scheduled jobs, and perform a backup/restore drill for your installation.
For Docker self-hosting, create .env once and keep its authentication secret across upgrades. Optional SSO/AI/provider settings in .env are passed to the application container. Use docker compose up -d --build when building this checkout; published images use version tags rather than an unversioned latest tag.
Before creating a production Compose database, set a persistent URL-safe random POSTGRES_PASSWORD in .env (for example, generate it with openssl rand -hex 32). The tredaro fallback is for local development only. For an existing database volume, retain its existing password: changing an environment variable does not rotate a PostgreSQL role password. Coordinate any rotation with the database administrator and update the application connection string together; never delete/reinitialize the volume to change credentials.
Docker Compose keeps uploaded photos and documents in the uploads volume at /app/data, alongside the separate PostgreSQL volume. Back up and restore both together. Other Node hosts must provide a persistent, writable UPLOADS_DIR; ephemeral/serverless filesystems are unsuitable for uploaded files. After this security upgrade, reissue outstanding portal invitations: legacy links are invalidated, and new invitations are single-use and revoked when portal access is revoked or a new invitation is issued.
The source Compose setup builds this checkout and requires Docker Compose 2.24 or newer for its optional .env file. Rebuild after updating source to pick up security fixes.
After upgrading, previous estimate (/e/), invoice (/i/), service-report (/r/, including photo downloads), booking-cancel and booking-reschedule links stop working. Their old non-expiring format is deliberately rejected; there is no insecure legacy fallback. Re-send outstanding links from staff workflows or use fresh links in the authenticated customer portal. No production links are changed until an operator deploys this upgrade.
New HMAC-authenticated links expire 30 days after issuance for estimates, invoices and booking changes, and 90 days for service reports. Estimate validity dates can end access sooner. Loaders, remote queries/commands, form actions, invoice checkout and photo downloads share the same verifier and return generic not-found responses for invalid/expired links. Draft/expired/superseded estimates and non-completed/cancelled service reports are unavailable; unsharing a photo denies future downloads. Booking changes are blocked once a visit is in progress or done; cancelled bookings cannot be rescheduled, and repeat cancellation remains idempotent. These visit-status checks also run at mutation time; there is no additional hours-before-visit cutoff. A booking more than 30 days after link issuance may need a fresh link. Reissuing a link does not revoke another unexpired link. Individual-link revocation is not available: restrict the underlying record where supported or, for an installation-wide emergency, coordinate authentication-secret rotation (which also affects other authenticated features). Links are bearer credentials: send them only to the intended recipient, and keep them out of logs and public issues.