Architecture
Core Architecture
Deployment Models
5 min
activate supports a range of deployment architectures to suit different organisational needs, security policies, and infrastructure preferences these options fall into three main categories on premises active directory hybrid active directory cloud only on premises ad {{active directory}} is fully hosted within your organisation’s network environment all domain controllers and identity services are on premises hybrid ad a combination of on premises {{active directory}} and {{microsoft entra id}} (e g using {{microsoft entra connect}} ) allows integration with both local domain services and cloud based identity platforms entra id only (cloud only) no on prem {{active directory}} identity is managed entirely through {{microsoft entra id}} activate integrates with all of the above via standard protocols (ldap, ldaps, kerberos, saml, oidc, etc ) infrastructure layout options single server deployment all core components ( web , orchestrator , and database ) are installed on a single server simplest footprint and fastest to deploy ideal for development , test/uat , or small scale production limited resilience and scale; not suitable for ha or strict separation of duties separate database server web and orchestrator are hosted together; the database runs on a separate sql server instance improves performance by isolating database workloads enables independent sizing, maintenance, and scaling of the data tier aligns with enterprise backup/dr practices split web and orchestrator servers the web and orchestrator components are deployed on separate servers independent scaling for interactive traffic vs background jobs better performance tuning and fault isolation enables horizontal scaling of either tier as demand grows these layouts are examples, not prescriptions they can be combined or evolved over time (e g , start single server, then split database, then separate web/orchestrator) to match growth, security, and availability requirements