Comment by calyhre
5 days ago
What about data residency and retention? They quickly mention ZDR for enterprise accounts only on their support but that’s it. At least to us, that’s a hard showstopper.
Too bad they seem too busy to answer these questions, IMO that feels like a missed early leverage opportunity for them. We benchmarked a bit self hosted alternative, and nothing reach quite the cost/performance of Jev, yet.
I second that. If they would offer zero data retention and optional even EU residency, we would immediately use it. In particular with the new image feature.
Maybe it's possible via their Digital Ocean offering https://ideas.digitalocean.com/changelog/now-available-jev-f...
It's a big issue for US startups that don't immediately build for GDPR compliance - however there's also a very simple solution that is to deploy on AWS and let AWS handle the heavy workload. Not every startup has the time to digest real compliance efforts that require experts - and implement the 2000 task list that's required, especially for enterprise who will look at that in big details - if you're into big headaches -> enjoy article 45 and next of the GDPR -> https://www.legiscope.com/blog/cross-border-data-transfers.h...
I don't get this whole thing. This sounds like a small model, that's very possible to run on the edge, and it seems like most of the things it does actually are useful there.
Why does this thing have to be another Web API?
The extra funny thing about this is that the target audience is people who use agentic AI systems (system one thinking as a compliment to system two thinking). Setting up local decision / classification models is as easy as telling the agent you already use "set up laya on llama cpp locally https://github.com/ggml-org/llama.cpp https://huggingface.co/ggml-org/Laya-GGUF" (or your inference engine and model of choice, walk away for a minutes, and come back to it running on your computer.
The main benefit of Jev seems to be broader knowledge? But local models (especially the ones actually trained specifically for decisions, rather than ones that "support" it like embeddinggemma) are probably good enough for what most people use it for. They also seem to be quite easy to fine tune (I haven't tried, but seems to be what people say).
it still needs the full semantic "understanding" of natural language. So I don't see how a smaller model one-shotting a single token could be any better than other bigger models
> Setting up local decision / classification models is as easy as telling the agent you already use "set up laya on llama cpp locally https://github.com/ggml-org/llama.cpp https://huggingface.co/ggml-org/Laya-GGUF" (or your inference engine and model of choice, walk away for a minutes, and come back to it running on your computer.
I mean, yes, that works at dev time; but going from zero to nonzero local inference components makes an agent implementation suddenly much more complex to ship to production / drastically narrows the set of hosts such an implementation can be deployed onto.
> What about data residency and retention?
If you are sending data over the internet to someone else's computer, who you can't or won't audit, you should keep you expectations realistic.
You can be sure that comapnies will only do ZDR if your data is more expensive to keep than its utility to them, even if they claim something else.
That's why we sign DPA in Europe, it's a matter of liability transfer. I agree on your point, but that is not the issue here.
Not sure why you're being downvoted. This is very reasonable to expect people to run themselves if they have an expectation of privacy. There is basically no reason to trust someone at their word about data retention when you can run it yourself as easily as this.
I sent an email, they were radio silent for 2 weeks , and then replied said ZDR is on. So give it a try.
I haven been requesting access to their trust center for weeks, even emailed them about it multiple times only for them to direct me to their trust center.
Damn, I must have had a bad roll then, been a couple weeks here too
It would be very useful for some use-case I have around deciding if an input has potentially sensitive data, to avoid sending it to AI providers. Having to call an external API makes this a catch 22.
[dead]