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 raised, and products holding more than $20 million at their peak. When the DAO ended the repositories became an archive. The name did not go with them.
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 a growing set of agent systems. Up close it already read as one body of work. Independent, opinionated, run properly, 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 leads with its own job. Peerlytics should look like protocol intelligence. KnowFulham should feel like a trusted local guide. Broadside should feel like a game.
What the umbrella supplies is quieter: a known builder, a public address, and a way to see how one experiment fed the next. The endorsement is two words, “by Galleon”, set under a product name that stays larger than it is.
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; they do not dissolve responsibility for it.
What carries over from the first chapter is a standard rather than a structure: ship the whole loop, keep the owner visible, let projects stay themselves, prefer evidence to theatre.