Roadmap¶
This page says what we are doing next and what we have decided against. What works today is the companion page: it describes the present; this one describes the intent.
Nothing here has a date. The order is the commitment.
The goal, as a test¶
Libera Suite is meant to replace Microsoft Office. We read that as one test: an organisation of a few dozen people, on Windows and macOS, uninstalls Office and does not reinstall it within a month. Each release removes one reason it would. These are the reasons, roughly in the order such an organisation meets them:
- It cannot be installed without a security warning, or by an administrator onto many machines.
- It does not speak the users' language.
- A document from outside looks wrong.
- Something done daily is missing: tabs, a password-protected file, a signature, a PDF to fill in, a Visio diagram to edit.
- It is not clear who maintains it, or for how long.
Shipped: 0.7, PDF, passwords and signatures¶
0.7 shipped in November 2026, two steps towards parity with Euro-Office Desktop in one release, because both change the editors' components and are cheaper rebuilt and published once.
PDF, edited and filled in. A PDF opens in the PDF editor: comments, highlights, drawings, text edits and pages moved, added or removed, saved as an incremental update after the original's bytes, which are left as they were. Forms fill and save, a French Cerfa and the US IRS forms among those tried. A PDF that asks for a password opens and saves, still protected. Creating a form comes in 0.8.
Password-protected documents. A document protected by Word, LibreOffice or Libera Suite asks for its password, opens and saves protected. File ▸ Protect gives one, changes or removes it, for Word, Excel, PowerPoint, OpenDocument and PDF files. A save to a format that cannot keep a password asks first.
Digital signatures. Listing a document's signatures and whether each is valid, signing with a key file, and removing a signature, for Word, Excel and PowerPoint files.
The components install like any Python package. pip install libera installs the editors and the converter as two more packages, built from the pinned sources where no wheel exists, and nothing is downloaded on first start.
Signed Flatpak bundles. Each has an OpenPGP signature beside it. Signing on macOS and Windows moved to a later release, below.
Shipped: 0.5 and 0.6¶
0.5 shipped on 20 October 2026, with the interface in French, German, Italian and Spanish, the fonts installed on the machine, and an editor page that sends nothing off the machine on its own. 0.6 shipped on 26 October, the first release towards parity:
- Tabs on macOS. Documents open as tabs of one window when the system prefers tabs (System Settings ▸ Desktop & Dock), as in every Mac document application. The + at the end of the tab bar opens the start window as a tab, and a tab can be dragged out into a window of its own.
- One window per document on Linux and Windows. Neither toolkit gives us macOS's tabs, so the only way there would be several editors in one page. Measured on Linux, that saves about 15% of memory and costs the rest: the documents load one after another, a recalculation in one tab freezes all of them, and one crash closes them all. So Libera Suite keeps a window per document there, as LibreOffice and Microsoft Office do, and the system groups them.
- The interface in every language the editors speak, more than 40, with a test that loads Words, Tables and Slides in each. Our own part (the menus, the start window, the dialogs) follows language by language, each once someone who speaks it has read it. A spelling dictionary comes with each language.
- A fidelity harness: a corpus of 30 Word documents, printed twice by the same build, gives the same pixels on macOS and on Linux. References from Word and a score come in 0.8.
Now: parity with Euro-Office Desktop¶
Euro-Office publishes a desktop application of its own, built on the same editors as Libera Suite. Someone comparing the two should find nothing in it that is missing here, macros apart (see below). Every feature on this list exists upstream already, in the editors we ship or beside them, so the work is wiring each one to the host and testing it, not writing it. This is the order we do them in.
Tabs, every language, PDF and passwords are done, above.
Plugins, including the AI assistant, and creating forms, in 0.8. Upstream's plugin system, and the plugins it carries, AI assistant included, and its form creator, which makes the fillable PDF forms 0.7 fills in. The AI assistant is off until it is configured, and it talks only to a provider the user chooses, which may run on their own machine. What leaves your machine will say so beside everything else.
Documents on a Nextcloud, ownCloud or Seafile server, in 0.9, with the check that lets us say parity. As in Euro-Office Desktop, a window on the server's own editors: the documents stay on that server, and editing with other people is that server's work. It is off until the user adds a server, and a local document's window never reaches the network either way.
Installs without a warning. Three things still wait on accounts and keys, and each ships as soon as it is ready: signing and notarisation on macOS, where Gatekeeper's prompt is a poor first five minutes; a .flatpakref, then Flathub; and code signing on Windows, so SmartScreen stops warning about the installer.
Alongside¶
The host becomes a runtime. The package splits in two: a host that runs apps, and the editors as one app among others. Nothing changes for a user. It comes when a second app does, or earlier if the boundary between the Apache-licensed host and the AGPL editors has to be shown in the code.
Fidelity, measured. A document from outside that looks wrong is the third reason on the list. The editor is mature, so a wrong layout is more often our packaging (a font, a resource) than the engine. Only a measurement finds those: a corpus of test documents, reference PDFs exported from Word, a score per page, and a harness that gives the same pixels twice, which 0.6 has. The score then gates releases, and every document a user reports goes into the corpus.
Later, towards 1.0¶
One feature at a time, each measured before it is promised. Most exist in the editor already and are not wired up.
Editing diagrams. Diagrams opens .vsdx and shows it. The converter writes no Visio format, so this needs converter work first. Euro-Office Desktop does not edit diagrams either.
Mail merge. An upstream feature, not reachable today.
Macros, in VBA, JavaScript and Python. Macros are off today. The editor's own are JavaScript against its API, and run none of the VBA that an organisation's workbooks and documents carry, which is what someone coming from Microsoft Office means by macros. They come back in three languages: Excel's VBA, so the macros already in those files run; JavaScript, the editor's own; and Python. Euro-Office Desktop has the JavaScript macros, so until then this is the one feature it has that Libera Suite leaves out.
In-application help. Upstream's manual documents ONLYOFFICE and weighs 84 MB, so Libera Suite does not ship it. Help comes back when there is documentation of our own to point at; these pages are the substitute.
More fonts, particularly CJK. The shipped set is 7 MB and renders ordinary documents faithfully; the full set is 248 MB. Where the line goes is an open decision, and the fidelity corpus will say how many documents fall back.
Windows on ARM. It runs the x64 build under emulation today.
1.0¶
1.0 means the test above passes for one real organisation. On top of the features: signed installers on Windows and macOS, a deployment an administrator can script (an MSI or equivalent, a pkg, a system Flatpak), a published support window for each release, and a security contact. The fifth reason is answered by Abilian's commitment, written down where an organisation's procurement can find it.
Not now¶
These are outside the current product. Each could arrive one day, in the shape described here. None is being worked on.
A collaboration server of our own, and accounts. Libera Suite edits files on your disk, and opens the ones on a server you already use (see above). Running such a server is a separate product, which may reuse the host. Nothing in the local application waits on it.
Telemetry, analytics, crash reporting. There is none. Anything of the kind would be opt-in and off until you turn it on. What leaves your machine would list it beside everything else the application does on the network.
Forking the document engine. The patch queue makes upstream build on macOS and Windows, brands it, and fixes the converter, mostly for OpenDocument files. It also carries a few fixes to the editors themselves: missing fonts substituted the way Word does, Markdown headings kept through a save, the PDF editor able to open a PDF, and two cross-site scripting holes closed (see the patch queue). Each is one small patch that says what it is for, so following upstream means rebasing a short series, not maintaining a fork. A further change to the engine goes in the same way: one reviewable patch, offered upstream first.
How to influence this¶
The most useful thing you can send is a document that renders wrongly, attached. The layout engine is upstream's and mature, so where output is wrong it is far more likely to be our packaging than the engine: a missing font, a missing resource. Those are quick to fix and invisible to us until somebody sends one. Feedback says where to send it.