Enterprise • dedicated instance • agreed infrastructure

A private Safety Software instance
on your agreed infrastructure

We deploy a dedicated Safety Software environment for organisations that do not want to use the standard SaaS service. First, we assess the infrastructure, dependencies and maintenance responsibilities. Only after that pre-deployment assessment do we confirm the architecture, scope and price.

On-premises deployment is not simply a matter of copying an application onto a server.

A private instance demands clear decisions on the operating system, database, domain, encrypted connections, email, secrets, encryption keys, backups, monitoring and update process. If those responsibilities are not documented before work begins, the first outage quickly exposes the gap: who fixes the failure, and who restores the data?

That is why every deployment starts with a technical assessment. We establish whether the environment is suitable, which connections are required, who owns each component and how acceptance will be tested. The standard service does not include a fully internet-isolated environment, high availability or corporate single sign-on (SSO).

A dedicated environment with responsibilities defined from day one

What the agreed private deployment includes

Architecture record
We document the environment, dependencies, data flows, owners and maintenance responsibilities.
Environment readiness assessment
We verify the compatibility of the server, database, network and services required to run the application.
Private instance installation
We deploy the agreed version of Safety Software in a separate, approved environment.
Dependency configuration
We configure the database, domain, encrypted connection, email, secrets and key management strictly within the agreed scope.
Testing and acceptance record
We test start-up, migrations, the diagnostics panel and the agreed user scenarios.
Operational documentation
We provide the agreed procedures for updates, faulty-update rollback, escalation and backups covered by the contract.

How we deliver a private Safety Software instance

1

Pre-deployment assessment

We gather IT requirements, environment parameters, expected integrations and organisational constraints.

2

Architecture and responsibilities

We confirm the solution, connections, dependencies and ownership of the server, data, backups and monitoring.

3

Installation and configuration

We deploy the application, database, migrations and agreed supporting services in the prepared environment.

Acceptance and handover

We complete the tests, review the results and hand the documentation to the people responsible for ongoing maintenance.

A private instance does not automatically include every Enterprise option

After the pre-deployment assessment, we document what is standard, what remains the client's responsibility and which capabilities require separate pricing.

What the service includes
What the service does not include
Environment
A dedicated instance on compatible, approved infrastructure.
Supply of hardware or an operating system, or server administration, unless expressly included in the contract.
Network connections
Configuration of the required connections and restrictions agreed during the pre-deployment assessment.
A fully offline environment or one isolated from all other networks as part of the standard service.
Availability and recovery
Basic testing plus an agreed backup and recovery plan within the defined scope.
High availability, clustering, automatic disaster recovery or guaranteed service parameters without a separate project.
Authentication and integrations
Standard accounts, roles and configuration available within Safety Software.
Corporate single sign-on (SSO), user directories, custom APIs or integrations not listed in the proposal.
Maintenance
Documented update, faulty-update rollback and escalation procedures, plus the support specified in the contract.
Unlimited 24/7 maintenance or responsibility for the client's entire infrastructure.

Frequently asked questions about on-premises deployment

Where can a private Safety Software instance be hosted?
It can run on compatible infrastructure operated by the client or a nominated provider. We confirm the specific environment, parameters and responsibilities during the pre-deployment assessment.
Can an on-premises deployment operate without internet access?
That is not a standard assumption. The application and its features may rely on external services. An offline deployment requires a separate dependency assessment and quotation.
Does the standard service include high availability and automatic disaster recovery?
No. The standard service covers one agreed instance and acceptance testing. Clustering, automatic failover and advanced recovery require a separate project.
Can corporate single sign-on (SSO) be integrated?
Corporate single sign-on is not part of the standard deployment. We assess integration with the identity provider once we understand the client's protocol, policies and environment.
Who is responsible for updates, backups and monitoring?
We document the division of responsibilities before deployment. Tasks may be handled by the client, its infrastructure provider or the Safety Software team, but only within the scope defined in the contract.

Start your private deployment with the architecture—not by copying files.

During the initial discussion, we will review your IT requirements, data location and preferred maintenance model. After the pre-deployment assessment, we will confirm the scope and price.

Discuss a private deployment

On-premises deployment is available through a tailored Enterprise proposal following an assessment of the environment and dependencies.

Practical articles on risk assessment, requirements and documentation — useful context for your team.