OpenCatalogi
Make your data discoverable and reusable, beyond your organisation too. Publish once from your own , be found everywhere.
Publish once. Be found everywhere. Come down on time.
You publish from the records you already keep. Residents, journalists and other public bodies find it in one search. The national index picks it up. And every item knows when it has to go.
One search across every catalogue that joined.
Today: a resident looks for a zoning decision and visits three municipal websites. Instead: they search once and find your document and the neighbouring municipality's in the same list. Nobody built a shared database. Each organisation keeps its own catalogue on its own server, and the search reaches across them.
Change it once, and the public page changes with it.
Today: a date is corrected in the case system, and someone remembers to correct the website too. Or not. Instead: the public page reads the record itself. Correct the field once, and the public page shows the correction. No second edit, no two versions of the truth.
All seventeen Woo categories, in the format the national index reads.
The Woo, the Dutch open government act, names seventeen kinds of information every public body has to publish. Today: someone uploads to the national index by hand, again and again. Instead: publish here, and the national index picks it up in the format it requires. Each item already carries its retention date, so it comes down again on time.
Links that keep working.
A member of parliament cites your report in a written question. Two reorganisations later, the link still opens the same document. Every published item keeps its own permanent address, so citations, audit files and court records keep working.
Open, and yours to take with you.
Every item exports as plain, open files. Your reading room runs on the server you host, or your partner hosts for you. The day you leave is as easy as the day you started.
It works the way you work. And it works for you.
Four things you would normally pay extra for. Here they are built in.
The council decides on Tuesday. It is public on Wednesday, by itself.
Today: someone keeps a list of what has to go public when, and what has to come down when. Instead: you draw it once. Set the publication date, and the item goes public on the day. Set the retention term, and it comes down on the day, with a note of why. A publication whose term is about to end lands on the records officer's list before the date. A batch of two hundred documents cleared for publication? Published in one go, and every one of them logged. Nothing forgotten, no chasing, no coding.
How automation worksYour reading room, your fields, your look. Without a developer.
A province wants the water board on every dataset. A municipality wants a decision number on every decision. A ministry wants a page per theme, in its own house style. Add the field, add the page, build the menu, pick the theme. In the running app, in minutes, and your changes stay with every update.
How customising worksAsk for the document. Get the document.
Type "which permits did we publish about the harbour last year?" and get the list, with links that open. Ask "what does the retention on the traffic decisions say?" and get the answer, not a spreadsheet to build. The assistant reads the catalogue the way a resident does. It only reads, and you decide who may ask it.
Meet the assistantThe people you serve look it up themselves. Without a request form.
The catalogue is the public front door, and Portaliq is the personal one. Behind a login, residents and businesses see what applies to them: the requests they filed, the contracts they hold, the invoices they owe or paid. A quotation is asked for and signed in the same place. The counter is open in the evening too, and your inbox stays quiet.
See the client portalWe ship the widgets you need
Install it and the home screen shows what the public reads, what still waits to go out, and which items are about to reach their retention date. Want more? Design your own widgets with Buildiq, or build your own dashboard from all your data with LaunchPad.
Your files, your photos, your neighbours, the national index.
A publication is the document itself, the photos that go with it and the links that belong to it. They live in your Nextcloud. The catalogue makes them public, and passes them on.
A publication is not a form. It is the report itself, the map that goes with it, the photos of the site and the links to the underlying decisions. Drop them on the publication from Files, and they are the public download. Everyone downloads the same version you see. Update the file, and the public download is the new file.
Read the docsThree apps that make the catalogue more yours.
Shape the reading room, ask it questions, and put its numbers on your own dashboard.
Partners shipping OpenCatalogi
Implementation, hosting, and integration partners that deliver OpenCatalogi to their customers. Pick the partner you already work with, or one whose stack matches yours.
Ship Conduction to your customers.
Three tiers: Host (ship our apps), Service (SLA + third-line support), Certified (trained, joint roadmap, tender-eligible). The apps stay open source, the relationship stays direct.
Apply through Support →