Shared deployment principles across the Armure suite.
All five Armure products share a common service runtime, common identity substrate and customer-controlled deployment model. Each product adds the topology and components required for its job while retaining the same core deployment principles.
Internet → DMZ → Internal, drawn explicitly
For products that span public and internal network zones, the reference pattern separates Internet, DMZ and internal responsibilities so the exposure boundary is explicit and reviewable.
Clients
Browsers and partner systems reach the applicable Armure edge over approved HTTPS endpoints.
Edge tier
Where required, an edge component terminates TLS or brokers requests while keeping responsibilities narrow.
Core services
Place product services, identity integrations, storage and operational records on internal networks according to the selected product topology.
Patterns used across the portfolio
Shared service runtime
All five Armure products use a common service-oriented runtime foundation while exposing product-specific components and capabilities.
Shared identity substrate
Armure Authentication Manager provides the common authentication substrate used across the Armure product family.
No vendor call-home
Armure runtime operation does not require outbound vendor telemetry, licence validation or operational call-home traffic.
Portable deployment
Every Armure product supports on-premise, private-cloud, hybrid and container / Docker deployment patterns.
Horizontal scale
Armure runtime services are designed for stateless horizontal scaling, with persistent state kept in the appropriate customer-controlled data services.
Extensible integration
Supported interfaces and extension points integrate identity, audit, provisioning and adjacent enterprise systems.
Choose the deployment pattern that fits the product and environment
Every Armure product supports customer-controlled deployment on-premise, in a private cloud, in hybrid environments and in containers / Docker. The selected topology can be scaled horizontally to match availability and throughput requirements.
Want the architecture walked against your network?
Bring your topology — DMZ, identity provider, storage — and we’ll show exactly how Armure lands in it.