Enterprise Solutions

Protocol infrastructure for isolated enterprise operation — Dedicated Cloud or self-hosted.

Request Enterprise info

Overview

Enterprise Solutions delivers the Protocol platform as enterprise infrastructure: the same application as in the public cloud, operated in an isolated environment.

The focus is deployment, isolation, identity integration and long-term infrastructure operations — not a separate product fork.

Objectives:

  • Isolated Protocol environment per organisation
  • Integration with existing identity and IT landscape
  • Predictable operations including updates and support
  • Data sovereignty through residency and tenancy

Deployment models

Dedicated Cloud is the preferred Enterprise model. Self-hosted is available when operations must remain fully with the customer.

Public Cloud (SaaS)

Multi-tenant operation on deep.rent infrastructure. Reference for standard operation without tenancy isolation.

Dedicated Cloud

Recommended

Isolated Protocol environment per customer, operated by deep.rent.

Isolation typically covers:

  • Database
  • Object storage
  • Domain / TLS
  • API and workers
  • Backup scope

deep.rent operates the platform. The customer controls identity, residency and integrations.

Self-Hosted / On-Premises

Optional, on request. Installation in customer infrastructure (Docker Compose, Kubernetes or OpenShift).

The customer operates infrastructure and runtime. deep.rent provides artefacts, upgrades and support for the licensed release line.

Architecture

One codebase, swappable infrastructure

Cloud and Enterprise share one application codebase. Differences exist only through deployment and providers.

Clients (Web · iOS · Android · Desktop)
↓
Protocol API
↓
Business Logic
↓
Provider Layer
↓
Storage · Auth · Mail · AI · OCR · Jobs

Providers

Infrastructure capabilities are encapsulated behind provider interfaces. Enterprise selects storage, authentication, mail and optional AI/OCR providers to match residency and policy.

Provider options

Storage

  • S3-compatible (e.g. Wasabi, AWS, Azure, MinIO)
  • Local filesystem (self-hosted)

Authentication

  • OpenID Connect
  • Microsoft Entra ID
  • Directory federation by project

Mail

  • SMTP
  • Microsoft 365 / Exchange
  • SES / SendGrid

AI / OCR

  • Cloud providers
  • Local (self-hosted)
  • Fully disableable

Enterprise capabilities

What the infrastructure adds for enterprise operation:

Security & Identity

  • TLS and encryption at rest
  • SSO via customer IdP
  • Roles and permissions
  • Audit logging
  • Optional IP allow-listing

Operations & governance

  • Isolated tenancy
  • Configurable residency
  • Branding / domain / mail sender
  • Retention and archival rules
  • Controlled feature enablement (AI, OCR)

Integration

  • REST API
  • Webhooks
  • Identity federation
  • Project-specific interfaces

Operations

  • High availability
  • Health endpoints and metrics
  • Backup and restore
  • Horizontal scaling of API and workers

Data protection & control

Enterprise supports organisational controls through isolation, identity, logging, and retention/deletion workflows. Legal accountability remains with the customer as controller.

Core controls

  • Data sovereignty via Dedicated Cloud or self-hosted
  • Auditability of administrative and security-relevant events
  • Retention and deletion per configured policy
  • Encryption in transit and at rest

Lifecycle

Enterprise follows a predictable release cycle independent of continuous public-cloud delivery.

Releases & LTS

Shared release train; Enterprise consumes versioned artefacts. Selected lines can be designated LTS.

Updates & migration

Dedicated Cloud: scheduled upgrades. Self-hosted: customer installation from published images/packages. Schema migrations ship with releases; breaking changes are announced.

Operations

Availability & scaling

Redundant API/worker instances, horizontal scaling, HA for stateful components according to infrastructure.

Monitoring & backup

Health/readiness endpoints, operational metrics, backup and restore in the tenancy scope (Dedicated Cloud) or customer-owned (self-hosted).

Deployment

Docker

Reference services:

  • protocol-api
  • protocol-worker
  • postgres
  • redis
  • storage
  • reverse proxy

Kubernetes

For larger or HA installations: rolling updates, health probes, horizontal scaling.

Mobile apps

iOS and Android apps are identical across all deployment models.

  • API endpoint
  • Tenant
  • Branding

No separate Enterprise binaries.

Licensing

Two models:

Enterprise (Dedicated Cloud)

  • Annual license
  • Operated by deep.rent
  • Updates, security fixes, support

Self-Hosted

  • On request
  • Annual license and maintenance
  • Artefacts and support for the licensed line

Optional: migration, integrations, training, enhanced SLA.

Principle

One platform. Enterprise infrastructure.

Enterprise Solutions changes deployment and operations — not the application. Functional evolution comes from the same codebase.

Request Enterprise info