An independent development studio.

From first spec to production.

The work starts with what the product needs to do. We turn that into a scope, design the interface and systems, implement the build and prepare it for launch. A project can start from a blank repository or from software that already exists.

Websites, stores, customer portals, internal tools and on-chain interfaces need different decisions. We choose the implementation around the requirements and the people who will operate it, rather than forcing every brief into the same stack.

Talk to the person building it.

Work directly with your developer. Reviews focus on what the product does, which decisions are still open and what is needed to complete the next part. Changes are discussed against a written scope.

A project needs clear ownership on both sides. We ask for an approval owner, usable source material and access to the systems involved. Unknowns are recorded and investigated before they become silent assumptions.

Full source. Full access.

You receive the custom source code and the agreed handover materials. The goal is a product you can operate and continue developing, with us or with another team.

Third-party components retain their own licences. Hosting, external services and ongoing support have separate responsibilities and costs. We make those dependencies part of the delivery discussion.

Your project stays out of our portfolio.

BRÈCHE never publishes or shares past client projects as references. No client names, screenshots, credits, results or case studies, including anonymised ones. Our public guides use fictional examples, never material taken from client work.

Your own product can launch publicly under your brand. We review its content, metadata and deployment choices against agreed confidentiality requirements. Our no-reference policy does not control records held by external providers.

Paid in crypto.

Development work is paid in crypto. The asset, network and payment milestones are agreed in the proposal. Your project does not need blockchain functionality to work with us.

Bring the requirements, the constraints and what you already have. The first useful step is a brief that makes the problem concrete.

Working notes you can use.

The guides are published under BRÈCHE. They cover scope, implementation decisions and handover, with worksheets you can download and edit. Technical references are linked where they support a claim. Their check date is recorded separately from the article's update date.

Examples labelled illustrative are fictional scenarios that explain a proposed workflow. They are not client projects, anonymised case studies, testimonials or measured business results. No client material is reused to produce them.

AI tools assist with drafting and implementation. That does not turn an example into experience or a local test into a production result. A project still needs its own requirements, verification and agreement.