One editor for{' '}
{
@@ -44,7 +46,7 @@ const flagship = [
))
}
- — in your browser, with SSO built in.
+ — in your browser, in your cluster, or inside your own product.
diff --git a/src/components/sections/ManifestoSection.astro b/src/components/sections/ManifestoSection.astro
new file mode 100644
index 0000000..dcd2bbe
--- /dev/null
+++ b/src/components/sections/ManifestoSection.astro
@@ -0,0 +1,149 @@
+---
+import SectionHeader from './SectionHeader.astro';
+
+// The five consequences of the belief. Each is a row of the `manifesto` table
+// in sections.ts (rows: 5) — keep the two in step if either changes.
+const consequences = [
+ {
+ belief: 'It runs in a browser',
+ consequence:
+ 'Because the data is not on your machine, and neither are your teammates. A tool that has to be installed is a tool that half the team never opens.',
+ },
+ {
+ belief: 'It reaches a phone',
+ consequence:
+ 'Because the incident that needs a query does not wait for you to open a laptop. The same editor, the same connections, on the screen you already have with you.',
+ },
+ {
+ belief: 'It deploys like infrastructure',
+ consequence:
+ 'A container, a Helm chart, an OpenShift operator, a one-click template on your platform. The way everything else that sits next to a database gets installed.',
+ },
+ {
+ belief: 'It embeds',
+ consequence:
+ 'One npm package, inside your own product. The most useful place for a database editor is the thing that created the database in the first place.',
+ },
+ {
+ belief: 'It holds nothing back',
+ consequence:
+ 'Single sign-on, ER diagrams, the AI assistant and the NoSQL engines all ship in the MIT build. There is no edition where the useful parts live.',
+ },
+];
+---
+
+
+
+
+
+ Open source · MIT · nothing held back
+
+
+
+
+
+ The tool goes to the data. Not the data to the tool.{' '}
+ Everything else about LibreDB Studio follows from that one line — including the licence.
+
+
+
+
+
+
+
+ Forty seconds, then an afternoon
+
+ You create a Postgres on a managed platform. It is ready in forty seconds. Then you want to look inside it —
+ so you open a port to the internet, dig an SSH tunnel, or install a desktop client on every machine that needs
+ one. The database took forty seconds. The window into it takes the rest of the day.
+
+
+
+ Now multiply it
+
+ The team runs Postgres for the application, Mongo for documents, Redis for the cache, ClickHouse for the
+ events. An engineer joins on Monday and spends their first days working out which data lives where, hunting
+ connection strings, waiting on access, and installing a different tool per engine.
+
+
+
+
+
+
+
+
+ Databases moved. They live in Kubernetes now, on managed platforms, in a customer's VPC reached through a jump
+ host. The tools that read them did not move. They are still desktop applications: heavy, licensed per seat,
+ install-first, built on the assumption of one database, one laptop, and one person who never changes machines.
+
+
+
+
+
+
+
+ {
+ consequences.map((c) => (
+
+ {c.belief}
+ {c.consequence}
+
+ ))
+ }
+
+
+
+
+
+
MIT is not generosity. It is a requirement of the architecture.
+
+ You cannot place a per-seat licensed, feature-gated tool into every environment you own. The moment single sign-on
+ costs extra, the tool stops being deployable by default.
+
+
+
+
+
+
Then why is Platform paid?
+
+ Because it is a service rather than an environment. LibreDB Studio is MIT because it
+ has to go everywhere. LibreDB Platform is hosting, tenancy, billing and support for
+ teams that would rather not run Studio themselves.
+
+
+ The line holds under pressure, which is the point. The editor you deploy is free and stays free. No capability is
+ moved across that line to manufacture a reason to upgrade.
+
+
+
+
+
+