Setup ToolJet Managed AI Server with ToolJet Self Hosted
Self-hosted ToolJet instances can use ToolJet-managed AI instead of deploying a separate AI server. AI requests from your instance are sent over the internet to ToolJet Managed AI Server, authenticated with ToolJet-managed LLM credentials, and billed against your instance's AI credits.
See Setup ToolJet AI → Overview for how this fits alongside the other AI setups and how the request is processed end-to-end.
Prerequisites
- A ToolJet license with the AI feature enabled.
- Outbound HTTPS (443) access from your ToolJet server to ToolJet Managed AI Server.
Whitelisting Network Access
If your instance runs behind a firewall, proxy, or restricted egress policy, allow outbound HTTPS access to the following domains:
| Domain | Purpose |
|---|---|
https://api-gateway.tooljet.ai | Routes AI requests to the configured LLM provider |
https://python-server.tooljet.ai | Backs AI operations that require the Python execution service |
If your instance uses an HTTP proxy, make sure these domains are reachable through it.
Setup
- Confirm your license includes AI credits. If you need to purchase more, follow the Self-Hosted Deployment steps under Buy Add-on Credits.
- Whitelist the domains listed above in your firewall, proxy, or network egress rules.
- No further configuration is needed. AI features become available in your workspace automatically, billed against your instance's pooled AI credits.
Billing
Credits are pooled at the instance level for self-hosted deployments. See Understanding AI Credits for details.
Switching the AI Provider
With this setup, each user can pick which LLM provider powers their own AI chats. See Selecting an AI Model for details.
Switching to a Different Setup
- To use your own LLM API key while continuing to route requests through ToolJet Managed AI Server, see Setup ToolJet Cloud AI (BYOK).
- To keep all AI traffic entirely within your own infrastructure with no data sent to ToolJet Managed AI Server, see Setup ToolJet Enterprise AI.