FlowFuse Assistant for Self-Hosted

[knolleary]

Description

Original FF Assistant Epic: #4073

Our current FF Assistant implementation is FFC only.

We need an agreed strategy for making it available to self-hosted customers. This epic is to figure out how to do that.

The current implementation works like this:

• The FF platform is configured with a url and token of the assistant service.
• The assistant service is running as a NR instance in FFC - using OpenAI keys we manage and pay for.
• The assistant makes api calls back to its local FF platform, which proxies the request to the assistant service.

For a self-hosted customer to use the assistant, they would need to update their flowforge.yml to provide the url/token to access the assistant service.

Some open questions to address.

1. Do all self-hosted customers use the same hosted assistant service end point?
2. How do we manage/provision additional api tokens for self-hosted? Should this just be part of the license? If so, how to validate the license in the assistant service.
3. Do we need to apply any quotas or limits on use of the api to avoid misuse?

Which customers would this be available to

None