Galleon · Essay
The fleet was already there
Why Galleon returned as the shared home for Andrew Wilkinson's independent products, agents, games, and experiments.
A name with unfinished work in it
Galleon first flew over a DeFi protocol. That chapter had a company, a team, capital, products, and more than $20 million in TVL at its peak. When the DAO ended, the repositories became an archive—but the name and the instinct behind it never really disappeared.
The work that followed looked unrelated from a distance: a protocol intelligence product, a USDC off-ramp, a neighbourhood guide, a browser naval game, an editor theme, and increasingly capable agent systems. Up close, they already behaved like a family. They were independent, opinionated, operationally serious, and built because Andrew wanted the thing to exist.
An umbrella, not a product suite
Galleon does not ask those projects to pretend they solve one customer problem. Each name should lead with its own job. Peerlytics should look like protocol intelligence. KnowFulham should feel like a trusted local guide. Broadside should feel like a game.
The umbrella supplies something quieter: a known builder, a shared standard of care, a public address, and a way to understand how the experiments inform one another. The endorsement is simply “by Galleon”. It joins the work without flattening it.
The standard behind the flag
A Galleon project should do more than make a persuasive screenshot. It should have a working route into the product, an owner, an operating story, and honest evidence of its state. Agents can maintain and extend the work, but they do not dissolve responsibility.
The new Galleon is therefore less a corporate structure than a workshop standard: ship the whole loop, keep the owner visible, let projects stay themselves, and prefer evidence to theatre.