ActiveManage doesn't lock you into one hosting model. The platform runs on a single shared PHP/MySQL server for small deployments, and scales up to AWS Elastic Beanstalk with sharded multi-tenant databases for large ones. The choice is driven by Site Settings rather than code changes.
Single-server deployments
The simplest setup: one PHP-capable web server (Apache or Nginx) plus one MySQL/MariaDB database. Suitable for internal tools, small SaaS products, or development environments. Sessions can live in file-based PHP sessions, Redis, or Memcached.
Multi-tenant shared database
For multi-tenant SaaS products, the default tenant database mode is shared — every tenant's rows live in the same physical database, distinguished by a tenantid column on each row. Cheap to run and trivial to back up.
Multi-tenant separate databases
For tenants that need stronger isolation (regulatory, performance, or just preference), switch tenant database mode to separate. Each tenant gets its own physical database. ActiveManage manages the connections automatically.
Database sharding
If you outgrow a single database server, enable Tenant Sharding. Tenant databases are distributed across multiple Database Host entries — each host is a separate MySQL/MariaDB server. Sharding can be paired with either shared or separate tenant database modes.
AWS Elastic Beanstalk
If you set the Deployment Target in Site Settings to awsbeanstalk, the Deployments feature lets you deploy your ActiveManage application to AWS Elastic Beanstalk instances from inside the admin panel. Useful for autoscaling production deployments.