By default, customers activate their subscription on the OutSystems Cloud and start developing and delivering applications immediately. But OutSystems was designed also for other clouds (private or public), on-premises or hybrid deployments. The OutSystems architecture guarantees that there is no loss of functionality and enables developers to move from the public cloud to an on-premises installation if need be.
Here's a high-level overview of the possible configurations:
OutSystems Cloud: Subscribe to the OutSystems Cloud to get the platform immediately provisioned, configured and tuned for high performance, security and reliability. OutSystems takes care of the infrastructure and provides both self-service options and a portfolio of admin services in a simple-to-use offering.
Other public clouds: For organizations that require deep control of their infrastructure and want to take advantage of the infrastructure services offered by public cloud vendors, OutSystems can also be provisioned in any other public cloud service.
Private cloud and on-premises: Some organizations need full control over enterprise and customer data, or have very specific requirements for security and regulatory compliance. Developer teams can install OutSystems in a private cloud, co-location data center, or on-premises.
Hybrid: It's possible to combine the various deployment models, distributing OutSystems deployments across public, private or on-premises environments, leveraging the unique benefits of each.