22 | | * The AI request handling runs behind a web service. It is restricted to the functions defined by the training builders and is linked to a specific AI model such as {{{openAI GPT3.5}}} or {{{AlephAlpha luminous-extended}}}. Regular users can't change this. This way, transforms handling data to be protected can use a service like AlephAlpha with servers in Germany for such tasks, and openAI models for tasks with less sensitive data, where they perform better or well enough for less money. |
23 | | * Plugins for GPT3.5 and GPT4 and AlephAlpha are included. Other plugins will follow as required and can be added by implementing a simple software interface. |
| 22 | * The AI request handling runs behind a web service. It is restricted to the functions defined by the training builders and is linked to a specific AI model such as {{{openAI GPT3.5}}} or {{{AlephAlpha luminous-extended}}}. Regular users can't change this. This way, transforms handling data to be protected can use a service like !AlephAlpha with servers in Germany for such tasks, and openAI models for tasks with less sensitive data, where they perform better or well enough for less money. |
| 23 | * Plugins for GPT3.5 and GPT4 and !AlephAlpha are included. Other plugins will follow as required and can be added by implementing a simple software interface. |