Skip to main content

About BuilderStudio

We are building a canvas where the design, the logic behind it and the published site are one document.

What we build

Design tools stop at the picture. The tools that ship a real product start from an empty file. Everything between those two points gets rebuilt by hand, often by a different person. We are building a canvas where that gap does not exist: the layout, the logic behind it and the thing you publish are one document, so changing one changes all of them.

What runs today

We are pre-launch, so this is a description of what works, not a roadmap. The canvas editor is the core: an infinite surface where pages, components and the content behind them sit together. Publishing compiles a canvas into a real website. Astro export hands the same site back as plain source, so the work is never stuck with one vendor. An MCP server lets coding agents open the actual document and edit it, instead of guessing from a screenshot. API keys are scoped, so each key reaches only the tools and canvases it was given.

The company

The company behind the product is BuilderStudio. Product questions, access requests and press all reach a person at info@builder.studio, the same inbox the contact page delivers to. The privacy policy says what happens to anything you put on a canvas, and the subprocessor list names every outside service that can touch it.

Where to go next