A working tool is not only meant to produce files. It also helps keep together everything that surrounds creation: ideas, sources, drafts, attempts, decisions, mistakes, quickly written notes and links we promise ourselves we will read later. A living project is never perfectly tidy. It moves through fragments, returns, detours and revisions.
The problem begins when all those fragments scatter.
A note in one app. A PDF somewhere else. An excerpt in the browser. A piece of code in a folder. An idea in a forgotten file. A resource in a lost tab. Over time, it is not only organization that suffers. The thinking itself becomes fragmented.
Panaches was born from that tension.
The idea is not to create one more tool to fill one more window. The idea is to build a local workshop where several gestures can coexist: searching, writing, coding, reading, annotating, organizing, comparing, drawing, listening, documenting, understanding. A space where the work is not artificially separated from its sources, methods and memory.
This vision is also linked to control.
When data goes everywhere, when each step depends on an external service, when tools impose their own rhythm, the creator loses part of their freedom. Panaches aims instead to preserve a workspace that is more personal, more readable, closer to the project and to the people building it.
The software is one part of that idea. The media space is another.
Through articles, resources, guides, workflows and shared methods, Panaches wants to become more than an application: a place of circulation between people who create, learn, build and transmit. A place where we do not only talk about tools, but about ways of working, researching, organizing and bringing something into existence.
Creation needs tools. But it also needs a space where ideas can stay alive long enough to become something.
Panaches is trying to build that space.
