Operations and Administration

Commissioning is designed for a fast start.

If the box is connected via network cable, it is directly reachable after switching on. Chat can then be used immediately.

If the box should be reachable via Wi‑Fi, a QR code leads to the installation assistant. The box is added to the network there. After that, you can work directly in chat and create the first agents or automations as needed.

All Indiebox applications run in separate containers. This makes operations easier because services can be managed independently of each other. Restarting or updating one application does not automatically affect the others.

Typically included:

• OpenWebUI as chat interface
• n8n for workflows, automation, and integrations
• Letta as agent environment if agents are used
• Own applications: an additional container for fully custom solutions

All containers can be controlled via the box dashboard and admin interface.

The dashboard is the central entry point for operations and diagnostics. It shows which applications are running, how the box is being used, and provides direct control.

Typical tasks covered there:

• Start, stop, restart applications
• Check status and utilization
• View logs to narrow down issues
• Manage box settings

This keeps normal operations in web interfaces. Daily work on operating-system level is not necessary.

Chat, workflows, dashboard, and administration are web interfaces. Access happens via browser, both on desktop and on mobile devices.

For mobile devices, OpenWebUI can also be used as an installable web app. It feels like an app, but technically remains a web interface.

If access from outside the local network is required, two clean approaches are common:

• VPN, so access works like in the internal network
• targeted release of defined endpoints through a local firewall, instead of exposing the box generally to the internet

Which option fits depends on the use case. The direction is important: internal is standard, external is deliberately enabled.

OpenWebUI and n8n are web applications. Users are created and managed there. Roles and permissions separate normal use from administration.

In a business context, login can be connected to existing systems. This is an integration point, not a startup obstacle.

n8n is the interface for workflows, automations, and integrations. Workflows consist of triggers and steps. This makes it understandable when actions are executed and where data flows.

n8n includes many connectors. A representative selection that is frequently used in daily work:

• Slack: Slack
• Microsoft Teams: Microsoft Teams
• Google Sheets: Google Sheets
• Jira Software: Jira Software
• Salesforce: Salesforce

The complete overview of integrations: n8n integrations

Important for operations: external integrations do not appear “by themselves”, but are deliberately configured in workflows.

Updates are triggered through the admin interface. Standard is manual start, so updates fit into a maintenance window. Automatic updates are possible on request.

Through container separation, applications can be updated independently. This reduces surprises: if an update affects only n8n, chat does not need to be touched at the same time.

Indiebox is delivered with several models for different tasks. This means the start is not “search for a model”, but “start the task”.

Preinstalled are:

• gpt-oss:120b for more complex tasks with high demand for reasoning and multi-step problem solving
• qwen3:30b for everyday tasks and automations
• qwen3-coder-next for coding tasks
• granite-embedding:278m for documents, search, and RAG (embeddings)

Disk space vs runtime: the decisive point is memory

With 2 TB storage, space for several models is usually sufficiently dimensioned for daily work. Less decisive is storage on disk, more decisive is runtime memory demand.

Indiebox is designed for systems with 128 GB shared memory. This is a practical advantage compared to classic GPU setups, which are often limited by GPU memory (VRAM). Through the large shared memory, even very large models in suitable quantization become realistically usable if the use case fits.

Load additional models (Ollama): deliberate and reversible

In addition to the preinstalled models, further models can be downloaded and integrated via Ollama.

Downloaded models are not part of the preconfigured Indiebox environment. Stability, quality, and suitability are therefore the responsibility of operations. The risk remains manageable because models can be removed at any time. This enables deliberate testing without permanently changing the system.

Indiebox bundles persistent application data in a central data area on the box. Within this area, data is separated by application. This is intentionally designed so backup and recovery stay simple.

In operation this means:

• Data and configuration are not distributed across many locations, but organized centrally.
• Backup can be implemented as a backup of this data area.
• Recovery happens via the installer: install base system, restore data area, start applications via dashboard.

At the core, data flow is simple:

1. Access
   Usage happens via browser or installable web app on Indiebox web interfaces (chat, workflows, dashboard).
2. Chat to the local model
   OpenWebUI forwards prompt and context to the model service on the box. The response goes back to OpenWebUI and is shown in the client.
3. Workflows to internal or external targets
   n8n executes workflows. Whether internal systems or external APIs are called depends on the specific workflow.

External services, MCP, and the risk from manipulated content

If the administrator enables external services, the box can access these services from inside to outside, for example for search or additional tools via MCP.

This increases possibilities but also brings a risk: content can be designed so that agents or automations are moved to unwanted actions. This is often described as prompt injection. It becomes critical especially when workflows have write permissions or execute actions without confirmation.

There is a configuration interface for network integration. Relevant settings are set there, without daily work on operating-system level.

As soon as the box is in the network and has a fixed name, a TLS certificate for HTTPS can be created or stored. This provides clean encrypted access in the browser.