Your application.
A full stack ready to grow.

Set nodes, caching and database topology for the enabled template. Test site plugins, sessions and backups.

Options differ by engine. Primary–secondary replication does not guarantee automatic failover; check the selected topology.

Automatic failover in this template requires Pgpool-II. Asynchronous replication does not guarantee zero data loss.

The upstream package starts with one broker. A RabbitMQ cluster requires an additional topology and workload-specific connectivity and replication configuration.

Based on Auto-Scalable Magento Cluster v2. Check the version, extensions and required services before provisioning.

Redis Cluster is distinct from Sentinel. Check the enabled template/version; Redis 7.4+ requires a self-managed custom image outside the certified managed stack.

Requires multiple available regions. Plan replication, latency and recovery separately; this is not an automatic DR guarantee.

A Kubernetes package separate from standard PaaS runtimes. Teams still configure Kubernetes workloads, policies and settings.

Based on Auto-Scalable Spring Boot Cluster. Configure application settings and resources; this differs from Jar Builder packages.

A Swarm topology rather than a single Docker Engine node. Plan manager quorum, placement and persistent data.

The package supports app and balancer scaling with session replication. Applications must support the chosen configuration.

Based on Auto-Scalable GlassFish Cluster with a balancer topology. Check Java and application compatibility before deployment.

A Community Edition package. Check node counts, data replicas and resource sizing for your workload.

Based on DevOps Lab – GitLab Server. Check runner / registry options and configure your team’s pipelines.

Connect repositories, credentials and build agents for your workflow. Pipelines still need application-specific configuration.

Configure repository formats, access permissions and storage for the selected package/version.

Connect with appropriate database permissions and restrict access to administrators.

A microservice build/deploy package distinct from Spring Boot Cluster. Configure the project and build for its manifest.

Check PHP/Drupal versions and modules. Plan backups for both site files and the database.

Choose extensions compatible with the package version and plan CMS updates alongside backups.

Plan learner file storage, the database, scheduled jobs and plugin compatibility for your usage.

Plan domains, SSL, network ports and resources around participants. No fixed room or user capacity is implied.

Check package version and edition terms. Configure identity, data storage and backups for your team’s policies.

Check themes, modules and payment integration requirements before launch.

Choose version-compatible extensions and configure store domains, SSL and database operations.

A file application rather than included object storage. Plan storage capacity and backups separately.

Configure storage, account access and updates for the package edition/version.

Check plugin compatibility, connect your workflow and back up the database and attachments.

Check the installed version and user permissions, and configure backups before production use.

Applies to a selected environment/layer. Domains and connectivity must meet certificate validation requirements.

Configure separate Backup Storage and retention, and test restores. Included retention or instant recovery is not implied.

Extend an existing environment and configure the repository and deployment pipeline for the package.

Choose source/target nodes and paths carefully. File synchronization is neither database replication nor a backup.

Configure compatible Logstash / OpenSearch endpoints and access permissions. Destination services have separate scope.

Configure data sources and dashboard access for the systems you monitor.

Prepare a domain, certificates, storage and push/pull access. Check the installed version’s features.

The upstream repository was archived on 7 May 2024 and documents support for Kong 1.x / Node.js 8–12 only. Verify platform availability and never expose the Admin API directly to the Internet.

Configure scrape targets, retention, storage and any required alert delivery system.

Choose destinations and supported routing policies. Validate health checks and DNS before serving live traffic.

Manage images, ports, volumes and host updates. This is not a Kubernetes cluster.

Check licensing and connection allowances. Configure network routes, certificates and user accounts.

Configure repository storage, authentication and backups.

Check Java, build configuration and dependency resolution for the selected package.

Configure repository access and deployment targets. Test application compatibility with the WildFly version.

Check the required edition, licence, operating system and supported services.

Standalone does not imply an HA cluster. Configure domains, plugins, storage and website backups.

Check Alpha status and limitations in the actual catalog. Plan data synchronization, DNS and recovery; this does not provide automatic DR.

Check Alpha status and enabled regions. Test replication, latency and failover; zero data loss and immediate production readiness are not guaranteed.

Check the game version, ports and resources, and back up game data. Player capacity depends on configuration and load.

Check the package’s network, protocol and software version, and plan node storage and operations.

Check Community modules and version compatibility. Enterprise features and additional services have a separate scope.

Check the package’s edition, licence, Java, database and publishing workflow.

Check supported Java and database versions, then configure domains, access and backups.

Check the edition, licence, search service and document storage. Configure permissions and backups.

Choose compatible extensions, configure authentication and back up the database and attachments.

Configure user permissions, check plugin compatibility and back up content and configuration.

Check the package version, modules and runtime. Configure editor permissions and backups.

Check PHP, database and required extras, then test updates and backups.

Configure respondent-data access and retention. Check mail delivery and the selected version’s requirements.

Check licensing and permitted use. Plan security, integrations and operations for the intended service.

Check the version, extensions and supporting services. Standalone does not automatically include an HA cluster.

Configure capacity, retention, access and backup jobs separately, and test restore. Storage alone does not create automatic backups.

Configure mail channels, roles and data retention. Check the version and set up backups.

Connect existing IMAP/SMTP services and configure TLS and user access. This does not create a mail server.

Check source and target versions and compatibility before changing, with backups and a rollback plan.

Match source, target and paths to the primary configuration. This is not database replication or backup.

Use a working domain and certificate. Check reverse-proxy behavior and redirect loops before enabling.

Check licensing, supported versions and topology. Configure policies and test their effect on the application.

Check provider permissions and conditions, assign administrators and manage configuration changes responsibly.

Use an existing RustFS deployment and a domain meeting certificate-validation requirements. Verify endpoints before use.

Check the OS, repositories, privileges and dependencies. Additional packages can affect the existing runtime.

Set schedules and time zones, and test application impact. Storage and some resources may still incur charges while stopped.

Use the required service account or licence. Configure agents and credentials securely and review exported data.

Check service availability and terms. Configure the agent, credentials and metrics to send.

Check the engine and cluster state first, with backups and a runbook. Recovery without data loss is not guaranteed.

Check the engine and version and back up data before analysis. Diagnostics do not repair or guarantee data integrity.

Validate configuration and module compatibility before reloading and test connections. Zero downtime is not guaranteed in every case.

Choose versions compatible with the OS and application dependencies, then test builds and service startup.