About BRÈCHE.
BRÈCHE is an independent web development studio at breche.dev. We design and build custom websites and web applications for international clients, with direct collaboration from the first brief to source code handover.
Your product. Your code.
Julxoo, CEO of BRÈCHE
Julxoo writes BRÈCHE's development guides on project scope, implementation decisions and software handover. They are written for people commissioning or taking over software, with technical detail where it helps them check the work.
Use the worked briefs and downloadable worksheets to define a project. Run the integration example to inspect how duplicate events can produce one task. All examples are created for the guides and use fictional data.
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.
How these guides are put together.
Each guide starts with a decision: what to include in a brief, when custom code is justified, or how to tell whether a handover works. The answer comes first, followed by examples, checks and the assumptions behind them. Julxoo signs the guides; BRÈCHE publishes them.
Official documentation supports provider-specific claims. The Sources section records when those references were checked. An article's update date changes when its content changes, not each time the site is rebuilt. Platform behaviour and account permissions should still be checked for the project at hand.
Illustrative scenarios use fictional organisations and data. Runnable examples include their own checks and explain what they omit. Neither is a client case study. AI tools assist with drafting and implementation; no generated biography, testimonial or client result is used as evidence.
If you find an error, email breche.dev@proton.me with the guide URL, the passage and a source or reproduction. Do not include private project material.
From first spec to production.