Skip to main content

Libera Suite

A desktop office suite you can own. Libera Suite opens the documents other people send you (.docx, .xlsx, .pptx, ODF), edits them on your machine and saves them back. It runs on your own computer, with no account to create and nothing in it that phones home.

Four editors share one application. The file picks the editor, so there is nothing to choose.

Libera Words .docx .odt .rtf .txt .md
Libera Tables .xlsx .ods .csv
Libera Slides .pptx .odp
Libera Diagrams opens .vsdx to read

Libera Words, with a document open: the editor's toolbar in the Libera Words purple, and a laid-out page below it.

Abilian builds the host as free software under the Apache License 2.0. The editors inside it come from Euro-Office (itself an AGPL fork of ONLYOFFICE by Ascensio System SIA), running locally, with the document engine unmodified: our patch queue against them is build configuration and branding.

Using it

libera report.docx        # a window, in Words, because the file says so
libera budget.xlsx        # Tables
libera *.pptx             # one window each
libera                    # the start window: new, open, recent

The start window, with a New tile for each of Document, Spreadsheet and Presentation, an Open button, and a Recent list of three documents.

What works today sets out the full list with its gaps. It covers editing, saving and exporting, with PDF in the Save As popup. It also covers blank documents of all four kinds, images, printing, spell check in six languages, crash recovery and a Recent list.

libera -v FILE            # what it is doing; -vv how; -vvv every request
libera --diagnose         # everything worth pasting into a bug report
libera --payload-status   # which editors are in use, and the revisions they were built from

How it works

The editors are a web application. Everything they cannot do in a browser (read a file from disk, convert it, save it, list the fonts, put a dialog on screen) they ask of one injected JavaScript object, window.AscDesktopEditor, which the host exists to answer.

We implement it in Python, behind the webview your system already ships. The host serves the editor over a loopback HTTP server and defines AscDesktopEditor before the editor's own code runs, so nothing about the editor itself changes.

The payload The editors: sdkjs, web-apps, the x2t converter, fonts, dictionaries. Built from upstream sources pinned by SHA, plus our patch queue. ~120 MB, installed out of tree or shipped inside the bundle.
The host src/libera/: the loopback HTTP server, the webview, the file dialogs, the menu bar and the converter calls, in about 4,700 lines of Python across 32 modules. All of the desktop application is here.
The bridge Three small JavaScript files, spliced into the <head> of every page the host serves. Our code and theirs never share a file.

Five thousand lines is a codebase a small team can read in an afternoon and still be maintaining in ten years.

We do not fork the engine. The patch queue is 28 patches across three upstream repositories: 24 of them make it build on macOS, 3 are configuration and branding, 1 fixes an upstream UI bug. None touches the editing engine, so following upstream means rebasing build configuration. Every release records the exact revisions it was built from, so the corresponding source is a commit plus a series that provably reapplies to it, and make patches checks that it still does.

Everything we ship, we build. build/ compiles the editors and the native converter from pinned upstream sources, including on macOS, where upstream publishes no binaries of its own.

Where it stands

Early, and running. All four editors work today on Windows 10 and 11 (x64), Linux (x86_64 and arm64) and macOS (Apple Silicon).

Tabs, file locking, and signing and notarisation on macOS are still to come. Linux has a menu bar and a launcher entry; neither has keyboard shortcuts, because pywebview's GTK menu has no way to attach them. What works today lists the known issues, so an evening spent reporting one is an evening wasted. The roadmap says what comes next and what we have decided against.

The most useful thing you can send us 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 (a font we did not ship, a resource we failed to serve) than the engine.

Installing it

Install gives the full instructions for each platform. Four ways in; the first works on both.

One command, no root. It picks the channel that suits the machine:

curl -fsSL https://cdn.abilian.com/libera/install.sh | sh

Homebrew, on Linux and macOS alike:

brew install abilian/tap/libera
libera --payload-install

Linux: the Flatpak. The bundle includes the editors, GTK and WebKit, so there is nothing else to fetch and nothing to get wrong:

arch=amd64     # or arm64
ver=$(curl -fsSL https://cdn.abilian.com/libera/bundles/latest)
curl -fLO "https://cdn.abilian.com/libera/bundles/libera-$ver-$arch.flatpak"
flatpak install --user "./libera-$ver-$arch.flatpak"
flatpak run eu.liberasuite.Libera

From PyPI, where the libera command fetches the editors on first run:

pipx install --system-site-packages libera        # Linux: the flag is not optional
uv tool install libera                            # macOS
libera --payload-install

Linux works on both architectures. Payload 0.2 is built on Ubuntu 22.04, so the converter needs glibc 2.34 and GLIBCXX 3.4.26: Ubuntu 22.04, Debian 12 and anything newer, measured in a clean container of each. The Flatpak needs none of that, since the editors inside it run against the GNOME runtime.

macOS is Apple Silicon, on macOS 14 or later. There is no Intel build.

Building it

git clone https://github.com/abilian/libera-suite && cd libera-suite
uv sync
make payload-all                 # fetch, patch, build, assemble, smoke-test (long: V8 alone is ~30 min)
export LIBERA_PAYLOAD="$BUILD_ROOT/out/payload"
uv run libera document.docx
make verify      # everything below, in the order that fails fastest
make test        # unit, the host over HTTP, the editor in headless Chromium
make lint        # ruff, ty, pyrefly, mypy, biome — green, and expected to stay that way
make smoke       # the converter: fonts, docx -> odt -> docx, docx -> pdf
make patches     # does the patch queue still apply to the pinned SHAs?

The test suite enforces one house rule: assert on content, never on exit codes. A converter that writes an empty document exits zero. A PDF with no glyphs in it is the right size. So the end-to-end run photographs the editor's own canvas and measures the ink on it.

docs/ The documentation site, published at https://docs.liberasuite.eu/. Start at Developers.
notes/ Where the reasoning lives: vision, specs, architecture, packaging, our relationship with upstream, the bugs that escaped to a user, a survey of how Euro-Office is put together. It stays in the development repository.
build/ Building the editors and the native binaries from pinned source plus our patches.
CLAUDE.md The orientation an agent gets, which happens to be the fastest one for a human too.

The package and the command are libera. The repository directory is local-office.

Credit

Libera Suite includes components from Euro-Office, itself a fork of ONLYOFFICE by Ascensio System SIA. Those components are AGPL v3 and are modified. The same line appears in Help ▸ About inside the application, in the editor's own About panel, and in what a software centre shows for the Flatpak.

The editors, the document engine and the format support are theirs. That is the hard part: twenty years of correctly reading a .docx written by somebody else's software. The host, the packaging and the desktop integration are ours. We are grateful for both.

Licence

Libera Suite ships as two artifacts under different licences.

The host is Apache-2.0: everything in src/libera/, which is the whole of this package.

The editor payload is AGPL-3.0: Euro-Office plus our patch queue against it (GUI assets are CC-BY-SA-4.0). It arrives as a separate download or inside a Flatpak, never vendored into the wheel.

Licence and attribution has the corresponding-source detail: what each release records, and where to fetch it.

Metadata

Release files for libera 0.3.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for libera 0.3.1
File Size Uploaded Provenance Actions
libera-0.3.1.tar.gz 117.4 kB Without provenance Details for libera-0.3.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for libera 0.3.1
File Interpreter ABI Platform Actions
libera-0.3.1-py3-none-any.whl Python 3 none any Details for libera-0.3.1-py3-none-any.whl

Total release size: 256.7 kB

Release files / libera-0.3.1.tar.gz

Download URL libera-0.3.1.tar.gz
Size 117.4 kB
Tags Source
SHA-256 checksum
How to use checksums
d60dcb450b62556d82f6d0c10c83dce77b9dc0df7756deba13fbb0f9a4be418e
BLAKE2b-256 checksum
How to use checksums
535ee79762eedd8cab91ee995615fae0656e74196ac7ee7ed857c95958cad758
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.12 {"installer":{"name":"uv","version":"0.12.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / libera-0.3.1-py3-none-any.whl

Download URL libera-0.3.1-py3-none-any.whl
Size 139.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d1c54eca3f9439017da5eae76cdc726243f20fc6c453ddf48702ef067d3b193e
BLAKE2b-256 checksum
How to use checksums
eb058d2258afe27e6f9aed2880750609aebdef194a1fd7ce4ee96e9a48f73023
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.12 {"installer":{"name":"uv","version":"0.12.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for libera 0.3.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page