Resilience across two providers

Two providers, one platform. Your risk spread out.

The clusters “Primary” and “Secondary” run the same applications on two of the selected providers. Secure Network by FABRIC connects them, encrypted over WireGuard, one shared Registry serves both, and you run everything from one organization.

The use case

Independence built into your architecture.

Products involved

Why two

For many products, availability is not a feature but the promise to customers. With Loopback you put that promise on two pairs of shoulders. You start “Primary” with one provider and “Secondary” with a second, each with an HA control plane, four Compute nodes, and its own load balancer. You operate both clusters the same way, with the same tools and the same permissions.

Connected through Fabric

Secure Network by FABRIC connects the two clusters peer-to-peer over WireGuard, encrypted and direct. The eBPF firewall runs on every node, and it is your DDoS protection at the same time. With WireGuard you automatically have access to your clusters, and over VPN you reach the nodes directly. Who may see or change Fabric is set in the central RBAC.

One image, two places

Your images live once in the organization's shared Registry and are available to both clusters. So Primary and Secondary run the same versions of your applications, and you roll out a new release to both without maintaining two pipelines.

Freedom as a strategy

You are not tied to a single vendor. When prices, locations, or requirements change, you shift capacity from one cluster to the other without switching platform, tools, or permission model. That is exactly why Loopback is built provider-agnostic, and exactly how your architecture stays in your hands.

The setup

Two clusters, one network. One bill.

This is what a month of this setup looks like. The sample bill shows the dynamic costs, and the Platform-Fee for your organization comes on top.

Sample bill

Resilience across two providers

Two production clusters on two of the selected providers run the same applications, connected and encrypted through Secure Network by FABRIC. You spread your risk and never depend on a single provider.

  • Cluster Primary

    HA control plane, 4 Compute with 4 vCPU / 8 GB, 1 load balancer

    253.18€

  • Cluster Secondary

    HA control plane, 4 Compute with 4 vCPU / 8 GB, 1 load balancer

    253.18€

  • Registry

    50 GB, 0.05€ per GB, shared by both clusters

    2.50€

Total

Sample for this setup, monthly.

508.87€

Amounts are net. Statutory VAT is charged in addition.Dynamic costs are shown per month and billed hourly, based on 720 hours.All amounts are rounded.Prices can be updated dynamically. When you open this page, you see the price that currently applies, and it is non-binding. The binding price is set when you order.

  • Primary

    HA control plane, four Compute nodes with 4 vCPU and 8 GB, and its own load balancer.

  • Secondary

    The same setup with a second provider, ready for the same applications.

  • Secure Network by FABRIC

    WireGuard peer-to-peer between the clusters, with an eBPF firewall on every node.

  • Registry

    One shared Registry for both clusters, organization-wide with Loopback RBAC.

How you get started

  1. 01

    Start Primary

    Create the first production cluster with one of the selected providers.

  2. 02

    Start Secondary

    Create the second cluster with the same setup on another provider.

  3. 03

    Connect Fabric

    Secure Network by FABRIC connects both clusters, encrypted over WireGuard.

  4. 04

    Roll out to both

    The same images from the shared Registry run on Primary and Secondary.

Next step

Start Primary and Secondary on two providers and connect them through Secure Network by FABRIC.