Home / On-premises
On-Premises Redaction Software
Installed in your own data center, on your hardware and your network, and operated by you. The page below is written for whoever has to sign off on that, not for whoever is buying.
What Runs Where
The platform is a web application, a database, supporting services, and an AI processing tier. In an on-premises deployment all four sit inside your boundary.
The AI tier is the one that usually decides the conversation. The whole stack runs locally: language models through vLLM or Ollama, and local models for transcription, computer vision, OCR and PII detection. No content and no inference request leaves the deployment.
Infrastructure
Operating system
Windows Server; see system requirements for supported versions
Dependencies
Database, message broker, search index and storage are required infrastructure
Network
Ports and firewall rules are documented per service
GPU
AI processing requires GPU capacity; sizing follows throughput
TLS
Certificate provisioning is part of setup
Privileges
Installation requires administrative privileges
Licensing
Per-server activation; each application instance carries its own
High Availability
The web application runs across several servers behind a load balancer, with the database on availability groups holding replicas.
The web tier is the one that scales out. Other services run as single instances per deployment, which shapes the topology you design. Plan accordingly rather than assuming every tier scales horizontally.
Upgrades and Recovery
Rolling application upgrade and zero-downtime database upgrade are supported, alongside a documented rollback and downgrade policy. Backup and restore, and disaster recovery, are part of the deployment rather than an afterthought.
Silent installer deployment is available for automated provisioning, and telemetry exports through OpenTelemetry to whatever you already run.
FAQ
On-Premises Redaction Software questions, answered
Is a GPU required?
Yes, for AI processing. It is a requirement rather than an optimisation, and sizing follows the throughput you need.
What has to be provisioned first?
A database, a message broker, a search index and storage, with documented ports and firewall rules.
How is it installed?
Through a silent installer for automated provisioning, which needs administrative privileges on the host.
How is licensing handled without internet access?
Licensing is activated per server, one per application instance. Licence verification normally requires outbound access independently of AI processing, and it is disabled for disconnected deployments.
Can it be upgraded without downtime?
Rolling application upgrade and zero-downtime database upgrade are supported, alongside backup and restore, disaster recovery, and telemetry export through OpenTelemetry.
Send Us Your Architecture Review
We will answer it against this list rather than around it.