¶ Deployment Models for the eTag Fuse Platform
The eTag Fuse Platform offers deployment flexibility to meet diverse organizational, regulatory, and operational requirements. Fuse can be deployed on-premises, in cloud environments, or across hybrid infrastructures — enabling governed, explainable interoperability wherever systems, data, AI, and users operate.
¶ Deployment Options
| Model | Description |
|---|---|
 On-Premises |
Deploy Fuse within private data centers, secure facilities, or air-gapped networks. |
 Cloud |
Deploy Fuse in public, private, or hybrid clouds (AWS, Azure, GCP, or private hosting). |
 Hybrid |
Deploy Fuse clusters that span on-premises and cloud environments for unified governance. |
Fuse adapts to your operational strategy — without forcing vendor lock-in or architectural compromises.
¶ Key Runtime Components
Fuse runtimes consist of two primary types:
-
Hub Runtimes
Optimized for web-based access, user interaction, administrative operations, and lightweight on-demand workflows. -
Engine Runtimes
Optimized for heavy processing, unattended orchestration, scheduled workflows, RPA tasks, and service-level integrations.
Both types of runtimes self-register and discover each other, enabling seamless runtime interoperability across single-site or multi-site deployments.
¶ Scaling and Architecture Considerations
Fuse supports both single-cluster and multi-cluster deployments:
- Cluster Planning: Must consider expected workflow load, AI agent execution, security segmentation, and regulatory controls.
- Scaling Approach: Hubs and Engines can scale independently depending on usage profiles.
- High Availability: Achievable via RDBMS replication, cluster redundancy, and Fuse RPC capabilities.
- Air-Gapped Support: Fuse can operate entirely within disconnected environments where external internet access is prohibited.
¶ Multi-Tenant vs Dedicated Deployments
While Fuse supports logical multi-tenancy, best practice recommends dedicated clusters per organization to:
- Reduce risk of cross-tenant data exposure
- Simplify governance and role separation
- Enhance security and regulatory compliance
If interoperability between organizations is needed, edge runtimes with limited capability scopes can bridge clusters safely.
¶ Compliance and Regulatory Adaptability
Fuse can be deployed to meet strict regulatory and operational needs, including:
- Government and classified environments
- Healthcare and insurance systems (HIPAA, HITRUST)
- Financial services (PCI-DSS, SOC 2)
- Privacy and residency regulations (GDPR, CCPA)
Deployment configurations can incorporate:
- Role-based access control (RBAC) for all administrative functions
- Encrypted communication between runtimes
- Staged workflow promotion and runtime operational hardening
¶ Deployment Flexibility Summary
| Capability | Supported |
|---|---|
| On-Premises Installation |  |
| Private Cloud Hosting | |
| Public Cloud Hosting | |
| Hybrid Cloud Deployment | |
| Multi-Region Availability | |
| Air-Gapped Operation | |
| Confidential Computing Environments | |
Fuse is infrastructure-agnostic but governance-first — allowing you to deploy the platform where it makes the most strategic, secure, and scalable sense.
Next: Runtime Architecture — Learn how Hub and Engine runtimes operate and collaborate in Fuse deployments.