FIELDSERVE
Try 30 days

YOUR ENVIRONMENT, YOUR CHOICE

Choose how
you run Serve.

Field Serve is available as a managed online service or as a tenant-installed deployment planned with Field Serve.

◉

SERVE HOSTED

Ready in your browser.

Field Serve hosts and manages the shared platform. Your company is onboarded into its own workspace, and your monthly plan is based on active user seats and enabled features.

  • Browser-based access for your organisation
  • Company workspace with tenant-isolated records
  • Monthly per-user plans
  • Onboarding and workspace provisioning through Field Serve
Compare hosted plans ↗
⌘

TENANT INSTALLED

Scoped to your environment.

For organisations that require deployment into their own infrastructure. Field Serve will scope hosting, identity, integrations, support and operational requirements with you.

  • Deployment planned for your environment
  • Identity and integration requirements reviewed
  • Support and maintenance responsibilities agreed
  • Commercial proposal based on agreed scope
Discuss an installation ↗

ONBOARDING COMES FIRST

Your workspace should
fit your organisation.

Field Serve will help establish the right users, features and deployment path before your team starts.

Plan your onboarding ↗

CHOOSE A DEPLOYMENT ROUTE

Different operating models, scoped separately.

Field Serve Cloud ↗

Browser-based access with a Field Serve-managed company workspace.

Tenant installed ↗

Technical and operational discovery for your own environment.

DEPLOYMENT DECISION GUIDE

Choose based on who will operate the service.

Both deployment routes need onboarding, access planning and a tested workflow. The important difference is who provides the infrastructure and who owns day-to-day technical operations.

Decision areaField Serve CloudTenant installed
Where it runsField Serve-managed hosted platform, accessed in a browser.A separately scoped customer environment, subject to technical discovery.
Workspace setupField Serve provisions each company workspace and initial access.Field Serve and the customer agree installation, identity and environment requirements.
OperationsHosting and service operations follow the Field Serve Cloud agreement.Monitoring, updates, backups, recovery and support owners must be written into the plan.
CommercialsPer-user monthly plans are published on the Pricing page.Quoted after technical and operational discovery.
IntegrationsCompany-owned connections require their own setup and any provider consent.Network access, app registration and provider responsibilities need to be scoped for the environment.

Questions to answer before choosing

  • Does your organisation require its own hosting boundary, or is a company-isolated hosted workspace suitable?
  • Who can operate databases, backups, updates, certificates and incident response?
  • Which identity systems and provider integrations are required at launch?
  • How many users and field engineers need access, and which roles will they use?
  • Will Field Serve be used alongside the separate Field Serve CRM?

A tenant-installed deployment is not a self-service download. Field Serve needs to confirm the technical fit, responsibilities, security requirements and acceptance tests before providing a quote.