Launch HN: Rivet (YC F25) – Scale and Orchestrate Agents on S3

Re:Launch HN: Rivet (YC F25) – Scale and Orchestrate Agents ... by serjester on Thursday November 05, 2026 @07:18PM (#50386496)

Even as someone who’s very involved in the space, I don’t understand what you guys do. It’d be helpful if your website led with the problem you’re solving instead of technical benchmarks.

I also don’t really understand the distinction between an actor and an agent. I’ve never heard anyone call them actors, and I doubt you’ll win that mindshare as a small startup.

[ Parent | on HN ]

Re:Launch HN: Rivet (YC F25) – Scale and Orchestrate Agents ... by throwaway-blaze on Thursday November 05, 2026 @07:44PM (#50386706)

Man I was just coming here to say the same thing. I have a Ph.D. in CS and should be the target audience for this as a guy doing startup stuff that could easily try out a new architecture or tool.

I read "Rivet (https://rivet.dev) – a fast, high-density, and scalable orchestrator for agentic workloads using the actor model" and I think "I have no idea what this means, except it's a new way to make a backend service of some kind??"

I've reached an age where, if I don't understand what it is from your description, I'm not the problem.

[ Parent | on HN ]

Re:Launch HN: Rivet (YC F25) – Scale and Orchestrate Agents ... by ggsp on Friday November 06, 2026 @01:22AM (#50388852)

I’m likely not much farther ahead than you are in understanding exactly what Rivet does, as I learn by banging my head against the thing I’m trying to use, and so far all I’ve done is read.

“Actor” comes from established CS terminology [1], and agents-in-actors make sense in principle.

Agree with others in this thread that a few use-cases in the README would help me decide whether this is worth banging my head against or not.

[1] https://en.wikipedia.org/wiki/Actor_model

[ Parent | on HN ]