Hi All
Shambu Pujar and Marek Karwacki (Current Foundation DevOps team) are proposing to operate the Babylon Mainnet Gateway + RCR/SS ( all of P1 services). for the Radix ecosystem.
-
The database and Kubernetes cluster is planned to run on AWS while the Radix full nodes are planned to run on OVH — combining AWS’s reliability with OVH’s cost-effective compute.
-
The setup we’re proposing has been battle-tested for a few years now, handling a variety of workloads and traffic fluctuations in production.
-
We use a Blue/Green deployment strategy, meaning upgrades — including full ledger resyncs — happen with zero downtime for end users.
-
We can be production-ready within 5-8 weeks of project start
Relay and Signalling Server Proposal
-
Shambu Pujar and Marek Karwacki are also proposing to operate the Radix Connect Relay (RCR) and WebRTC Signalling Server.
-
Both services are lightweight message relays — they pass encrypted data between Radix clients without inspecting or storing it.
-
Our preferred approach (Option A) is to run these as add-on workloads on the same infrastructure already built for the Gateway,
We had a thought on if it is possible to offset some of the costs from service offering to commercial vendors within ecosystem. It is technically feasible, however commercially not viable given the conditions and probable payment modes that a commercial vendor might propose. So the cost offsetting from the proposal fee in near term doesn’t seems viable.