Cycle Platform Primitives
The Cycle Platform is built on foundational pieces known as 'primitives', which are designed to work together to provide a fully managed DevOps ecosystem. By leveraging these core components, users can easily organize and deploy resources, manage environments, and control various aspects of their infrastructure with precision
| Primitive | Definition |
|---|---|
| Hubs | The hub is the highest level resource on the platform. It is tied to a tier and defines access rights, the number of users, servers, environments, images, and other resources. All resources created within the platform are associated with a hub. |
| Infrastructure | Represents a collection of servers, clusters, providers, IP addresses, and auto-scale groups that form the backbone of infrastructure management. |
| Clusters | A cluster groups together servers from one or more providers, organized by name, and serves as a unit to physically separate workloads on infrastructure. |
| Servers | Servers are compute nodes deployed into clusters through the platform, providing the underlying hardware or virtualized resources for running containers. |
| IPs | IP addresses, either IPv4 or IPv6, are provisioned from a provider and can be assigned to servers or reserved for future use. |
| Auto-Scale Groups | Define rules for how infrastructure should respond to scaling events, allowing resources to automatically adjust based on demand. |
| Environments | An environment represents a group of containers that share an isolated network, which spans all servers within a given cluster. |
| Deployments | Enable the maintenance of multiple independent versions of applications within a single environment, supporting version control and rollback capabilities. |
| Scoped Variables | Allow variables, such as environment variables or injected files, to be assigned to one or more containers within an environment for configuration management. |
| Images | An image is an atomic snapshot of a filesystem, used to create containers. Images can be built from various sources. |
| Image Source | Refers to the location, type, and authentication details used when creating an image from an external source. |
| Containers | A container represents the combination of an image and its configuration, providing the runtime environment for applications. |
| Instances | An instance is a copy of a container, deployed and running within the platform. |
| Stacks | Stacks allow users to configure all aspects of an application, save the configuration to version control, and automate the deployment process. |
| Pipelines | Pipelines enable the creation of declarative automations that handle complex deployment workflows and integrations. |
| DNS | Provides full-featured DNS management, allowing the creation and management of DNS zones and records. |
| Networks | Represents a software-defined network used to connect between two to eight environments, facilitating secure communication between them. |