When using AI, LLMs, and GPTs, especially when using external services, consult your CISO, DPO, and Legal. At the very least go over all the fine prints!
AI, LLMs, and GPTs will most likely, or even already are, part of processing data in general. Whether it is applicable to your own use cases or not, myDRE is designed to be able to do the work that must be done.
While anDREa is no expert in this field, we do use it ourselves, and more importantly, we recognize you may want to experiment or use AI, LLMs, and GPTs yourself. And as always, we offer options:
- Deploy and utilize it fully from within your Workspace
- Connect securely to external services
Why use myDRE?
Locally: quick access to resources, less red tape
If you want to deploy 'local' AI, LLMs, or GPTs you need resources. myDRE of course provides quick access to the resources you need. Further more, because it is in a trusted environment, not only you need to worry less about security and privacy challenges, the organisation knows that the work is contained and this should reduce the amount of red tape.
External services: receiving and prepping data, collaboration, demonstrable compliant
In case you want to interact with services external to myDRE, this is often possible by allow listing (sub)domains. But why do you want to do this? You still need a trusted environment in which a data custodian is willing to issue the needed data into. You might need to prep the data before submitting it to the external service. You still need to receive outcomes. Especially when working in collaboration, it makes sense to use a trusted environment for this.
Overview
Supported
- External to myDRE
- Julius AI
- Perplexity.ai
- Within myDRE Workspace
- GPT4All
- Host ALL your AI locally
Not (yet) supported
- ChatGPT
- Under investigation, it requires mtalk.google.com on ports 5228, 5229, and 5230, non-standard http(s) ports are currently not supported.