Skip to main content

3 posts tagged with "directus"

View All Tags

Launch a SaaS Starter: A Backend in a Box on Your Own PostgreSQL

· 4 min read
FoundryDB Team
Engineering @ FoundryDB

Every product needs the same first afternoon of plumbing. Provision a database. Stand up an admin tool. Build sign-in and token issuance, or wire in a third party that holds your users hostage. Find somewhere to put uploads. Point a domain at it and get a certificate. None of it is the product you set out to build, and all of it has to exist before the product can.

The Launch a SaaS starter stack collapses that into one button. You get a SaaS backend in a box: your own PostgreSQL with a Directus studio over it, end-user auth, object storage, and a custom domain, wired together and EU-resident, in minutes.

saas-starter stack composition & launch
RUNNING Stack wired · SaaS backend live · EU
Stack Templatesaas-starterlaunch ⇉PostgreSQLDATABASE_URL → appFilesS3 creds → appDirectusadmin + REST / GraphQLEnd-user AuthOIDC issuerfront →Edge DomainTLS · auto certserve →SaaS BackendEU-resident
Template · launchPostgreSQLFiles bucketDirectus (SaaS backend)End-user auth (OIDC)Custom edge domainwiring (env injected)

Launch a CMS: A Headless Content Platform on Your Own PostgreSQL

· 4 min read
FoundryDB Team
Engineering @ FoundryDB

Standing up a headless CMS usually means a weekend. Provision a database. Pick a CMS. Wire it to the database with a connection string you paste into an environment file. Open a firewall rule. Mint an API token. Then, finally, model your first collection. The content platform you actually wanted was always one good afternoon of plumbing away.

The Launch a CMS stack collapses that into one button. You get a production headless CMS running on your own PostgreSQL, EU-resident, in minutes, with nothing to wire by hand.

CMS stack composition & launch
RUNNING Stack wired · headless CMS live
Stack Templatecmslaunch ⇉PostgreSQLdatabaseDirectusDATABASE_URL ← dbserve →Content APIREST / GraphQL
Template · launchPostgreSQL (database)Directus (headless CMS)wiring (DATABASE_URL 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)