FlowPSA helps IT support companies (MSPs) and in-house IT teams manage support requests, track the work and time, and prepare draft invoices. PSA stands for professional services automation, software for organizing service work. It is built as the companion to FlowRMM and shares its database, so the remote session and checked action that fixed a computer are saved on the support request.

Do I need FlowRMM to use FlowPSA?

Yes. The current paid offer is FlowPSA as an add-on to a FlowRMM Business subscription, on the same billed endpoint count. FlowRMM works on its own without FlowPSA. Technically, requests do not need a computer attached, but that does not make FlowPSA a separate purchase.

How much does FlowPSA cost?

FlowPSA is an add-on to FlowRMM Business. FlowRMM Business is $1 per endpoint (enrolled computer) per month with a 100-endpoint minimum, starting at $100/month. FlowPSA adds $0.50 on the same count, for a combined $1.50 per endpoint per month, starting at $150/month. Technicians, AI agents, and client portal users are not charged by FlowDevs.

Which AI does FlowPSA use?

Yours. FlowPSA offers MCP (Model Context Protocol), a connection that lets compatible AI apps such as Claude, ChatGPT, or a local model work with FlowPSA through defined actions. There is no paid AI add-on. AI can open, sort, write notes on, and propose work, but cannot approve changes, post invoices, or skip the checks required before a request closes.

Can FlowPSA replace HaloPSA or ConnectWise PSA?

For the daily loop of tickets, dispatch, time, agreements, and invoicing, yes, and it is built to. It is not yet a full replacement for every module of a ten-year ConnectWise configuration: quotes, stock, purchase orders, and e-sign are on the roadmap. We list both on the product page.

Where does FlowPSA run?

FlowPSA runs as an Azure Container App beside FlowRMM in the same Azure environment, in its own Postgres schema, behind Microsoft Entra ID with Admin, Operator, Billing, and Viewer app roles. Setup is self-serve with the guides. FlowDevs offers optional concierge setup as a service, never as a licence gate.

Support requests, work time, and billing

Manage support requests. Track the work. Prepare invoices.

FlowPSA helps IT support companies and in-house IT teams keep customer requests, assignments, work history, time, and billing in one place.

Request access See a walkthrough

For example

A customer needs computer help. Your team records the request, assigns the work, tracks the time, and prepares a draft invoice for review. Everyone can see what happened and what needs to happen next.

PSA stands for professional services automation. Here, it means organizing the work of a service team.

FlowPSA is an add-on to FlowRMM Business · combined $1.50 per endpoint (enrolled computer) per month, from $150/mo · no per-technician fees

FlowPSA / Tickets / INC0001042

PersonAgentFlowRMM evidence

INC0001042HighResolved · vetted

VPN drops at Acme Warehouse

Company: Acme Corp
Site: Acme Warehouse
Device: acme-wks-01
Owner: Alex

FlowRMM09:02
Alert escalated: VPN tunnel down on acme-wks-01
Opened INC0001042 · correlation alert-7731
Your MCP agent09:03internal
Triage: 2 similar resolutions at Acme Corp. Suggests KB-NET-012 VPN failover.
Internal note · proposed task for Networking
Alex (Acme MSP)09:05
Claimed ticket. Task routed to Networking queue.
SLA paused: none · 2h 51m to target
FlowRMM09:11
Remote Console session on acme-wks-01 · 14 min
Session link attached by Alex
FlowRMM09:26verified
Action “Restart VPN client service” approved by Sam · exit 0
Verify event: tunnel up, 3 checks green
Alex (Acme MSP)09:31
Resolution vetted. 0:45 billable logged to Acme Corp agreement.
Draft invoice line created · posting needs a second person

Illustration of one support request (ticket) in FlowPSA, with made-up Acme example data. Press play or pick a step.

shared record with FlowRMM: 1
AI actions available over MCP: 100+
per-technician fees: 0
people to post an invoice: 2

The promise

Open one request. See the whole story.

A ticket is a support request. Anyone on your team should be able to answer these five questions from that one screen, without opening other tools.

01
What is the work?
The title, type of request, priority, and the latest message from the customer.
02
Who owns the next move?
A named person or AI agent who has taken it from a team list.
03
What changed most recently?
The newest entry in one history that is never rewritten.
04
Who and what is involved?
The company, location, contacts, and the FlowRMM computers involved.
05
Is the computer actually fixed?
A recorded FlowRMM session or checked action, not just a note saying “fixed.”

The daily loop

From the first request to the invoice.

Each request moves through the same five steps. When FlowRMM fixes the computer, the record of that work is saved on the request, and approved time becomes a draft invoice.

01
Intake
A request arrives by email, the customer portal, a FlowRMM alert, or an AI agent. A resend never makes a second request.
ensure_work_item
02
Assign
The most urgent request goes to the next person by a published score, not by preference. Tasks go to the right team list under the same request.
claim_next_ticket
03
Work
Open FlowRMM from the request to work on the computer. The session and the approved action are saved in the request history.
session.attached
04
Close
Tasks are done, changes are approved, proof from the computer is saved, and a named person signs off. Then it closes.
resolution_gate.passed
05
Bill
Approved time is applied to the customer agreement and becomes a draft invoice. A second person reviews it before posting.
invoice.draft

People and AI

Let AI help. Keep people in charge.

AI can sort new requests, pick up the next one, draft notes, and propose time entries on the same history as your team. People make the required approvals. This works through MCP, a connection that lets compatible AI apps such as Claude, ChatGPT, or a local model work with FlowPSA. FlowPSA itself decides what the AI is allowed to do, not the AI's instructions.

No paid AI add-on. You choose the AI and pay its vendor, not us.
You can assign work to an AI agent like a person, and it never counts as a paid user.
AI can propose closing a request, a change, or billable time. People decide.

claim_next_ticketget_ticketfind_similar_resolutionsdetect_incident_stormscheck_resolution_gaterequest_resolvelog_timeget_weekly_timesheetcreate_changerequest_change_approvalpreview_invoicerequest_invoice

Who can take each action in FlowPSA
Action	MCP agent	Person
Open a ticket, add an internal note	Yes	Yes
Assign an owner, add tasks	Yes	Yes
Send a customer-visible note	Proposes	Approves
Log billable time	Proposes	Yes
Resolve without an RMM verify event	Proposes	Vets
Approve a change	Never	Second person
Post an invoice	Never	Second person

FlowPSA enforces these rules itself. An AI agent cannot decide any approval. For changes and invoices, a second person reviews it: the person who asked cannot approve their own request.

Everyday help

Less searching. More finished, billed work.

See everything in the product

Smart Dispatch

One button gives each person the most urgent request next, using a published score. A big outage does not wait behind password resets.

Outage Shield

Seven people at Acme Corp report the same problem. Your team can link the requests to one incident, record the fix, and close the related requests together.

Resolution memory

See how a similar problem was fixed last time at this company, and the written procedure that applies, before anyone starts guessing.

Changes with a way back

A change cannot ask for approval until it says how to do it, how to check it, and how to undo it. Undoing a change is a normal outcome, not a failure.

Timesheets with a full history

Changing a time entry needs a reason, and the old value is kept. Billing only uses weeks that a person approved.

Agreements to invoices

Prepaid hours, rates, and billing increments per customer. Approved time becomes a draft invoice, and a second person reviews it before it is posted.

Works with FlowRMM

Keep the computer work with the support request.

FlowRMM lets your team connect to computers and do the work. When a technician uses it, the remote session and approved actions show up on the support request in FlowPSA, so nobody has to copy notes between tools.

No duplicate requests
If FlowRMM sends the same alert twice, you still get one request. Each message carries an event ID.
Optional
FlowRMM works the same with FlowPSA turned off. Teams using only FlowRMM never see a FlowPSA charge.
One computer count
Billing uses the enrolled computer count FlowRMM already reports.
Separate permissions
Being an admin in FlowRMM does not make someone an admin in FlowPSA. Each app has its own Microsoft Entra roles.

How FlowPSA and FlowRMM fit

FlowRMM

schema public

Connects your team to computers

Endpoints and inventory
Remote Console sessions
Approved actions + verify
Endpoint MCP

FlowPSA

schema flowpsa

Organizes requests, time, and billing

Tickets, tasks, changes
Time and timesheets
Agreements and SLAs
Draft invoices + PSA MCP

One Postgres

tenant_idclient_idsite_iddevice_id

The same customer, site, and computer records in both apps. No nightly copying, no mapping spreadsheet.

Technical detail: FlowPSA keeps its data in its own section (schema) of the same Postgres database FlowRMM uses, with the same customer, site, and device IDs. There is no mapping table and no nightly sync.

Pilot in development

A fix should come with a fresh check.

We are building a small workflow for IT support teams: review a proposed fix, get approval, and check what changed. Initial work uses simulated cases.

Planned test workflow

Start with one request
Choose the problem, test computer, allowed action, and success check before work starts.
A person approves the action
The pilot is designed to run only the agreed action after a person approves it.
Check the computer again
A fresh check should show whether the expected change happened. A command finishing is only part of the story.
Leave evidence or ask for help
The goal is a clear record of what ran and what the check found. If the result is unclear, a technician takes over.

In the current products, FlowRMM supports remote access and recorded actions, and FlowPSA organizes support work. This end-to-end pilot is still under development. Customer results and release availability are not established yet. An end-to-end repair on a test computer has not been demonstrated yet.

Help shape the pilot

Bring one recurring support problem.

Run an IT support company (MSP)? We are looking for operators to help shape this workflow around real support work.

Start with one type of ticket your team handles repeatedly. Together, we can define a supervised test: what action is allowed, who approves it, what a fresh check must show, and when a technician takes over.

The first conversation is about fit and test scope. The pilot is still in development; live testing would be agreed separately.

See a walkthrough

Pricing

Pricing based on managed computers.

FlowPSA is an optional add-on to FlowRMM Business, billed on the same count of enrolled computers (endpoints). Hiring people or adding AI agents does not raise the price.

FlowRMM Business + FlowPSA

$1.50/endpoint/mo

100-endpoint minimum, so it starts at $150/month. All FlowPSA modules.

That is FlowRMM Business at $1 (from $100/mo) plus the FlowPSA add-on at $0.50 on the same count. FlowPSA is not sold without FlowRMM.

✓ Never billed: technician seats, including part-time and after-hours
✓ Never billed: mCP agent accounts (your AI vendor bills its own usage)
✓ Never billed: client portal users
✓ Never billed: a paid “AI” add-on from FlowDevs

Full pricing and examples

Enrolled computers250

Billed on your enrolled count. The minimum is 100 endpoints. Adding technicians or AI agents does not change this price.

FlowRMM Business (required base)

250 billed endpoints × $1

$250/mo

FlowPSA add-on (optional)

Same 250 endpoints × $0.50

$125/mo

Estimated combined total

$375/mo

Estimate only, not a bill or quote. Estimates assume the same enrolled count for the whole month. FlowRMM bills enrolled endpoint-months, so computers enrolled for part of a month are prorated.

Honest scope

What is not in the product yet.

FlowPSA already handles the daily work: requests, assignments, changes, projects, time, agreements, and draft invoices. These are planned next. We will not label them as available before they are.

Quotes and sales orders
Opportunity to quote to sales order to contract, without making sales the home screen.
Recurring invoices
Contract-driven recurring lines alongside time-based drafts.
Stock and purchase orders
Serialized and bulk stock, POs, and supplier records.
E-sign
A connector for quote and change sign-off.
License and seat reconciliation
Held back until contracted quantities are stored durably. We will not invent true-ups from inventory counts.
Project Gantt
A timeline view over the task graph that already exists.

How FlowPSA compares to HaloPSA, ConnectWise, and Autotask

FAQ

Common questions.

Request access

Request access to FlowPSA.

Tell us about your team. We will follow up and show you a real support request on a real computer, not a slide deck.

Self-serve by default. Set it up next to FlowRMM with the guides. Hands-on setup help is optional, never required to get a licence.
A published price. FlowPSA adds $0.50 per endpoint to FlowRMM Business, for $1.50 combined, from $150/mo. No quote call, no per-user count, no onboarding fee.
A direct line. Your feedback shapes quotes, stock, and recurring billing as they ship.