Self-hosting & bring your own key
FlowLens doesn't require you to route your workflow data through a shared AI service you don't control. This guide covers pointing FlowLens at your own provider, or keeping everything on your own infrastructure.
Design placeholder: setting names and commands below are bracketed placeholders. Swap in the real configuration before publishing.
Why it works this way
Workflow JSON often contains the shape of your actual business logic: which systems talk to which, what triggers what. That's not something every team wants living in someone else's analytics pipeline by default.
Data flow with your own key
Your platform
n8n · Zapier · Make
FlowLens
History + diffs
Your provider
Your key, your cost
Nothing requires a shared, FlowLens-operated AI service.
1. Choose a provider
Point FlowLens at any of these. Pick one to see its example configuration.
2. Run FlowLens on your infrastructure
If you'd rather not send workflow data to a third-party model provider at all, the self-hosted path exists for exactly that reason. Pair it with a self-hosted model and nothing leaves your network.
Deploy: [DEPLOY COMMAND]
Set your model endpoint to your own OpenAI- or Anthropic-compatible URL.
Connect your platform: cloud or self-hosted n8n connects the same way. n8n setup →
What FlowLens never does on its own
Apply a fix
Suggestions are proposals. You review the diff before anything touches the live workflow.
Require a shared AI service
Your key, your usage, your cost, or a model you host yourself.