InferadaDocsPortal
Guides

Managed Apps

Provision supported chat and workflow applications for your organisation, preconfigured to use its Inferada models.

What you get

From Organisation → Apps, select an application and choose Provision. Servada creates a dedicated instance on its own subdomain and connects it to the models configured for your organisation.

Servada manages the application infrastructure, updates, and gateway credentials. The application retains its own account and permission system.

Available applications

Choose the application that matches the task your team needs to perform:

OpenWebUI
Chat

A chat interface for models configured in Inferada.

Users can select a model, keep conversation history, upload files for question answering, and use prompt libraries.

Flowise
Workflow Builder

Build chatbots and multi-step AI workflows visually.

Connect prompts, document stores, models, and other components in a visual flow builder.

n8n
Workflow Builder

Add model calls to broader business automations.

Connect AI steps with databases, email, messaging services, APIs, and other n8n integrations.

Open and administer an app

Once an app shows as running, click Open to launch it in a new tab. Use Reveal credentials to retrieve the initial administrator login. Add users and manage permissions within the application's own account system.

Automatic gateway configuration

With Auto-create a token enabled, the provisioned application receives a gateway connection and credential:

  • OpenWebUI: the gateway is the default OpenAI connection. Pick a model and start a conversation.
  • n8n: an Inferada (default) OpenAI credential is created for the admin user. Both classic OpenAI nodes and the AI / LangChain nodes share this one credential type. Select it on a node, then choose a model.
  • Flowise: the same Inferada (default) credential is created, and the container's OPENAI_BASE_URL defaults to the gateway. Use the OpenAI Custom Model (or OpenAI Embeddings Custom) node, select the credential, enter a model ID, and leave Base Path blank.

If credential creation fails during provisioning, add it manually with the same name and inf_… token.

Choose a token owner

An automatically created token belongs to the user selected under Token owner. The token appears in that user's API tokens list for review and revocation.

Select a member of the organisation that owns the app. This keeps token management with that organisation. Destroying the app revokes its automatically created token.