Skip to content
Britive Bridge
Deployment Guides

Deployment Guides

The Bridge runs from a single container image in three shapes. Pick the one that matches where you run software and how much scale and availability you need.

Not sure which to pick? If you’re trying the Bridge for the first time, start with Single-Server. Move to AWS or Kubernetes when you’re ready for production.

Choose Your Deployment

Single-Server
One container, one host. Best for trials, labs, and small teams.
AWS (ECS Fargate)
A scalable, highly available cluster deployed with CloudFormation.
Kubernetes
The same cluster on any Kubernetes platform (EKS, on-prem, and more).

How They Compare

Single-ServerAWS (ECS)Kubernetes
Best forTrials, labs, small teamsProduction on AWSProduction on Kubernetes
ContainersOne (does everything)Many (orchestrator + proxies + session workers)Many (same roles, as pods)
Scales automaticallyNoYesYes
Survives a container failureNoYesYes
DatabasePostgreSQL you provideAmazon RDS (created for you)PostgreSQL pod or managed service
Effort to set upLowestMedium (one CloudFormation command)Medium (one manifest, plus a cluster)

What Every Deployment Needs

No matter which mode you choose, you’ll need:

  1. A PostgreSQL database. The Bridge stores all of its state here. It’s mandatory in every mode. The AWS guide creates one for you; the other guides show you how to point at one.
  2. A configuration file. A single YAML file that turns on the protocols you want and sets options. A fully documented reference file is available to download: bridge.reference.yaml. See Configuration.
  3. A few secrets. Most importantly an encryption key the Bridge uses to protect stored credentials. Each guide shows you how to generate and supply it.
  4. A license (recommended). The Bridge runs in limited mode without one. See Licensing.

Keep the encryption key (BRIDGE_ENCRYPTION_KEY_B64) safe and don’t change it after go-live. It protects the credentials stored in your database; changing it makes existing checkouts unreadable.

See the Full Picture

The guides above deploy the Bridge on its own. Once you add the co-located Broker, the Britive platform drives checkouts and the deployment reaches out to your target resources — which adds traffic planes and ports the basic guides don’t cover.

Bridge & Broker Network Architecture
Every port and channel in a complete Bridge + Broker deployment: the four traffic planes, the checkout and session lifecycle, and a firewall map.

Read it before you design firewall rules or security groups for production. The network model is identical across all three deployment shapes.

Last updated on