Welcome
How to plan, build, test, release and maintain a project in Zuse Bifrost, and how to reach it over the API, webhooks and MCP.
Zuse Bifrost is where Zuse Technologies plans a client project once and then builds, tests, releases and maintains it against that same record. A Business Analyst captures the scope, the people, the requirements and the rules; developers, testers and release managers work from that record rather than from copies of it; clients approve and sign off inside it; and every phase, from the first epic to the last incident review, points back at the artefacts it touched.
This site is the complete guide to the product. The Product Guide describes every page as a person uses it, phase by phase. The three reference sections describe the same record as a machine reaches it: the REST API, the outbound webhooks and the MCP server for coding agents. Integrations covers GitHub, pipelines, Telegram and email.
Start here
What Zuse Bifrost is
The five phases, the one record they share, and who does what in it.
REST API
Mint a token, read a project, create a story, receive the event.
MCP server
Hand a coding agent the project's record and let it write back.
Webhooks & events
Signed deliveries for every change, with retries and replay.
How is this guide?
Last updated on