SAYNIS GovSuite
A modular management information system for public bodies: records, workflow approvals and reporting in one place.
Public bodies rarely need a bespoke system built from nothing. They need the same core — records, roles, approvals, reporting — configured to their mandate.
GovSuite is being built as that core, delivered as modules a bureau can adopt one at a time, so a first deployment is a single department rather than an institution-wide programme.
It is not a replacement for a custom build where your process is genuinely distinctive. We will tell you which of the two you need.
What SAYNIS GovSuite is being built to do.
Configurable records
Record types defined per bureau without writing code.
Roles and permissions
Mapped to real organisational structure and delegation.
Approval workflows
Multi-step routing with delegation and escalation.
Case tracking
Correspondence and cases followed from receipt to closure.
Reporting views
By role, in the formats the bureau already submits.
Audit trail
Complete and queryable, for oversight and inspection.
Export
To existing reporting formats without re-entry.
Offline tolerance
Data entry designed to survive an unreliable office connection.
Four steps, end to end.
- W1Configure
Configure records and roles
The bureau's own record types and permission structure.
- W2Digitise
Digitise one process
A single department, in production, before the next.
- W3Route
Route approvals
Approvals move through the system rather than by phone.
- W4Report
Report from one source
Figures come from the record, not from reconciliation.
- On-premise or national cloud, at the institution's discretion.
- Regional bureaus and agency departments, adopted one at a time.
- Offices with intermittent power and bandwidth.
- Processes requiring documentation, quotations and audit provisions.
- Node.js and PostgreSQL, with a documented REST API.
- React and TypeScript, accessible on low-end devices.
- Docker, deployable without an internet connection.
- Audit logging, role-based access and backups from day one.
What people ask about SAYNIS GovSuite.
It is in development and we are not committing to a public date. We are looking for a small number of pilot bureaus, and we will be direct about what does and does not work yet.
Yes. On-premise deployment is a design requirement, not an option added later, because data residency is a real constraint for the institutions we build for.
GovSuite where the process is standard, a custom build where it is not. We would rather tell you a module fits badly than configure it into something nobody uses.
Yes. We supply formal quotations, security and architecture documentation, and company details, and can work through a local partner where regulations require one.
You do. Data, configuration and any code delivered to you remain your property, and there is no hosting arrangement you cannot leave.
Register interest as a pilot
Design partners get early access and direct influence over what we build. We can only take a few at a time, so we will tell you quickly either way.