Skip to content

General Design Principles

These principles apply across all five pillars and should inform every architecture decision on Cleura Cloud.

  • Design for failure. Assume any instance, volume, or availability zone can fail, and architect so the workload survives it.
  • Automate everything repeatable. Provision through the Cleura API, CLI, or Infrastructure-as-Code rather than one-off manual changes in the portal.
  • Match the deployment model to the workload’s risk profile. Use the Cleura Compliant Cloud for regulated or mission-critical data, the Cleura Public Cloud for general-purpose workloads, and the Cleura Private Cloud where full isolation is required.
  • Keep architectures open and portable. Cleura Cloud’s OpenStack foundation avoids proprietary lock-in. Design workloads so they remain portable across regions and, if ever needed, providers.
  • Build in security and compliance from day one, not as an afterthought before an audit.
  • Test what you assume will work. Rather than testing only at launch, test backups, failover, and scaling regularly.
  • Right-size continuously. Cloud resources are elastic. Provisioning should be revisited as usage patterns change, not fixed at launch.