Skip to main content

2 posts tagged with "nocodb"

View All Tags

Launch a No-Code Database: NocoDB on Your Own EU-Resident PostgreSQL

· 5 min read
FoundryDB Team
Engineering @ FoundryDB

Spreadsheets are how most teams actually model their work. A table of customers, a tracker of orders, a board of tasks. The tools that make this delightful, the Airtables of the world, give you a grid you can edit by hand and an API you did not have to write. What they do not give you is the database. Your data lives in someone else's product, in a shape you do not control, behind an export button.

Today you can have both. Launch a no-code database stands up NocoDB, the open-source Airtable alternative, wired to your own PostgreSQL. The editing experience is the spreadsheet you wanted. The thing underneath is a real SQL database, in your own account, resident in Europe, that you can query, scale, and back up like any other.

No-code database stack · compose & launch
RUNNING Stack wired · no-code grid + REST API live
Stack Templatenocode-dblaunch ⇉PostgreSQLmanagedNocoDBNC_DB → dbserve →No-code UIgrid + REST API
Template · endpointPostgreSQLNocoDB appwiring (NC_DB 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)