From aa50cca899a0edc949400fbbb9938680c063be1d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Be=C3=B1at=20Espi=C3=B1a?= Date: Fri, 9 Oct 2026 16:05:59 +0200 Subject: [PATCH 1/2] feat: one database is what Bounda needs, not a ceiling The fact named the React Router integration and OpenTelemetry, which sell the packages around Bounda rather than Bounda. It now says what the one database holds and that a read model may still have a database of its own. --- src/components/landing/facts.astro | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/components/landing/facts.astro b/src/components/landing/facts.astro index 2f37350..e2ec996 100644 --- a/src/components/landing/facts.astro +++ b/src/components/landing/facts.astro @@ -17,8 +17,8 @@ const facts = [ }, { label: "One database", - title: "Runs where you are.", - body: "PostgreSQL, SQLite or libSQL. On Cloudflare, one Durable Object per tenant holds the whole domain, driven by its alarm. React Router integration and OpenTelemetry.", + title: "Nothing else to run.", + body: "Events, read models and the work still pending share one PostgreSQL, SQLite or libSQL database, or one Durable Object per tenant. One is all it takes, not all it allows: a read model can have a database of its own.", }, ]; --- From 21dc326c0ca470c0e89ac81673b4ce827db99840 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Be=C3=B1at=20Espi=C3=B1a?= Date: Fri, 9 Oct 2026 16:05:59 +0200 Subject: [PATCH 2/2] feat: say what the one database holds, not which ones --- src/components/landing/facts.astro | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/components/landing/facts.astro b/src/components/landing/facts.astro index e2ec996..83bbfe0 100644 --- a/src/components/landing/facts.astro +++ b/src/components/landing/facts.astro @@ -18,7 +18,7 @@ const facts = [ { label: "One database", title: "Nothing else to run.", - body: "Events, read models and the work still pending share one PostgreSQL, SQLite or libSQL database, or one Durable Object per tenant. One is all it takes, not all it allows: a read model can have a database of its own.", + body: "Events, read models and the work still pending share one database. Start there; when a read model outgrows it, it gets a database of its own.", }, ]; ---