Freedom to choose your provider
Choose providers and locations to suit Kubernetes and Object Storage. Loopback brings management together with central permissions and a shared billing model.
Choose providers and locations to suit Kubernetes and Object Storage. Loopback brings management together with central permissions and a shared billing model.
Not every workload places the same demands on its infrastructure. One application needs a specific location, another needs suitable compute resources. Costs and proximity to the data being processed also influence the choice.
With Loopback, you choose providers and locations for each service. You manage Kubernetes and Object Storage through the same platform. Accounts, organizations, permissions, and billing remain within a shared model.
Choosing a provider starts with your application's requirements. Which resources does it need? Where should data be processed? Which connections does it have to other services?
Within one company, these questions can lead to different decisions. A development team needs an environment for regular testing. A production application must run at a defined location. Another service processes files and needs Object Storage.
Several criteria help guide your choice:
| Criterion | Planning question |
|---|---|
| Location | Where should the application and data run? |
| Resources | Which compute and storage resources does the workload need? |
| Data paths | Which other services does the application communicate with? |
| Costs | Which ongoing resource usage and transfers will occur? |
| Operations | How will the infrastructure fit into your team's workflows? |
Freedom to choose your provider means being able to consider these requirements for each service. A decision about one location or provider does not automatically have to determine the infrastructure for your entire stack.
When you use different providers, your team still needs a shared framework for management.
In Loopback, your organization provides that framework. Memberships, groups, and permissions are managed there. Projects structure your resources. Your selected infrastructure providers supply the underlying infrastructure.
Loopback remains your team's shared point of access for management. You work within the same organization even when individual resources run with different providers.
This is particularly useful when new requirements emerge. An additional project may call for a different infrastructure choice. Its management can still fit into your existing organization.
For Kubernetes, you choose a provider and location to suit your cluster. Loopback connects this choice with managed cluster operations.
Loopback provides the HA control plane and private network. Compute resources come from your selected providers. The Kubernetes API remains the standard interface for your applications and tools.
This lets you consider two decisions separately: which infrastructure should support the workload, and how should the cluster be managed?
For your team, this could lead to the following structure:
| Environment | Selection requirement |
|---|---|
| Development | Resources for builds, tests, and ongoing development |
| Staging | A suitable environment for testing planned releases |
| Production | Location and resources suited to the production workload |
These requirements guide your provider choice. Cluster management stays on Loopback.
You can find more about cluster operations on the Kubernetes product page.
Infrastructure choices also matter for Object Storage. Loopback offers several S3 providers. Your selected provider determines where the data is stored.
Your application accesses buckets through familiar S3 APIs and SDKs. You manage them in your Loopback project alongside its other resources.
Consider the entire data path when choosing. An application that frequently reads or writes large files has different requirements from a service with occasional uploads. The cluster location and storage location therefore belong in the same planning process.
A shared project context does not automatically mean physical proximity. Your selections determine where compute and data should actually reside.
The Object Storage product page describes the features for managing buckets and access.
Infrastructure can differ between projects. Responsibilities within your company should still remain clear.
Loopback uses platform-wide RBAC for this purpose. People have individual accounts and become members of your organization. Groups and fine-grained permissions let you define who may use which products and functions.
Permissions are managed within the shared platform context. For example, a team can be responsible for several projects whose clusters run with different providers.
When organizing access, a person's tasks are what matter. Infrastructure provider selection becomes part of resource planning, while platform permissions remain centrally assigned.
This makes it easier to represent responsibilities consistently across your entire stack.
Different infrastructure decisions also affect costs. Compute, storage, and traffic therefore belong in the planning for each workload.
Loopback brings billing together in a shared model. It consists of a Platform-Fee per organization and usage-based costs for resources.
Your team gains a central framework for assessing the economics of its chosen infrastructure. Cost planning should still reflect the actual architecture: which resources run continuously? How much storage is needed? Which data is transferred between services?
Provider choice is one part of this assessment. How your application uses its resources matters just as much.
Suppose a company operates several applications. One team develops a new service while another maintains an existing production application. Files are also stored in Object Storage.
The teams can choose infrastructure based on their respective requirements:
This creates a shared management structure for different infrastructure decisions.
Freedom to choose your provider gives you room to plan your infrastructure. You can select Kubernetes and Object Storage according to their respective requirements while retaining a shared framework for operations.
Loopback connects these services through organizations, projects, permissions, and billing. The underlying infrastructure can differ. The platform for managing it stays the same.
Start with managed Kubernetes, object storage, registry, or Bundles. One account, one permission model.