Insurance, energy, mobile, subscriptions, memberships: Omnipacto answers what a folder cannot. What does it all cost per month? Until when can we cancel? And which mobile contract did we have in 2022?
Omnipacto is not a file store. The contract is the master record; the paperwork hangs off it.
Five yearly invoices from one insurer are five different contracts. An archive sees five PDFs. Omnipacto keeps each contract with its numbers, term, price and documents by role: policy, terms, amendment, price change, invoice.
From minimum term, renewal and notice period Omnipacto computes the last day to cancel. The deadlines page shows a traffic light; reminders arrive in time via ntfy, e-mail or webhook.
Prices are never overwritten, only added with a date. Switching providers becomes a chain of predecessor and successor. The 2023 price is still there later, and "what did we have back then?" has an answer.
All pictures show the demo household "Familie Beispiel", not real data. The interface is available in English as well.
Term and cancellation with the last day to cancel, price history, documents by role, contract numbers, holder and insured person.
Urgent, soon, relaxed. You set the thresholds. Reminders go out via ntfy, e-mail or webhook, configurable per person.
Contracts by person and by object: supplementary insurance for the kids, a mobile plan for everyone, and everything tied to the house: building, contents, electricity, gas, water, maintenance.
If you run Paperless-ngx, you attach documents straight from the archive. Paperless keeps the files, Omnipacto only reads. Without an archive you simply upload PDFs.
With a language model on your own network (Ollama) Omnipacto reads policies, terms and price changes and proposes values. Every value shows where it was found. Only what you confirm is applied.
Light or dark, five accent colours, compact or airy, font size, language. Every person sets it for themselves; the household sets defaults.
Several households per installation, several people per household with roles. Sign in locally or via OpenID Connect.
A server, a NAS or a mini PC with Docker is enough. PostgreSQL comes along. Paperless-ngx, Ollama and ntfy are optional.
git clone …/omnipacto # address follows with the first release
cd omnipacto
cp .env.example .env # generate a secret, point to your archive
docker compose up -d # http://your-server:8000On first visit you create your account and household. Backup is a pg_dump plus the file folder, nothing else. Stack: Python, FastAPI, PostgreSQL, React.
Yes, at demo.omnipacto.de. The account is pre-filled on the sign-in page. The demo shows the fictional Beispiel family and is reset every night. Password, members and notifications are locked there; everything else is yours to touch. The demo speaks German by default – switch the language under Settings.
No. Omnipacto has its own document store. If you run Paperless-ngx, you attach documents straight from the archive, which keeps the files. Other sources are planned through an adapter interface.
No. Omnipacto runs on your own device. There is no account with us, no telemetry, and no outbound connection you did not set up yourself.
Optional and local. An Ollama model on your network reads attached documents and proposes values, each with its source passage. Only what you confirm is applied. Without Ollama only this feature is missing.
The source code is licensed under the AGPL-3.0 and free to use. Companies that cannot meet the AGPL's terms can obtain a commercial license.
Yes. A household has several users with the roles owner, editor and viewer. One person can belong to several households, for example their own family and their parents.
It lives in a PostgreSQL database and a file folder on your device. Access only after sign-in, optionally via your existing identity provider through OpenID Connect. Document links are short-lived and bound to the household.
Copy the database dump and the file folder to the new device, carry over the configuration, start. No keys are tied to the machine.