Create your workspace yourself, in a few minutes
You no longer have to write to us to get started. Sign up with Google, Microsoft or a link sent to your inbox, name your workspace, pick its address, and it is yours. In French or in English.
What you can do today and could not yesterday — and what we repaired. A log that only ever announced novelties would read as advertising, and you would stop believing the rest of it.
You no longer have to write to us to get started. Sign up with Google, Microsoft or a link sent to your inbox, name your workspace, pick its address, and it is yours. In French or in English.
The site now says what the product does and what it asks of you: three pages on alignment, attention and authority, and a manifesto stating the seven disciplines the method demands — including the ones you can practise without us.
A page lists the databases that hold your objectives and every outside service the instance calls, with what is sent to each. It is derived from what the running instance actually has configured, so an integration that is switched off cannot appear on it, and one that is on cannot be left out.
It read « every customer has their own database ». That stopped being true for the free tier, which shares one, separated by workspace. The page now states the four levels plainly, free tier included.
The header collapsed on itself, the call to action broke across three lines, and the whole page scrolled sideways. It was a missing line in the stylesheet, and it made the first screen of every visitor on a phone look broken.
Your developers connect their assistant to Galy with one token per machine, revocable, and a page explains how. The assistant reads your strategy and writes its briefs, specs and after-delivery checks back into it. Galy never reaches into your code.
Inside your workspace, it shows what an agent observed of your setup — and only that. There is no box to tick: a self-assessment is an opinion, and this page does not display opinions.
For customers who get their own machine, provisioning no longer asks a human to open an administrator session on the database server. And the instance reads its secrets by name, from the store you already use, without knowing which one it is.
Internal corrections, refactorings and dependency updates. They change nothing for you, so they stay in the repository history where they belong. This page only carries what you can see.