Viewing a single comment thread. View all comments

doyougitme OP t1_ivol9ap wrote

Thanks for the feedback! That totally makes sense. I just added a pricing table to the login page as a quick fix.

21

ReginaldIII t1_ivqkw78 wrote

TOS > Prohibited Uses > 3. there's a typo on "Umpersonate"

I couldn't find a formal statement on your data policy for data uploaded to "uwstore", which I assume from your stack and how it appears in the notebooks is AWS EBS?

Do you give guarantees about data sandboxing between users? Have you penetration tested the ability to leak data out of another users environment or persistent storage.

Do you reserve the right to audit data a user has uploaded into uwstore or do you promise not to look at users data? This has a pretty big impact on what kinds of data people can process on your service as we often need a clearly written data policy to know we're operating within our rules of governance.

You allow Docker images, which is a nice feature, but are there size limits on images? You provide a build service based on a provided Dockerfile, how many cores / ram / local storage does that build process run on?

If I have pushed a (potentially large) image to a repository, and I base my Dockerfile FROM that image, is this allowed or do you have a set of curated base images we need to use?

Do you allow users to provide an access token so you can pull images from a private repository? If you've pulled a private image from a repository and it is now in the cache of your services, are other users able to base their Dockerfile's FROM that private image without providing an access token?

11