Very interesting. We’ve for sure felt the pain of large robotics images and slow deployments, especially when CUDA and ML dependencies are involved, or when adding a seemingly small ROS package pulls a long chain of transitive dependencies. The file-level deduplication approach is clever. Curious how transparent it is to existing Docker/OCI workflows. Does it require any changes to the client, or it mostly sits underneath the existing tooling?

It mostly sits underneath existing tooling. I replace the push/pull client (run `clipper pull` instead of `docker pull`, and optionally the BuildKit driver (to get build outputs natively in my format). That pull command ingests the image into your chosen runtime, meaning your docker/podman/k8s run commands remain the same. If you're interested I can set up a demo/call/coffee.

Remote video streaming is relevant. Please free to send us an email.

Thanks, YC launches have helped quite a bit with drawing attention. We're hoping HN will pronounce it more.

I'm impressed with your two other capitalists in addition to YC getting involved.

On first impression of course, but they don't seem like your run-of-the-mill VCs who often have much more money than brains.

Boston Dynamics vs Salem Statics, haha. Seriously though, we are very complimentary to BD, since Spot is one of the platforms we deploy on.

Cofounder here. we're based in Austin, TX, but yes, the name alludes to Salem MA. We're bringing inanimate objects to life through robotics, haha.