v0.8.0 — why Studio exists, ten engines, and a commercial support commitment

The site said what Studio does — never why it exists

The hero stated a category, "The Modern, AI-Powered SQL IDE", that any competitor could claim word for word, and no page carried the story at all.

A new manifesto table under the studio schema now does, at /manifesto: the two scenes the project started from, the belief that the tool goes to the data, the five things that belief forces — browser-based, deployable, embeddable, unrestricted — and the MIT licence as a consequence of the architecture rather than a gesture. It follows the visual rhythm of the existing manifesto section, so it reads as part of the site rather than bolted on.

The hero now leads with the claim instead of the category: the database editor that deploys next to your data instead of onto your laptop.

We were underselling by three engines

src/data/engines.ts exists specifically to stop engine counts drifting across surfaces — its own comment says so. The array had stopped at seven: Couchbase, ClickHouse and Apache Druid were missing from the hero, the JSON-LD, the keywords and the get-started copy. Three more strings bypassed the array entirely and hardcoded "7+" into SEO descriptions.

Fixed at the source, so every derived surface corrects itself. A new test fails on any section copy that spells out an engine count, which makes the drift non-recurring.

Commercial support, in writing, behind a named vendor

grep -ri "commercial support\|rancher\|rke2\|k3s\|suse" src/ returned nothing — while LibreDB is already listed in the SUSE Partner Certification & Solutions Catalog. The new /support section closes that gap:

• Vendor of record — legal entity, address and company-information link, all derived from company.ts, so the page cannot drift from the footer, the privacy policy or the JSON-LD.
• Supported platform versions — Kubernetes, K3s, RKE2, Rancher and OpenShift, plus container and Node.js runtimes. Mirrors the table in docs/RANCHER.md, including its Supported/Validated split: a — means "same support terms, no published test run yet" rather than implying a run that never happened.
• What support covers — installation and upgrades, configuration, defect fixes, security patches — and how to reach us.
• JSON-LD — a Service node whose provider carries the same @id as the vendor Organization, so a crawler resolves support to a legally identified company.

The page is deliberately platform-neutral rather than SUSE-specific: the commitment is the same wherever Studio runs.

A Rancher card on /deploy

public/logos/deploy/rancher.svg was already in the repo, unused. It now appears under Kubernetes & orchestration, linking to docs/RANCHER.md, with rancher/rancher stars. Status is available, not official — install today is a ClusterRepo pointing at our chart repo; it flips to official once the chart ships in Rancher's own Partners repository. A test pins that, so the flip has to be a deliberate change.

Toolchain and docs

Astro 7.1.5, @astrojs/check 0.9.10, oxlint 1.76.0. The README's deployment story was wrong — it implied pushes to main deploy; production is gated on publishing a release, and it now says so.

Full changelog: v0.7.4...v0.8.0