Launch HN: Hebbian Robotics (YC S26) – Build scalable robotics data pipelines

44 points by kstonekuan 14 hours ago on hackernews | 12 comments

dostick | 13 hours ago

How robitics may be “scalable”?

pelagicAustral | 13 hours ago

Build a software implementation, lets call it The Matrix. Feed it to unknowing organic vessels, lets say Humans. Make it so they existence is a soothing mixture of comforting (fabricated) reality and inorganic desires. Extract power from these vessels. Make more robots. Profit.

[OP] kstonekuan | 12 hours ago

Our users process thousands of hours of data used in robotics model training, that's when they need scalable infrastructure to handle the workloads

hnvd8v0o2d | 13 hours ago

Filing this away

pj_mukh | 11 hours ago

Super cool! How do you think you will want to sell these into robotics teams, I find so many core engineering teams in Robotics companies have a "we'll just build it ourself" attitude around tools like this.

Have you had luck cracking past that?

[OP] kstonekuan | 11 hours ago

We have had this same experience, and it's a big reason we chose to go open source and make it easy for teams to migrate their business logic onto our SDK instead of requiring them to adopt a new system. By targeting a more foundational layer, we aim to be a part of that "built it yourself" system instead of replacing it.

a_t48 | 10 hours ago

This is a strategy I’m taking as well. Build the tooling that can be integrated into anyone’s platform, over some all in one system that inevitably won’t check all the boxes.

[OP] kstonekuan | 9 hours ago

Yes, especially in a field moving as fast as robotics, users need the flexibility to extend the system quickly

ZeroCool2u | 11 hours ago

I'd be interested in using this with something like the new HuggingFace robots. Do you have demos showing how to go from HFlow dataset to training to deploy?

[OP] kstonekuan | 10 hours ago

Love those robots! Unfortunately, we don't support the training and deployment side yet as we are focused only on data processing for now.

heyitsguay | 3 hours ago

Creating a basic ergonomic example of the full train/deploy loop, using your data engine, for a popular platform in the zeitgeist, will give you a traction boost.

You don't have to innovate on the parts outside your core competency. Have your favorite LLM ingest the Reachy docs, give it control of a robot, and put a lightweight example together. Iterate till you like the example flow and you've purged docs and output text of AI slop, then release!

[OP] kstonekuan | an hour ago

Thanks for the advice, we'll definitely consider an example like this.