Introduction

Early access. Registry is rolling out behind an organization flag. Storage and egress are metered but not yet billed.

Longbridge Registry is a private artifact registry hosted in the EU. It does three jobs from one place:

• A private container registry — push and pull your own images at registry.lngbrdg.com/<registry>/<repository> over the OCI Distribution API, authenticated with a key or a keyless CI rule.
• A pull-through cache — mirror public upstreams (Docker Hub, GHCR, and the rest of the catalog) through your own registry, so a rate limit or an outage upstream doesn’t stall your builds.
• A Terraform and OpenTofu registry — host private modules and providers on the native registry protocol, with provider signing managed for you.

Who it’s for

Teams running builds and deployments who want their images close to their clusters, under EU data residency, without operating a registry themselves — and who are tired of public-registry rate limits during a busy CI hour.

What you get

• Standard docker / oras push and pull — no bespoke client.
• Deduplicated, content-addressed storage; you’re billed for logical bytes.
• Short-lived credentials via lbr registry login, keyless CI via OIDC, or long-lived keys where you need them.
• A pull-through cache with per-registry BYO upstream credentials, so cached private images ride your own rate limits.
• First-class Terraform, CLI, and Go SDK surfaces — the registry and its keys are declarable as code.

Where to next

• Quickstart — from nothing to your first docker push in about five minutes.
• Core concepts — registries, keys, access rules, and the cache.