Frontline PSA

Platform

Open where it helps, locked down where it matters.

Frontline PSA connects to your customers' tenants without holding their credentials, speaks an API your existing tools already understand, and records who did what. It runs on your own infrastructure with a standard PostgreSQL database.

Frontline PSA
A customer tenant: its connections, their health and the actions available.

Customer tenants

Reach into the customer's environment, safely

Tenant actions run through DPGatekeeper, Dual Path's access broker. The PSA never stores a vendor credential. It links each company to its tenant and asks Gatekeeper to act.

  • Lookups run straight away: Microsoft 365 users, groups, licences, domains, managed devices, mailbox and OneDrive usage, Okta users, and Datto RMM sites and devices
  • Results drop into the ticket as an internal note with one click
  • Changes need two people: one requests with a reason, a different person approves
  • Connection health for every tenant on one page
ActionApproval
List and find users, groups, licences, domainsNone, read only
Managed devices, mailbox and OneDrive usageNone, read only
Okta users · RMM sites and devicesNone, read only
Disable accountSecond person
Send mailSecond person
Suspend Okta userSecond person

These are the actions available today. Other changes, such as password resets and licence changes, are not available through Gatekeeper yet.

Autotask-compatible API

Your existing integrations keep working

Frontline PSA serves a REST API at /atservicesrest/v1.0 that follows the Autotask REST API. Point a tool at your Frontline PSA address, give it new credentials, and it reads and writes the same entities.

  • 20 entities including Tickets, TicketNotes, TimeEntries, Companies, Contacts, ConfigurationItems, Contracts, Projects and Tasks
  • Query filters, paging, picklist information and user-defined fields
  • Each API user acts as a named resource, with read-only and impersonation options
  • A request log, and secrets you can rotate or disable per user
  • Picklist values can be mapped to the Autotask numbers your scripts expect
Read the API guide
POST /atservicesrest/v1.0/Tickets

ApiIntegrationCode: ••••••••
UserName: monitoring@yourmsp.example
Secret: ••••••••

{
  "companyID": 3,
  "title": "Backup job failed: FS01 nightly",
  "queueID": 6,
  "priority": 2,
  "status": 1
}

Security and audit

The right access for each role

Seven security levels ship with the product, built from 34 individual permissions that are enforced on the server, not just hidden in the interface.

  • Administrator, Service manager, Dispatcher, Technician, Sales, Finance and Read only
  • Finance data is visible only to levels that include billing
  • An audit log of changes, with export
  • Sign-in through Cloudflare Access, so your identity provider and its MFA policy apply
Frontline PSA
The security levels matrix.

Administration

Shape it to how you work

Queues and SLAs

Your own queues, and SLA targets by priority with business hours.

Workflow rules

Automatic assignment, routing, notes, notifications and to-dos when tickets change.

Roles and rates

Billing roles with their rates, used by contracts and time entries.

Picklists

Your own statuses, issue types, sub-issues, sources and more.

Resources and departments

Who works here, what they can do and who approves their time.

Work types and codes

Billing codes for labour, materials, services and expenses.

Frontline PSA
A workflow rule: when a critical ticket is created, notify the queue.

Deployment

Your infrastructure, your data

Self-hosted

Runs on Node.js or from the supplied Docker image, with a health check endpoint for your orchestrator.

PostgreSQL

A standard PostgreSQL 16 or later database. Your data stays in a format every tool can read.

Try it in minutes

An embedded database and a complete fictional MSP let you evaluate the whole product before connecting anything real.

Straight answers

What Frontline PSA does not do yet

We would rather you hear this from us than find out in week two.

Is there a customer portal?

Not yet. Tickets are created by your team, by recurring templates, or by other systems through the API.

Does it turn incoming email into tickets?

Not yet. Monitoring and other tools can create tickets through the Autotask-compatible API.

Does it send email?

Not in the current release. Notifications appear inside the app, a reply to a customer is recorded on the ticket, and invoice emails are held in an outbox that administrators can review.

Does it sync with accounting software?

Not directly. Invoices and ledger items export to CSV for import into your accounting system.

Do workflow rules cover more than tickets?

Rules run on tickets only in the current release.

Are webhooks or SOAP supported by the API?

No. The API is REST only and does not send webhooks.

See it on your own tickets.

Tell us how your service desk runs today and we will walk you through Frontline PSA with a setup that looks like yours.