Skip to main content

2 posts tagged with "metabase"

View All Tags

Launch a BI workspace: Metabase on your own PostgreSQL, in minutes

· 4 min read
FoundryDB Team
Engineering @ FoundryDB

Getting to your first dashboard is rarely about the dashboard. It is about provisioning a database, standing up a BI tool, opening a port, copying a connection string, and praying the two halves agree on TLS. By the time anything renders, the afternoon is gone and the chart you actually wanted is still a row in a spreadsheet.

The Launch a BI workspace stack collapses all of that into one launch. You get a complete Metabase workspace wired to your own PostgreSQL, EU-resident, with dashboards in minutes. You do not assemble it. You launch it.

BI workspace stack composition
RUNNING Stack wired · BI workspace live
Stack Templatebi-workspacelaunch ⇉PostgreSQLtier-2Metabaseattaches dbserve →BI Workspacedashboards
TemplatePostgreSQLMetabase · BI workspacewiring (connection injected)

Your Database, Now With Batteries Included: Click-to-Attach Companion Apps

· 6 min read
FoundryDB Team
Engineering @ FoundryDB

You have a database full of tables. Now you want to see them. So you go find a BI tool, spin up a server for it, open a firewall rule, copy a connection string, paste in a host and a port and a username and a password, pick the right SSL mode, and after twenty minutes of yak-shaving you finally reach a login screen. Then you do it again next week when someone asks for a CMS, or a GraphQL API, or a no-code grid your ops team can edit.

That whole detour is now one click. From any FoundryDB database, click Add app, pick what you want, and the platform provisions a connected companion application for you. It auto-connects to your database over a private network with its own scoped credentials, serves it at its own subdomain with automatic HTTPS, and meters it like any other service. No config, no connection strings, no separate hosting to babysit. One click from data to a working app.

App-to-database attachment wiring
WIRED private SDN · app → database
App SDNprivate⇄ peeringDatabase SDNprivate⇢ :5432PostgreSQLfirewall + pg_hba
App SDN① SDN peering② firewall + pg_hba③ env inject + redeployDatabase SDN :5432private SDN traffic (dashed)