Credential HUB – an external credential layer for Flowise and other AI/automation tools

[luiscyphre404-cmd]

Hi everyone,

I’ve been working on an open-source project called Credential HUB, and I’d like to get some feedback from people running Flowise in real-world or self-hosted environments.

The problem I’m trying to address isn’t that Flowise cannot manage credentials itself.

It appears when the environment around Flowise grows.

A typical AI/automation stack can quickly involve credentials for LLM providers, APIs, databases, vector stores, MCP services and other external systems. Those credentials may be needed not only by Flowise, but also by automation tools, agents or other self-hosted applications.

At that point, credentials start becoming distributed across the individual applications.

Credential HUB explores a different model:

Provider / API → Credential HUB → authorized consumers

Instead of treating every application as a separate credential store, credentials are managed in a dedicated, self-hosted layer. Flowise could then be one authorized consumer alongside other applications.

The HUB manages the credential lifecycle and controls which consumers are allowed to resolve a credential at runtime.

The project currently includes:

• API token and OAuth-based credential management
• encrypted credential storage
• credential lifecycle/status management
• controlled consumer access
• deny-by-default credential resolution
• administrative import/export
• a web interface for credential and access management

Credential HUB is not intended to replace Flowise's built-in credential handling or a general-purpose secrets manager.

The question I'm interested in is whether separating credential lifecycle management from the individual AI/automation applications is useful in practice.

For example, if you use Flowise together with other tools:

How do you currently handle credentials that are needed across several applications?

Do you keep separate copies in each application, use an external secrets manager, or have another approach?

And would a dedicated credential layer between providers and applications solve a real problem in your setup?

There is currently no native Flowise integration. Before building one, I'd like to understand what such an integration would actually need to provide to be useful to Flowise users.

The project is open source and self-hosted:

[GitHub – Credential HUB](https://github.com/luiscyphre404-cmd/credential-hub)

I'd particularly appreciate feedback about the credential workflows you encounter in larger Flowise setups — including cases where this approach would not be useful.

Thanks and regards
Luis