HN Showcase
Back to browse
BridgeBase – one control plane for TigerBeetle,Redis,MySQL,ClickHouse

BridgeBase – one control plane for TigerBeetle,Redis,MySQL,ClickHouse

by amustaque97·Mar 2, 2026·3 points·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemBold Bet

Control plane for multi-database chaos—real pain, but execution is beta-only.

Strengths
  • •Tackles genuine operational overhead: six dashboards → one, six auth schemes → one
  • •SDK-first approach (Node, Python) with live TigerBeetle + Redis, roadmap clear
  • •Niche but specific: TigerBeetle combo unusual enough to suggest real customer demand
Weaknesses
  • •Only 2/6 promised databases live; MySQL, ClickHouse, PostGIS, VectorDB still 'coming soon'
  • •'One control plane' claim unproven—vague how deep integration and operational automation actually go
Target Audience

Platform engineers and SaaS teams running heterogeneous database stacks

Similar To

HashiCorp Terraform · MongoDB Atlas · Supabase (multi-engine)

Post Description

Hi HN,

We built this because we got tired of becoming accidental platform engineers.

Multi-database stacks are the default now, but the operational overhead is brutal. We wanted one auth layer, one dashboard, and one way to provision and monitor everything.

Live now: `Redis` + `TigerBeetle` (weird combo, but that’s what our beta users needed).

Next up: - `MySQL` - `ClickHouse` - `Postgres` + `PostGIS` - `VectorDB`

SDK-first approach. `Node` and `Python` ready.

npm: <https://www.npmjs.com/search?q=%40bridgebase>

PyPI: <https://pypi.org/project/bridgebase/>

Would love feedback from anyone running multi-database workloads in production.

What’s the biggest pain point we missed?

Similar Projects