The rule is written once.The system applies it the same way, always.And everything is on the record.
Ciserex is an e-government system. Institutions use it to run their procedures — a session, an opinion, an appointment — from beginning to end: who took part, what was decided, when, and under which rule. Changing a rule is a request somebody approves, and it is written down. nine applications share one system, so what one of them records the others can find.
- Nineapplications on one system
- Onesingle sign-in for all of them
- Zeroservers for the institution to maintain
From beginning to end.
The nine applications do different work and all of them walk the same path. This is the path.
Whatever arrives comes in, however it arrives.
A letter by e-mail, a session being broadcast, a file somebody uploads, a news item. Each one ends up inside the system with its date and where it came from.
A person reviews. The machine prepares.
The artificial intelligence reads, classifies and proposes a draft. Whoever holds the task confirms it, corrects it or discards it, and what remains carries their name.
Approval follows the rule.
Quorum, majority, deadline and the chain of signatures come from the written procedure. The system applies them the same way every time and says which rule it used.
And everything is on the record.
Each step is noted with its time and with who took it, linked to the step before. Nothing is erased: a correction is made by adding, and the correction is on the record too.
Out comes a document that can be cited.
Minutes, an opinion, a report or a dashboard, with its version and its seal. Whoever receives it can check that it is the same one that was approved.
Nine applications. One system.
Each one handles different work and all of them read the same information. An institution uses the ones it needs and adds another when it needs one.
Available
Hemicycle
What Congress does with rights, session by session
Available
Harmoniser
Every norm against the charter, with tickets and approvals
Available
Org chart
Who works here, who they report to and what they may do
Available
Conflict meter
Where social conflict is growing and which rights it touches
Available
Library
The documents every app compares against
Available
Data
Every dataset in the organisation, in one place
Installed in parts. Opened by permission.
Each application brings its own list of permissions — read, review, approve, publish — and the institution decides which ones belong to each post. That is why two institutions can work on the same file while each sees what is theirs, and everything they do is signed with their name.
Data
Permissions it opens
Sign in once, with the account they already have.
Each person signs in with their Google account, on the computer and on the phone, and that same sign-in holds for every application.
One entry for each thing.
A person, a place, a date, a document: each exists once and every application reads the same one. When the Conflict meter saves a news item about a bill, that item appears on the bill's page the Hemicycle opens.
What is calculated and what is decided.
Some questions have one correct answer and some call for judgement. The system treats them differently, and the line between them is written into the procedure.
Two places it can run.
The system is the same in both. What changes is where the institution's data lives.
In the Ciserex cloud
The institution signs in and works. Keeping the system running is Ciserex's job.
In your own account
The system is installed in the institution's own cloud account, and the data does not leave it.
There are no servers to maintain.
The system needs no machines sitting switched on waiting for work: it answers when somebody uses it. The institution schedules no updates and announces no maintenance windows.
- It installs the same way every timeThe installation is written down step by step, so a new institution ends up like the last one.
- It can be rolled backEvery change to the installation keeps its date, its author and its reason, and the previous state can be restored.
- It can be checkedWhat the installation says and what is actually running are compared, and the difference is visible.
What the cloud provider certifies, and what the system proves.
The data centres, the network and the encryption are audited by Amazon, and those certifications are inherited. The rest — how a file is kept, who may see it, what is recorded — the system proves, and it proves it by checking at the moment you ask.
Certified by AWS
The infrastructure arrives certified. The reports are published by AWS and the customer obtains them with their own account.
- SOC 1, SOC 2 and SOC 3
- ISO/IEC 27001, 27017 and 27018
- PCI DSS Level 1
- Regions of the customer's choosing
Proven by the system
The Quality application keeps each control once, together with the check that proves it. Standards rest on that same catalogue, so two standards answer the same about one control.
- ISO 9001Quality management
- ISO/IEC 27001Information security
- ISO 15489Records management
- ISO/IEC 42001AI management
- GDPRPersonal data protection
- SOC 2Trust services criteria
Ciserex is not certified against these standards. Every requirement carries the check that proves it and the result of running that check at the moment somebody asks. A requirement no check reaches is marked “by hand”, says who must review it and what they must look at, and does not count as met.
The applications, one by one.
Each page describes the application, what it brings, the permissions it opens and the screens that are already published.