Runtime overview
The navigation demo’s Dashboard shows request count, memory use, CPU activity and uptime.
A native, declarative full-stack web development systemMade with HyperBricks
Describe, build and dynamically serve your web applications with one native binary.
HyperBricks is a native development tool with shared conventions for humans and agents. Compose your application from reusable components and HTML templates, then build, serve, inspect, edit content and deploy through one integrated workflow.
YAML describes your application using reusable components: your HTML templates define the markup; fill them with Markdown, data from APIs and content you edit through Spaces. Use template functions for presentation logic. Add application logic through server-side JavaScript or native plugins.
HyperBricks bundles your frontend assets and serves pages and HTML fragments. Use its browser tools to inspect the application and edit content, then deploy it as a running application or export it as static HTML.
Beta software. Features, configuration, and APIs may change. Read the project status.
HyperBricks is easy to install:
INSTALL HYPERBRICKS / v1.3.2-beta
curl -fsS https://hyperbricks.eu/install.sh | shInstalling on Windows?
Using HyperBricks on Windows is not recommended yet. The full regression test suite has not yet been run on Windows. And please note that native Go plugins require WSL2 or Linux. Platform details
Want to help test HyperBricks on Windows? Try the command below and share your feedback.
irm https://hyperbricks.eu/install.ps1 | iexFOR HUMANS AND AGENTS
Shared conventions for humans and agents
HyperBricks configuration is declarative: you describe which components your application uses, how they connect and what they render. The complexity of fetching data, running application logic and presenting results lives in dedicated layers: API integrations, native plugins and templates. Separating implementation logic from application composition preserves a clear structure and makes components easier to reuse, replace and combine.
As agents write more code, shared conventions and integrated tools become more valuable. HyperBricks gives humans and agents the same declarative components, schemas and validation tools. Its VS Code extension connects to the built-in language-server for diagnostics, completion, hover documentation, go-to-definition and formatting, using the runtime parser and component schemas.
Get the VS Code extensionAgents can use these tools without VS Code. The linter checks YAML syntax and source style; Doctor checks the module. Both return JSON diagnostics, so an agent can check its changes against the project’s rules and use the results to correct them.
hyperbricks lint -m my-app --json
hyperbricks doctor -m my-app --jsonFor diagnostics, completion and hover during editing, an agent with a compatible LSP client can start the same language-server using hyperbricks language-server --stdio.
FROM YOUR TERMINAL
Discover the HyperBricks CLI
See what you get when you install HyperBricks. This recorded session walks through a starter’s files, command help, deployment options, diagnostics and settings, then starts the application.
Recorded with HyperBricks v1.3.2-beta. Use the timeline to explore; the session ends with the server running. Download the recording.
YOUR DEVELOPMENT WORKSPACE, INCLUDED
Monitor, edit content and deploy from within your browser
In developer mode, HyperBricks gives you a dashboard to inspect your running application and investigate rendering errors. Spaces adds CMS-like content editing, with editable fields defined by your page composition. You can author and preview content within the structure you’ve built. A separate deployment interface lets you build, package and deploy your application.
INSPECT & DIAGNOSE
Dashboard & Errors
Dashboard lists your application’s routes and shows requests, memory use and CPU activity. When a page fails to render, Errors identifies the component, source location and resource involved, so you can find the configuration that needs changing.
Application routes
Browse the routes registered by this module, check their component types and open a page from the list.
Rendering diagnostics
A missing template produces a diagnostic with the affected component, source location and resource path.
EDIT & PREVIEW
Spaces
Create pages that inherit a shared layout, each with its own content, URL and metadata. You declare which fields can be edited; Spaces provides the browser interface. Changes are saved to your project files, so content and application code can be versioned together.
Editing a page
This German café page inherits its layout while keeping its own title, route and content.
Source-defined fields
The source defines these text, email and Markdown file fields, including their labels and groups.
Editing a Markdown document
The visitor guide has unsaved changes. Save Shared Document writes them to the file; Known references shows where it is used.
Markdown preview
Preview renders the edited Markdown so you can check its formatting before saving the document.
BUILD & DEPLOY
Deployment
Package your application as a runtime archive, try it locally and push it to your server. The deployment interfaces let you manage builds, start and stop applications, inspect their status and edit their configuration. Keep previous builds available when you need to roll back.
Build and package
Keep source modules and packaged builds together. Start a build locally, push it to a configured target or download its runtime archive.
Inspect a running deployment
The remote interface shows the active build, its runtime mode and port. Expand its details to inspect exactly what is running.
Configure each build
Open a build’s package configuration directly from the deployment interface. Review runtime settings before saving changes.
START WITH SOMETHING REAL
Try the demos
Run examples and explore their source code.
HTMX · API DATACatalog & cart
HTMX · FRAGMENTSTo-do app
API DATA · STATIC HTMLCoffee from an API
SWUP · TRANSITIONSPage navigation
ARCADE · TYPESCRIPTNeon Pong
Prefer Turbo or Unpoly? Browse all modules
FAQ
Frequently asked questions
Does HyperBricks require a specific frontend framework?
No. HyperBricks returns HTML pages and fragments and does not require a specific frontend framework. You can use plain browser JavaScript, HTMX, or another library. You choose your frontend tools.
Can I keep my own frontend tools?
Yes. Your templates define the HTML, and you supply CSS and browser JavaScript. Templates use Go html/template with Sprig functions. The integrated esbuild component bundles JavaScript, TypeScript, and CSS. It does not install npm dependencies or type-check TypeScript.
How do Spaces and Markdown work?
A Space inherits a page source and supplies its own route, title, content, and metadata. The source declares which fields the development editor may change. Markdown renders inline content or a declared resource file inside a page or fragment. Saving content requires a separate build or deployment to publish it.
What are my deployment options?
Export your configured site as rendered HTML and assets, including a ZIP archive. For dynamic applications, run HyperBricks and deploy module archives. Local and remote web interfaces support building, pushing, activation, logs, and process controls. Native Go plugins must match the runtime that loads them.
What does the development interface include?
The development interface has three sections: Dashboard, Spaces, and Errors. Dashboard provides development tools, Spaces edits declared page fields, and Errors shows render diagnostics. Spaces is a development editor; it does not provide production authentication.
Is HyperBricks ready for production?
HyperBricks is currently in beta. It is suitable for evaluation, prototypes, and controlled deployments, but features, configuration, and APIs may still change. Test your application against the exact runtime version you deploy and plan for upgrades before relying on it for production-critical workloads.
BETA STATUS
HyperBricks is under active development. Features, configuration, and APIs may change as the project evolves. The project is released under the MIT License and provided “as-is,” without any warranties or guarantees.