Architecture
GeoDoctor runs inside your network
GeoDoctor installs on a server you own and run. There is no cloud component in the validation path, so trusting us with your spatial data is not something you have to do.
Your data stays on your network
GeoDoctor installs on your own server. There is no cloud component in the validation path and no telemetry by default. The only outbound call is optional licence activation, which can be done offline.
Offline-first licensing
Licences are signed files bound to a hardware fingerprint. A disconnected installation keeps working for the whole of its grace period, so an isolated site never needs to reach us.
Tamper-evident audit trail
Every sign-in, permission change, validation, export and administrative action is recorded with the actor, target, outcome and source address, in a tamper-evident audit trail: each entry is chained to the one before, so an edit or a deletion shows.
Enterprise identity
Single sign-on with your identity provider (OIDC), including its multi-factor authentication, configurable password policy, account lockout and remote session revocation.
Least-privilege access
Granular permissions grouped into roles and scoped per organisation, so nobody needs an administrator account to do an analyst's job. Cross-organisation access is denied by default and enforced centrally rather than rechecked at every endpoint and missed at one of them.
Retention you control
Configurable automatic deletion for audit logs, validation runs, reports and uploaded data, so retention matches your obligation rather than your disk.
Access by role
Privilege is granular rather than binary: role-based access, scoped per organisation. Cross-organisation access is denied by default and enforced centrally, rather than rechecked at every endpoint and missed at one of them.
Installed on your infrastructure
One installer bundles the runtime, the database and the application. There is nothing else to procure, nothing to install first, and no database to be licensed separately.
What the server needs
| Component | Minimum | Recommended |
|---|---|---|
| Operating system | Windows 10 or 11, 64-bit | Windows Server 2022 |
| CPU | 4 cores | 8–16 cores |
| Memory | 16 GB | 32–64 GB |
| Storage | 2 GB for GeoDoctor, plus your data and its results | 500 GB SSD for large datasets |
| Database | Bundled PostgreSQL and PostGIS, on this machine only | Bundled |
| Ports | 7007 (GeoDoctor) and 5433 (its database) | Either changeable in the installer |
| Client | A current browser | Nothing to install |
Tell it which hostnames to answer on
A request carrying a host header GeoDoctor does not recognise is rejected rather than redirected. If the installation will be reached by an IP address, by another DNS name, or through a reverse proxy, add those hostnames to its allowed-hosts setting during installation — before your users connect.
What we do not have
A reviewer trusts a document that admits a gap far more than one that does not, so here are ours.
- No SOC 2 report.
- No ISO 27001 certification.
- No published third-party penetration test.
- No bug bounty programme.
What we offer instead
- An architecture that removes the need to trust us with the data in the first place.
- Completed security questionnaires and architecture documentation on request.
- Your own security team is welcome to review the installed software.
Reporting a vulnerability
Email [email protected]. We acknowledge within one business day. We will not pursue researchers acting in good faith, and we will tell you when a fix ships. There is no bounty programme, and we will not pretend otherwise.
Is there a cloud version?
How does licensing work?
What if the server hardware changes?
Can it run with no internet access at all?
What does installation involve?
See it for yourself
Install it on a server you control and point it at your own data. That tells you more than any document we could send.