kgva CMS
7f6bedebdc
rapport: trimmed the competitor-positioning paragraph and the tools-i-wanted framing, just the feature list and the free/self-hostable facts now.\n\ndossier: reflects that it left the rhino plugin behind and is now its own standalone desktop app (own geometry kernel, own rust/wasm rendering engine, own file format), instead of the old rhino-vs-open-source-cad justification.\n\nopenbureau: reframed as the platform the other two are built on rather than just a collection point for finished tools, and named as still taking shape.
16 lines
1.1 KiB
Markdown
16 lines
1.1 KiB
Markdown
---
|
|
title: "openbureau"
|
|
description: "open and self-owned tools for architecture"
|
|
build:
|
|
render: never
|
|
list: never
|
|
---
|
|
|
|
architecture runs on tools. the tools shape what gets thought, drawn, and built. most are proprietary: subscriptions that can be cancelled, file formats only their owners can read, work that disappears when a license lapses. in a profession that already runs on precarious labor, that's rent extraction.
|
|
|
|
free and open source software is the cleanest answer, but not the only one. what i'm after is ownership and openness. tools you own instead of rent. file formats anyone can read. data that doesn't sit behind a paywall. code as a commons when possible. when it isn't, at least open data.
|
|
|
|
openbureau is that position turned into a platform — still taking shape. dossier and rapport are the first pieces built on it: tools written for my own practice, released so other people can use or fork them.
|
|
|
|
beyond what i build, openbureau is also a service: i curate open-source software that carries no fixed costs and no lock-in, set it up, and support it, so a studio or small practice can run on tools it owns instead of subscriptions it rents.
|