Security and data control
Where your data lives, how the product protects it, and how to report a problem.
Your data stays on your server
Tagaris is self-hosted. The register lives in your own PostgreSQL database on hardware you control, and the app sends no telemetry and no analytics. Given the database superuser, as in the standard install, the app moves to a limited role of its own on first start. The one outbound call it makes by default is a daily check for a newer version, which sends the version number, a random install identifier and the month the server was set up and can be switched off; anything else, such as release-note emails or feedback, you opt into. Licence keys are verified offline apart from the activation and renewal checks described in Licensing, and air-gapped installs can use a licence file with no internet at all.
Nothing is locked in. Full CSV and JSON export is available on every tier, and a whole-organisation export is built into Settings.
Access and authentication
Sign-in is email and password with optional two-factor authentication (an authenticator app, an emailed code, or backup codes). One policy for the whole install can require two-factor for administrators or for everyone. OpenID Connect single sign-on with Microsoft Entra ID, Okta, Google Workspace or any other provider is also available, with a policy that requires it for everyone except the application administrators, whose passwords are the break-glass way in. Both are on every plan. Each organisation can also have its own identity provider for its own staff, who are matched on the provider and their directory id, never by email address. PKCE is used with every provider, browser sign-on callbacks are bound to the state cookie, so a callback the browser did not start is refused, and a Google sign-in is checked against your allowed Workspace domain on every sign-in. The public account sign-up endpoint is closed: accounts are only created by the setup wizard and by accepting an invite.
Roles are Admin, Editor and View only, and view only means exactly that: look, search and nothing else, which is why view-only sign-ins are free and unlimited. Access groups give a person particular jobs (twelve permissions, such as recording audits or receiving deliveries) without making them an Editor, and a person can be limited to particular sites and to some areas of the register, hiding the rest from lists, search, reports, exports, the mobile app and their personal API key. Organisation users, such as a customer's own staff, see only their own organisation. Every action names the permission it needs and is enforced by a central least-privilege check on the server, in the browser, the mobile app and the API alike. The sign-in endpoints are rate limited.
Secrets and backups
Integration, mail and single sign-on credentials are encrypted at rest with AES-256-GCM, keyed from the install secret. Setup refuses a placeholder secret, and the secret can be replaced without entering the saved settings again. Scheduled backups are built into the product, with optional passphrase encryption, an in-app restore, and offsite copies to S3-compatible storage. The backups guide covers schedules, retention and restore tests.
The software supply chain
Release images are built for linux/amd64 and linux/arm64 and scanned for known vulnerabilities before each release. Dependency advisories are tracked and updated on a regular cadence. The deployment files are public at github.com/goodhall-solutions-ltd/tagaris.
Reporting a vulnerability
Email [email protected] with what you found, how to reproduce it and the impact you think it has. We aim to acknowledge within 3 working days and ask for reasonable time to fix before public disclosure. Please do not raise security issues in the public tracker.
Running it safely
- Set a strong, unique install secret and store a copy safely
- Serve the app over HTTPS behind a reverse proxy that terminates TLS
- Behind a proxy, set
TRUSTED_PROXIESso sign-in limits see each client's own address, and keep port 3000 off the internet - Keep the container image current; migrations run automatically
- Take the built-in backups, and test a restore while the stakes are low
- Keep the database unreachable from outside the Compose network, which is the default
Questions a security review will ask
The documentation covers deployment, upgrades, backups and the API in detail, and we answer security questionnaires by email.