Cloud SaaS
The fastest start: a managed, multi-tenant service where we run the web and worker processes, PostgreSQL and file storage for you. Sign in and begin — upgrades and backups are part of the service.
Deployment
Run it your way — our cloud, your Linux, or Windows Server
The same product everywhere: our managed multi-tenant cloud, a Docker Compose bundle on your Linux servers, or Windows Server with or without Docker. One codebase, one artifact — on-prem is simply a single-workspace instance of the same code.
One codebase, three deployment modelsDocker Compose bundleNative Windows services optionAir-gap ready
Three models, one product
Pick where it runs — not what you get
Every model runs the same web and worker processes on PostgreSQL with a file-storage location. The features never change; only the infrastructure does.
On-prem Linux
A Docker Compose bundle — web, worker, PostgreSQL and an optional TLS reverse proxy — with named volumes for database and files and a single .env for configuration. Upgrades are a pull and restart, and the upgrade script takes an automatic pre-upgrade database dump first.
Windows Server
Run the same Compose bundle with Docker on Windows — or take the native path: web and worker installed as Windows services, PostgreSQL for Windows, file storage on an NTFS path and an optional TLS proxy service. No Docker required.
Compare
The three models at a glance
Same product, same version, same features — here is what actually differs between them.
| At a glance | Cloud | On-prem Linux | Windows Server |
|---|---|---|---|
| Infrastructure | Managed by us — multi-tenant service | Your servers — Docker Compose: web, worker, PostgreSQL | Docker on Windows, or native Windows services with PostgreSQL for Windows |
| Installation | None — sign in and start | One Compose bundle, named volumes, a single .env | The same Compose bundle, or a scripted native installer |
| Upgrades | Continuous, handled for you | Pull and restart — automatic pre-upgrade database dump, then automatic migrations | Same flow via Docker or the installer, with the same automatic pre-upgrade backup |
| File storage | Managed object storage | Named volume, local filesystem, or any S3-compatible store | NTFS path, or any S3-compatible store |
| Email delivery | Handled by the platform | Your SMTP relay | Your SMTP relay |
| License & activation | Subscription entitlements per workspace | Ed25519-signed license file, verified fully offline | Ed25519-signed license file, verified fully offline |
| Best for | Teams that want zero ops and the fastest start | Data sovereignty, hardened and air-gapped networks | Windows-standard IT estates — with or without Docker |
One platform version covers the core and every module across all three models — modules unlock by license, not by separate builds.
Air gap & data sovereignty
Built to run where the internet doesn't reach
UniSentinel is engineered for networks that never touch the internet — and for teams that must always be able to walk away with their data.
- Container images load from tarballs — no external registry access needed.
- Licenses are Ed25519-signed files verified offline against a public key baked into the build — no activation server, no call home.
- Zero outbound connections required, and no telemetry by default — error reporting is strictly opt-in.
- Backup and restore are documented: database dumps plus file-storage snapshots, with an automatic dump before every upgrade.
- A full workspace export — a JSON/CSV bundle of your data — keeps you portable on any day. No lock-in, ever.
- If a license expires, a grace period and then read-only mode follow — your data is never locked away.
Container images loaded from tarballLoaded
License file verified offlineEd25519Valid
Pre-upgrade database dumpSaved
Migrations applied, forward-onlyCurrent
Health endpoints/healthz · /readyzHealthy
Outbound connections requiredZero
How it works
From download to upgraded in four steps
The same documented flow on Linux and Windows Server — predictable enough to hand to any ops team.
- 01
Install
Cloud: sign in. Linux: load the Compose bundle, set a single .env, start the services. Windows Server: the same — or run the native installer instead.
- 02
Migrate
Database migrations run automatically on startup — strictly forward-only, ordered, and safe to re-run. Cautious admins can run them explicitly from the command line instead.
- 03
Verify
Confirm liveness on /healthz and readiness on /readyz, which also checks the database connection and that migrations are current. Structured logs and an optional metrics endpoint plug into your monitoring.
- 04
Upgrade
Pull the new version and restart. On-prem, the upgrade script takes an automatic database dump first, then migrations bring the schema forward — and every release documents its migration set.
Frequently asked questions
Can UniSentinel run fully air-gapped?
Yes. Container images load from tarballs, the license is an Ed25519-signed file verified offline, and the product requires zero outbound connections — with no telemetry by default and error reporting strictly opt-in. TLS comes from the bundled reverse-proxy option or your own proxy, and email goes through your internal SMTP relay.
Can we run on Windows Server without Docker?
Yes. The native package installs the web and worker processes as Windows services, uses PostgreSQL for Windows, stores files on an NTFS path, and offers an optional TLS proxy service — all through a scripted installer. Windows is built and tested continuously in our CI, not ported as an afterthought.
How do upgrades work?
One platform version covers the core and every module, so there is a single release to track — modules unlock by license, not separate artifacts. The flow is: backup (automatic pre-upgrade database dump on-prem), pull the new version, migrations apply automatically and forward-only, then verify on /healthz.
What happens to our data if we leave?
You take it with you. The workspace export produces a complete JSON/CSV bundle of your data, and on-prem your database and files already live on your own infrastructure. If a license lapses, a grace period and then read-only mode follow — your data is never locked away.
Are cloud and on-prem functionally identical?
Yes — same codebase, same artifact, same features. Cloud is multi-tenant with isolated workspaces; on-prem is a single-workspace instance of the very same code. What differs is who runs the infrastructure and how entitlements arrive: a subscription in cloud, a license file on-prem.
Get started
See UniSentinel running on your terms
Book a 30-minute walkthrough. We'll map your program to the modules you need — cloud, on-prem Linux or Windows Server.
Every module works standalone. License only what you need — grow when you're ready.