About

Signals is the foundation.

weathership builds open-source infrastructure for federated engines, agents, and data products. Independent projects keep their own gRPC, models, and UIs. They attach to Signals over a shared protocol, scheduler, and warehouse.

The lattice

Each project is inspectable in source and documented as it ships.

Mission

To build durable, transparent infrastructure — systems whose behavior is inspectable, whose decisions can be traced, and whose failure modes are documented before they're hit. We release as open source by default because the systems we want to exist need to be reviewable by the people who depend on them.

Values

Open
The software ships under permissive licenses. The architectural decisions are written down. The trade-offs we made — and the ones we didn't — are visible to anyone who wants to read them.
Transparent
When we say a system does something, it does that thing. When it doesn't, the gap is named. We don't paper over uncertainty with confidence we haven't earned.
Durable
We optimize for the system that's still useful in five years over the demo that's compelling next week.

Origin

A weather ship was once a vessel stationed in open ocean for the express purpose of gathering atmospheric data — a floating instrument that turned uncertainty into signal so the ships following behind could plan their crossing. Signals plays that role for the rest of the fleet.

weathership was started by Ryan Hill in 2026 to hold related engineering threads under one umbrella. The projects predate the umbrella; the umbrella exists because they benefit from being held together.

Press, brand, and assets

The full media kit has the logo (SVG + PNG renders), color palette with copyable tokens, type system, usage guidelines, and press boilerplate. Everything on this site is downloadable.