Deployment Models
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.