Viewing profile — ozkatz

costs? 1PB of EBS volumes on sc1-class HDD is roughly $15k/month. Let's say you need at least 2 copies of each byte for cross-AZ availability and durability, that's 30k per PB for …

Curious if you’ve had a chance to try lakeFS? It was designed with large-scale environments in mind. I’m aware of several deployments managing hundreds of petabytes of data and bil…

That’s the current RBAC implementation: agents by default can make no API calls. the only way for them to contact the outside world is through a forward proxy configured in the san…

Appreciate the honest feedback. I agree there's a lot to improve there.

very very fast: proportional to the count of objects modified, but not their size. Every commit represents a snapshot - an immutable listing of objects that represents the reposito…

S3 offers versioning at the single file level. Imagine an agent dropping a directory with 1m images in it. just figuring out what happened and what got dropped, restoring it one by…

Regarding pricing - that's indeed a great question and we don't have an answer yet. It will very likely be based on consumption and should be competitive to similar solutions. Atom…

It uses lakeFS under the hood, so the unit of conflict would be a single file (object, under the hood). Resolving conflicts requires "picking" a winning side, or rerunning a confli…

It provides a filesystem abstraction, which agents are really good at interacting with. Because it's just a POSIX filesystem - you can put a sqlite database directly on it and get …

it should absolutely scale to that. The filesystem is backed by lakeFS, where every sandbox automatically branches out, and mounts that branch. so you get isolation from lakeFS and…

If that database is stored on the transactional filesystem available to the sandboxes, yes! Instead of backing up, it utilizes an efficient snapshot mechanism (lakeFS under the hoo…

Part of the appeal (subjective, I know) of versioning is stuff like human-in-the-loop approvals. Think of a pull request: a change is requested by an agent, a human approves, chang…

Hey! It doesn't necessarily have to be "data heavy", but any form of state (from code to binary files) that an agent might use for automation. Agents are really good at interacting…

Oh VMS, How I miss thee

In a perfect world, every system and external API would expose a standardized interface for versioning its own immutable state, so you'd be able to rollback and time travel across …

oz dot katz at treeverse.io would be best. ICP is SMB/mid-sized ISVs.

not at the moment. You can use lakeFS directly with Fuse-Mount to do something similar with your own compute.

Currently a static 2 cores and 4GB RAM, no GPU. Will be configurable soon!

Exactly that!

Much appreciated! and good luck with your project

https://www.youtube.com/watch?v=fDR8tmes020 - a 2 minute hands-on demo!

indeed - this only applies to the filesystem managed by tilde. Existing version control is fine if you're only managing code. For data (Think large parquet files, millions json fil…

The repository itself get fuse-mounted into the running sandbox - no skill or MCP required to interact with data: an agent can simply `cat ` and use whatever tools they are already…