Loopback
DEZu Deutsch wechseln

BundlesBeta

From repository to cluster. One workflow.

Connect a repository, set the path to the target cluster, and run deploy and rollback in Loopback. Built images are stored in the organization-wide Registry.

Get started
GitHub through a Bundle to environments and clusters.

From repository to workspace.

Four steps on the platform. Connect a repository, set workspace and settings, build the pipeline and image, and see the running app.

A workflow your team creates.

The Bundle stores your team's workflow in the account: who owns it, which repository it uses, where it deploys, and how you roll back.

Saved Bundle checkout-api with ownership, repository binding, target cluster, last revision, and who can run it.

checkout-api

Saved in the account

Bundle

checkout-api

Team platform · acme-platform

Repository

acme-platform/checkout-api

Bound · branch main

Target cluster

production-cluster-001

Kubernetes · environment thursday-dev

Last revision

1.4.2

Chart revision of the Bundle

Rollback

Previous revision

Stored in the workflow

Who can run it

Platform · acme-platform

Deploy and rollback for this Bundle. You set the rights directly on the Bundle in the account.

  • Ownership in the account

    The Bundle belongs to the organization. The team creates it and stays owner of the configuration. You manage name, rights, and execution in the account, not in the repository.

  • Repository as a binding

    You connect a GitHub repository to the Bundle. The connection is part of the saved configuration, and your team can change it at any time in the Loopback UI.

  • Set the target cluster

    The target cluster is part of the Bundle, together with workspace and environment. Your team decides where deployments go before anyone starts the first run.

  • Rollback on the workflow

    Rollback belongs to the saved configuration. Whoever can run the Bundle returns to a previous revision at any time, independent of the next commit in the repository.

Continue in the same model.

The target cluster and the images live on the same platform.

Target

Kubernetes as the workspace

Each environment deploys to a managed cluster in the project.

One fixed price per Bundle.

Each Bundle is 99€ per month, with the Registry for its images included. From repository to cluster, in the same organization.

Bundles

99€

per Bundle per month Registry included

  • Registry included
  • Connect repository
  • From repository to cluster
  • Deploy and rollback
  • Images are stored in the Registry
  • Workflow in the organization
View pricing

FAQ

What is a Bundle?

A Bundle is your team's workflow from repository to cluster. You connect a GitHub repository to a target cluster, run deploy and rollback, and the images live in the organization Registry.

How do DNS and Bundles work together?

Bundles use your organization's zones. You manage records and delegation in the same account, with the same permissions.

Get started