-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Open
Labels
feature-requestNew feature request for Prowler.New feature request for Prowler.plannedIssues that are in Prowler RoadmapIssues that are in Prowler Roadmap
Description
New feature motivation
Currently, Lighthouse AI in Prowler is tied directly to the official OpenAI API.
However, multiple cloud providers (such as DigitalOcean and GitHub) now offer OpenAI models through their own platforms.
Supporting these alternative endpoints would:
- Increase flexibility
- Reduce vendor lock-in
- Potentially lower costs depending on the provider chosen
Solution Proposed
Introduce a configurable option to specify:
- The API base URL
- Provider credentials
This would allow users to seamlessly switch between OpenAI’s official API and other providers that expose the same model interfaces (e.g., DigitalOcean, GitHub).
Implementation suggestion:
- Use an environment variable or configuration file to define the provider endpoint.
- Maintain full backward compatibility with the current default (official OpenAI).
Describe alternatives you've considered
- Forking the codebase to hardcode alternative API endpoints – not practical, as it would make upgrades and maintenance difficult.
- Proxying requests through a middleware service that rewrites calls from Lighthouse AI to the desired provider – adds unnecessary complexity and infrastructure overhead.
- Sticking only with OpenAI official API – limits flexibility and ignores the growing ecosystem of compatible providers.
Additional context
No response
Chan9390
Metadata
Metadata
Assignees
Labels
feature-requestNew feature request for Prowler.New feature request for Prowler.plannedIssues that are in Prowler RoadmapIssues that are in Prowler Roadmap