Backed by Y Combinator

One memory for everytechnical domain.

Shepherd connects research, hardware, firmware, software, and operations in one shared memory your team can trace and your agents can act on.

SlackGranolaNotionGmailGoogle DriveGoogle DocsCalendarGitHubBitbucketConfluenceSchematicsClaude CodeCodexCursorLinearStripeSlackGranolaNotionGmailGoogle DriveGoogle DocsCalendarGitHubBitbucketConfluenceSchematicsClaude CodeCodexCursorLinearStripe

Shepherd learns while you work.

Every design review, experiment, message, and commit becomes shared memory across research, hardware, firmware, software, and the agents working with them.

Communications
Ishan thermal limit confirmed
Philip lab run moved to Thursday
research partner approved
Research
Materials review · alloy B selected
Optics review · new test plan
paper notes · failure mode found
Software & firmware
trace the sensor drift
control loop PR merged
fix the bootloader race
Hardware & systems
Rev C schematic review
HW-204 · vibration test
system requirements · 42 docs
Shepherd

Every technical domain, one memory.

Trace why a decision was made, see how it crossed disciplines, and give every person and agent the same context.

Trace decisions across domains

Ask in Slack, then use MCP to give Codex, Claude Code, and Cursor the full team context.

Shepherd
why did Rev C change the sensor mount?
Read 12:17 PM
The vibration run exposed resonance at 62 Hz. Research proposed the new geometry; hardware approved it Monday.

Research reaches implementation

See how research becomes implementation: from the Confluence spec to the schematic, firmware, and code.

Philip
updated the control firmware
2h
Ishan
closed the optics review
4h
Ankit
shared the new test protocol
1d

Open loops cross boundaries

Trace the Bitbucket change to its system requirement in Linear before it blocks the team.

noted three open loops
compare the simulation with the lab run
resolve the firmware issue from the test channel
update the system requirement

Make every domain compound.