Bauwerk seems like a cool way to automate dev work. I like that it runs on my own hardware and handles the whole pipeline. The autonomy options are handy, though I wish pricing was listed.
Questions about Bauwerk
What is Bauwerk?
Bauwerk is a self-hosted software development pipeline tool that uses AI agents to automate implementing, testing, building, and deploying code from plain-language task descriptions. It runs on the user's own hardware and integrates with existing repositories through a configuration file, supporting projects such as iOS and Node applications. The product provides multiple autonomy levels and allows users to approve merges at a pull request gate, or enable automatic merging and deployment, including submission to TestFlight for iOS apps.
How does the Bauwerk pipeline operate from task to production?
The process begins by pointing Bauwerk at a repository using a tiny .bauwerk/config.json file to define how to test, build, and ship. Users then file a task, which can be a one-line instruction or a full epic that opens refinement first to nail down scope before coding. Agents claim the task and run the pipeline in parallel across isolated git worktrees, streaming real-time logs to the board over SSE. Finally, users review and ship by approving at the PR gate or enabling Full Auto merge and deploy, with iOS apps going to TestFlight and others opening a PR with an auto-written changelog.
Who is the ideal user for Bauwerk and what specific control does it offer?
Bauwerk is designed for teams that need visibility and control over the full development pipeline rather than just code generation. It suits projects requiring self-hosted runners on their own hardware to keep source, secrets, and build artifacts under their direct control. The tool supports multiple autonomy levels, allowing users to choose between Full Auto, PR Gate, or Manual approval per task based on their trust level.
What specific technical features and autonomy levels does Bauwerk provide?
The tool includes four distinct pipeline stages: implement, test, build, and deploy, each streaming live to the board. It features three autonomy levels for user intervention and supports three or more project types including iOS, Node, and custom adapters. The system runs tasks in parallel by default, isolating them per project to drain backlogs efficiently without sequential bottlenecks.
How can a user get started with Bauwerk?
Users can create an account directly on the website to access the self-hosted autonomous dev pipeline. The platform allows spinning up AI agents on local hardware to execute tasks without external dependencies. The entire workflow is managed through a single pipeline that handles everything from prompt to production on autopilot.
How does Bauwerk ensure data security and local execution?
The tool is 100% self-hosted, meaning the runner executes entirely on the user's own hardware. This ensures that source code, secrets, and build artifacts never leave the user's control. The architecture is built to keep all data and processes local, avoiding cloud-based execution for the core pipeline stages.
How does Bauwerk maintain transparency during the development process?
The system provides real-time visibility by streaming logs straight to the board over SSE, eliminating any black box in the process. Users can watch every step live as agents write changes, run test suites, archive, sign, and upload artifacts. This transparency allows for immediate verification of each phase from implement to deploy.
What project types and deployment targets does Bauwerk support?
The platform supports iOS applications by automatically submitting builds to TestFlight, as well as Node services and any project with a custom adapter. It handles the entire lifecycle including archiving, signing, and uploading, not just generating a diff. The system creates a paper trail with auto-written changelogs and a PR for every change that lands.
How does the autonomy control feature work in practice?
The tool allows users to set autonomy levels per task, ranging from Full Auto to Manual. This flexibility lets users hand over exactly as much control as they trust, with no more. The PR Gate feature specifically allows users to approve merges before automatic deployment occurs.
What specific examples of tasks or features are shown on the Bauwerk board?
The website mentions a dark mode feature that can be added to Settings, demonstrating its customization capabilities. The platform also references a board running interface where tasks like adding dark mode to SettingsView.swift are tracked and executed.
How does Bauwerk handle concurrent tasks across multiple projects?
The system runs tasks in parallel across projects using isolated git worktrees, ensuring that one project does not block another. This parallel execution model allows the backlog to drain efficiently rather than processing tasks one by one.
What configuration file is required to connect a project to Bauwerk?
The tool requires a configuration file named .bauwerk/config.json to define testing, building, and shipping parameters. This file is essential for connecting a project and telling the agents how to interact with the repository.
How does Bauwerk manage scope definition before implementation?
The platform includes a feature where epics open refinement first, ensuring the scope is nailed down before any code is written. This step prevents scope creep and ensures that the implementation phase starts with clear objectives.
What is the official website of Bauwerk?
The official website of Bauwerk is bauwerk.dev.
How is Bauwerk rated on Trustburn?
On Trustburn, Bauwerk has a rating of 4.3 out of 5 based on 4 reviews.
AI-generated from reviews on this page. Verify anything important with the company directly.
Bauwerk distinguishes itself by managing the entire pipeline from implementation through to deployment, rather than just generating code diffs. The three autonomy levels—Full Auto, PR Gate, and Manual—allow granular control over where human intervention is required. Running on local hardware ensures source data never leaves your control. The parallel execution across isolated git worktrees suggests efficient handling of multiple projects, while real-time logging via SSE provides necessary visibility without a black box effect. This structure supports a rigorous workflow for iOS and Node environments.
The self-hosted model is appealing. I wonder about the subscription tiers since pricing isn't listed.
Bauwerk offers a self-hosted dev pipeline that runs agents on your own hardware. The implementation to deployment flow is clear, but pricing details are not explicitly listed on the site. It seems robust for teams wanting control, though the lack of cost transparency is a minor drawback for early adopters.
News
No news yet. This is where the business shares its own updates and press.
Photos
No photos yet. Photos shared by reviewers will show up here.
Widgets
Get the widget for your site →About Bauwerk
Bauwerk is a self-hosted software development pipeline tool that uses AI agents to automate the process of implementing, testing, building, and deploying code from plain-language task descriptions. It runs on the user's own hardware and integrates with existing repositories through a configuration file, supporting projects such as iOS and Node applications. The product provides multiple autonomy levels and allows users to approve merges at a pull request gate, or enable automatic merging and deployment, including submission to TestFlight for iOS apps. Bauwerk positions itself around offering visibility and control over the full pipeline rather than code generation alone.
- Website
- bauwerk.dev
- Categories
- Computer software