Roadmap
From alpha to a first release.
ServiceFlo 0.1.0a1 is out now as an alpha. Beta releases are targeted for late December 2026, and the first full release, 0.1.0, is planned for February 2027. This page says what each stage means and what is left to do.
Since November 2026You are here
Alpha
Everything is here to try. Screens and settings may still change from one alpha to the next.
- Tickets, queues, email in and out, routing rules and service targets
- Knowledge base, service catalog, request forms and a portal
- Problems, changes with approvals and a calendar, assets, contracts and licences
- Optional AI: triage, summaries, drafts and a help bot, on a model you choose
- Reports, an API, webhooks, and a connection for AI assistants
- One-command backup, restore and upgrade, with a backup taken before every upgrade
Targeted for late December 2026
Beta
The features are settled. From here on the work is testing, fixing and explaining.
- The guide finished: installing, the first hour as an administrator, connecting other tools
- Installs and upgrades tried on real servers, not only on our own
- An open source licence chosen and the code published
- Fixes for what people trying the alpha run into
Planned for February 2027
Release 0.1.0
The first release meant for everyday use by a real service desk.
- An upgrade path from every alpha and beta, tested before it ships
- Numbered releases after it, each with notes on what changed and what to do
- Fixes only between feature releases, so an upgrade is never a surprise
What an alpha means for you
Try it freely
Install it, load the demo data and look around. This is the best time to tell us what is missing or confusing.
Expect change
A screen or a setting may move before the release. Each alpha comes with notes on what changed.
Your data carries over
Upgrading keeps your tickets and files, and takes a backup first. Still, keep backups of your own until the release.
Dates are plans, not promises: if something is not ready, the release waits for it.
Get started