ServiceFlo

Open source Free forever

The service desk that fits just right.

Real ITSM for mid-sized organisations: tickets, a knowledge base, a service catalog, changes, assets and AI that can run on your own hardware. Without the enterprise price tag, or the enterprise headache.

Service, in flow.

The right size

Not too little. Not too much.

Most service desks make you choose: a shared inbox you outgrow in a year, or an enterprise suite that takes months to roll out. ServiceFlo is built for the organisations in between.

Why it exists

Built by people who have run the help desk.

ServiceFlo comes out of a decade spent managing a help desk on an old ticketing tool. Getting it to behave the way the team needed meant hacks, workarounds and knowing which of its quirks to lean on.

ServiceFlo was born from that frustration, and from the belief that there had to be a better way: a service desk that fits how the work is really done, and stays out of the way while you do it.

  • Low friction

    The common jobs take the fewest clicks. Nobody should need a trick to do their work.

  • Real value

    Each feature is there because a working help desk needed it.

  • No fluff

    If it only looks good in a sales demo, it is not in the product.

Features

Everything a service desk needs. Nothing it doesn't.

These are real screens from a ServiceFlo demo site, filled with sample data for a made-up university.

Tickets

The whole story of a request, on one page.

Email, forms and the portal all land in queues you design. Each ticket shows the conversation, the person, the service it touches and the clock it is on.

  • Queues and routing rules you set up yourself
  • Clear “respond by” and “resolve by” times on every ticket
  • Matching guides and similar solved tickets right beside it

Self-service

Answers people can find on their own.

A knowledge base and a service catalog give people somewhere to look before they write in, and a proper form to fill in when they do.

  • Guides sorted into categories, with search
  • A request form for each service, with approvals where needed
  • A status page for the days something is down

Changes, problems and assets

See what a change will touch before you make it.

Plan work on a shared calendar, trace repeat tickets back to one cause, and know what you own and what depends on it.

  • A change calendar that warns when two changes clash
  • Problems that gather their tickets and publish a workaround
  • Assets tied to their tickets, contracts and licences

Asset map

Know what depends on what.

Every asset and service can show what it relies on and what relies on it. When a print server has trouble, you can see at a glance which printers and services go with it.

  • Different kinds of link, each drawn in its own colour
  • An asset that is not working stands out on the map
  • Open tickets and changes counted on every box

AI, on your terms

AI that helps, and can stay in the building.

Sort new tickets as they arrive, catch up on a long one, draft a reply or translate a message. Point it at a model running on your own hardware, or leave it switched off: everything else works without it.

  • Triage for new tickets: it suggests the problem type, team and priority, and an agent decides
  • A summary of what has happened so far, in seconds
  • Drafts for replies, handover notes and “what fixed it”
  • A help bot that answers from your own guides and shows its sources

Reports

Numbers you can act on.

See how much work is coming in, how fast it is answered and where it gets stuck, without exporting anything to a spreadsheet first.

  • Volume, backlog, response and resolution times
  • Service targets met, and the reasons for the ones missed
  • Satisfaction, time and cost by team

Connect it

Fits in with the tools you already run.

A service desk is rarely alone. ServiceFlo can take work in from other systems, tell them what happened, and wait for a yes from the right person. It also works with Microsoft Teams and Power Automate.

An API for the everyday jobs

Anything that can send a web request can open a ticket: a monitoring tool, an HR system, a script of your own.

  • Open tickets, reply, assign, change the status and import assets
  • Each key acts as one person, so it sees only what that person may see
  • Built-in pages that list every call and let you try it

Webhooks that tell your other tools

A webhook is a message ServiceFlo sends to an address you choose, the moment something happens.

  • Choose the events: created, replied, assigned, status changed, moved
  • Or send one from a routing rule, only when its conditions match
  • Every message is signed, and every delivery is logged

Approvals before the work starts

Some requests need a yes first. ServiceFlo asks the right people, reminds them and keeps the answer on the record.

  • Ask one person, several, or a saved group such as a change board
  • Everyone must agree, any one is enough, or a set number of yes votes
  • A catalog service can ask the requester's manager on its own

What's in the box

All of it. In one install.

28 parts, one product. There are no add-ons to buy and no editions to compare: switch on the modules you need and leave the rest off.

Service desk

  • Tickets and queueswith filters you build yourself
  • Email in and outreplies thread onto the ticket
  • Routing rulessend work to the right team
  • AI triagesuggests type, team and priority (optional AI)
  • Service targetsrespond-by and resolve-by clocks
  • Approvalsfor requests and changes
  • Tasks and checklistswith reusable templates
  • Satisfaction surveysa rating after the fix

Self-service

  • Portalpeople follow their own tickets
  • Knowledge baseguides, categories and search
  • Service catalogwhat you offer and how to get it
  • Request formsone per service, with your fields
  • Status pageservice alerts and maintenance
  • Help botanswers from your guides (optional AI)

Service management

  • Problemsknown errors and workarounds
  • Changestemplates, approvals and reviews
  • Change calendarwith clash warnings
  • Major incidentsone update reaches everyone affected
  • Assetstypes, fields and a dependency map
  • Contracts and licencesrenewal warnings and seat counts
  • Supplierswho you buy from, in one list

Platform

  • WorkspacesIT, HR or any team, side by side
  • Custom fields and statusesset up in Settings, no code
  • Directory lookuppeople from Active Directory or LDAP
  • Reportsdashboards, exports and scheduled email
  • API and webhooksplus Teams and Power Automate
  • Data feedsfor Power BI and AI assistants
  • Your brandinglogo, colours, light and dark themes

Open source

Free to use. Yours to run.

ServiceFlo is open source software, under the AGPL 3.0 licence. There is no sales call and no trial clock: download it, start it and see if it fits.

Free, with nothing held back
No price per agent, no paid tiers, no features locked behind an upgrade. Add your whole team.
No renewal, no hostage negotiation
Single sign-on, approvals, the audit trail and the API are all in the free download. Nothing expires, so there is no renewal where the price jumps once your team depends on it.
Your server, your data
One Docker image runs the whole system on a single host you control. Tickets and files stay with you.
Open to read and to change
Every line of the code is public. Check how it works, fix what bothers you, share what you build.
View the code
# 1. Get the code
$ git clone <repository> serviceflo
$ cd serviceflo

# 2. Set your host name and keys
$ cp .env.example .env

# 3. Build and start everything
$ make prod-up
✓ web  ✓ worker  ✓ timers  ✓ mail
✓ postgres  ✓ redis
Three steps on any Linux host with Docker.

Questions

Fair questions, straight answers.

Is it really free?

Yes. ServiceFlo is open source, with no price per agent and no paid edition. The only cost is the server you run it on and the time to set it up.

What happens at renewal time?

Nothing, because there is no renewal. With a licensed suite, the yearly renewal can feel like a hostage negotiation: your tickets, your history and your team's habits are inside the product, so you pay what is asked. ServiceFlo has no contract to renew and no licence key that runs out. The features an enterprise needs, such as single sign-on, approvals and an audit trail, are part of the free download. Your data sits in a standard PostgreSQL database on your own server, so you can leave whenever you like.

Who is it for?

Mid-sized organisations that have outgrown a shared inbox but do not want an enterprise suite: universities, schools, councils, charities, companies. If a team of a few dozen people answers requests for a few thousand, it should fit well.

What do I need to run it?

One Linux host with Docker. The database, the cache and every background job come in the same set-up, so there is nothing else to install. A laptop is enough for a trial.

Is it only for IT?

No. Each team gets its own workspace with its own queues, forms, fields and knowledge base. IT and HR can work side by side without seeing each other's tickets, and so can facilities, finance or any team that answers requests.

Do I have to use the AI features?

No. AI is off until you switch it on, and everything else works without it. When you do want it, you choose the model: one running on your own hardware through Ollama, or a hosted provider.

Where does our data live?

On your server. Tickets, files and guides stay in your own database and storage. Nothing is sent anywhere unless you connect an outside service yourself, such as a mail server or a hosted AI model.

Can it use our staff directory?

Yes. ServiceFlo can copy people, departments and affiliations from Active Directory or another LDAP directory, keep them up to date on a schedule, and let people sign in with their directory password.

Can we make it our own?

Yes. Statuses, categories, custom fields, forms, routing rules, your logo and your colours are all set up in Settings, with no code. And because the code is open, you can change anything else too.

See if it fits.

It is free and it runs on one server, so trying ServiceFlo costs an afternoon, not a budget request.