BuildWithHQ
Canonical knowledge unit · architecture

Server-driven JSON presentation

BuildWithHQ represents pages and much application behavior as versioned JSON/schema interpreted by a shared runtime, enabling many application variations from a common codebase.

ID: BWHQ-ARCH-003Status: currentAuthority: highjsonpresentationrenderermetadata-driven

Server-driven JSON presentation

Principle

Pages, menus, components, data bindings, role visibility, workflows, actions, and configuration can be represented as JSON rather than compiled into a unique frontend codebase for every tenant.

Runtime

A shared renderer interprets the saved structure. BuildWithHQ can patch and secure the common rendering/execution engine while applications diverge through data/configuration.

Builder workflow

A builder can work visually, inspect or edit raw JSON, and use structured developer tooling. If JSON/schema is no longer the right abstraction, the next layer is an API/custom-service boundary rather than a forced platform ceiling.

Tenant customization

Tenant-specific page/layout overrides can exist without forking the whole platform. Presentation metadata can narrow visibility but must not be treated as an authorization boundary.

Related knowledge

Security invariantsSecurity is designed as a shared structural layer: server-derived identity, one authorization path, explicit tenant/application/location scope, and separate permissions for read, AI, export, and sensitive disclosure.API-first custom service boundaryDeveloper custom code runs behind declared, schema-validated API endpoints so BuildWithHQ can bind custom logic into pages, workflows, AI, and external APIs without exposing platform core IP or direct unrestricted SQL.
Machine-readable source: canonical Markdown. This HTML companion exists for human reading, search indexing, and AI retrieval.