Function
Place the EPTT core in the operating model that fits the organization’s control needs.
DEPLOYMENT ARCHITECTURE
Choose the control boundary — not just the server location.
Deployment is about responsibility, isolation, network, release control and operating model. The EPTT core stays the same; the boundary around it changes.
Cloud
Central operation with low local infrastructure burden.
→EPTTDedicated
Separate runtime and clearer technical isolation.
→EPTTOn-Prem
EPTT components in the customer environment.
→EPTTOEM / White-label
Agreed branding, distribution and delivery model.
→OPERATIONAL CONTRACT
Deployment is a responsibility boundary.
Cloud, Dedicated, On-Prem and OEM are not merely different places to run software; they shift responsibility for operations, network, access and recovery.
Requirement
Network paths, DNS/TLS, administrative access, backup/recovery and integrations must be clarified.
Boundary
The same product core does not mean the same operational responsibility; responsibility must be defined per delivery.
CloudCentral operation
EPTT infrastructure is operated centrally; customer network and endpoint requirements still apply.
DedicatedSeparate runtime
Technical isolation and change boundaries must be described in the delivery.
On-PremCustomer environment
The customer owns parts of infrastructure, network and local operation according to the agreed responsibility model.
OEMBranded delivery
Branding, distribution, support and release responsibility must be agreed separately.
DECISION BASIS
Define the boundaries before the model.
The right deployment model is chosen by clarifying responsibility and integration boundaries first — not by starting with a product label.
01Runtime
Where should the relevant EPTT components actually run?
02Network
Which network boundaries, connections and access paths are involved?
03Identity & access
Who owns the user, role and login model for the delivery?
04Monitoring & backup
Who monitors, backs up and tests restore for the selected runtime?
05Release control
How are clients and server components approved, distributed and maintained?
06Support responsibility
Who handles first-line, escalation and technical changes?
07Branding & distribution
Is the delivery EPTT-branded, partner-led or OEM/white-label?
The answers become part of the concrete scope and offer.Build solution scope →