open-webui
Open WebUI LicenseBranding rules apply from v0.6.6; earlier code and small deployments have different terms.
Source ↗AGIWORK / FIELD GUIDE
A practical guide to the layers, choices and tools behind an enterprise AI platform — from a first experiment to managed operations.
Start small. Add capability only when a real requirement justifies it.
THE IDEA / FROM MY REFERENCE ARCHITECTURE
I use this map to separate the jobs an AI platform has to do: serving people, connecting models and knowledge, controlling access, and operating safely. The toolkit below is an adapted selection from my enterprise AI ecosystem catalogue.
You do not need every component. Begin with a defined use case and add layers as data sensitivity, users and operational requirements grow. The stages are a learning path, not a maturity certification or a prescription.
01 / ARCHITECTURE MAP
This is a functional map, not a required deployment topology. Each area links to examples and decisions in the toolkit below.
Identity, permissions, evaluation and oversight span the entire system. Components within a category are often alternatives, not a shopping list.
02 / A LEARNING PATH
I group tools by the work you are doing. Some tools serve several stages; a later stage is not automatically better.
Explore models, a simple interface and a small task.
Explore starting points ↗02Add agent logic, documents, retrieval or media only as needed.
Agents & knowledge ↗03Connect services and models with explicit access and controls.
Connections & safety ↗04Evaluate, monitor and govern the system as usage grows.
Operations & governance ↗03 / TOOLKIT
Official project links are starting points for evaluation. These projects overlap and evolve; check current releases, compatibility, maintenance, security and licence terms before adoption.
Browse my full directory by architecture role, from personal assistants and coding agents to models, knowledge and operations.
Give people a useful way to interact with a model and learn from a small, bounded use case.
MY TAKEStart with one interface and one model. A self-hosted interface does not automatically make an external model or its data processing private.
A self-hosted interface for models, tools, knowledge and configurable agents.
Source-available; review licence and branding terms.Agent & workflow automationVisually build workflows and AI agents that connect to services.
Fair-code; review the Sustainable Use License.Local model runtimeRun supported models locally for experiments and development.
Model licences are separate.AI chat interfaceA multi-user chat interface and integration starting point.
Check edition and deployed version.Prototype UIBuild a simple web interface for a model or Python function.
Check dependencies and hosting.Web UI libraryBuild a custom web interface for AI applications.
You provide the application and its security controls.Shared learning environmentProvide multi-user notebook environments for learning and exploration.
Configure user isolation and resource limits.Learning platformOrganise courses, learning content and activities.
Review extensions and operational requirements.Visual workflowsConnect events, APIs and services in low-code flows.
Review third-party nodes.Build a single agent or workflow with an explicit task, tools, state and clear boundaries.
MY TAKEA model runtime, an agent framework and a workflow engine have different jobs. Choose the simplest fit; multi-agent coordination is not a prerequisite.
Configure assistants and connect models, tools and knowledge through a self-hosted interface.
Source-available; review licence and branding terms.Agent & workflow automationCreate AI agents and automated workflows with visual building blocks.
Fair-code; review the Sustainable Use License.Personal agent platformRun a personal assistant that connects models, tools and messaging channels.
Review workspace permissions and access to connected accounts.Personal agent platformRun a tool-using assistant with persistent context, skills and messaging integrations.
Review skills, tool access and the selected model provider.Personal agent frameworkBuild or run a lightweight personal agent with tools, memory and chat integrations.
Review exposed tools, credentials and deployment settings.Agent libraryA lightweight Python starting point for tool-using agents.
Code-executing agents require isolation.Visual agent builderCompose AI and agent workflows through a visual interface.
Review community and commercial editions separately.Agent frameworkPython agents with typed inputs, outputs and validation.
Check model and provider terms.Stateful orchestrationBuild stateful, controllable agent workflows.
Review related service editions.Multi-agent frameworkCoordinate agents and tasks where roles and handoffs are useful.
Review core and hosted offerings separately.Agent toolkitA code-first toolkit for building and evaluating agents.
Cloud integrations may have separate terms.Give development agents a bounded workspace to inspect code, propose changes, run tools and support delivery.
MY TAKEA coding agent combines a model with an execution harness and tools. Compare workspace permissions, model access, review workflows and data handling before adoption.
Use an open coding agent to work with a codebase from developer interfaces.
Check provider terms and execution permissions.Coding agentWork with an agent that reads, changes and tests code through a terminal and other integrations.
Review Anthropic service and workspace permissions.Coding agent & harnessUse OpenAI’s coding agent across app, CLI, editor and programmatic workflows.
Open-source harness and hosted services have separate terms.Coding agent toolkitUse an extensible terminal coding agent or its agent toolkit as a building block.
Inspect extensions and configure appropriate execution boundaries.Agentic development environmentUse ZCode’s agent to work with files, commands, models and development tasks.
Review product, provider and data-handling terms.Agentic development platformUse agents in development workflows across an editor, terminal and browser.
Review access, availability and product terms.Agent harnessAssemble plugin-based agent workflows with sessions, tools and a web interface.
Review plugins, model access and permissions before use.Terminal coding assistantPair with an AI assistant to edit code in a local Git repository.
Review model-provider terms and changes before merging.Turn approved source material into searchable evidence that an application can cite.
MY TAKEFor RAG, check extraction quality, access permissions, retrieval relevance and source freshness. A vector database is not an access-control system by itself.
Convert supported documents into structured content; OCR options are available.
Check OCR engines and model licences.Data integrationMove supported data from sources into destinations for processing.
Check connector and edition terms.OCRRecognise text in images and scanned pages.
Quality depends on source and language data.Vector searchAdd vector similarity search to PostgreSQL.
A pragmatic option when PostgreSQL is already in use.Vector searchA dedicated vector search engine.
Compare filtering, operations and scale requirements.Vector databaseVector search infrastructure for larger deployments.
Distributed deployment adds operational work.Search engineExplore full-text and vector search for retrieval.
Check version, plugins and operational requirements.Graph databaseModel and query relationships as a graph.
Community and enterprise editions have different terms.RAG frameworkCompose retrieval and AI pipelines from components.
Evaluate retrieval and answers separately.Add media processing or adapt a model when the problem actually requires it.
MY TAKEStart with existing models and a test set. Fine-tuning, visual workflows and transcription introduce additional compute, data and model-licence decisions.
Transcribe speech with supported open model weights.
Review model and data terms.Audio & video processingProcess and convert supported audio and video formats.
Enabled libraries and build options affect licence obligations.Visual media workflowsCompose node-based image and other media workflows.
Extensions and models carry their own terms.Model trainingTrain or fine-tune language models with supported methods.
Requires data, evaluation and compute planning.Synthetic dataExplore synthetic tabular data generation.
Synthetic data is not automatically private; evaluate disclosure risk.Route applications to approved local or external models, and select serving infrastructure appropriate to demand.
MY TAKEOllama is a useful local starting point. vLLM and KServe address different serving and deployment needs; benchmark on your own hardware and models.
Run and serve supported models locally for applications and development.
Review each model’s licence and hardware needs.Model gatewayA proxy and unified interface for supported model providers.
Review version, edition and integrations.Inference servingServe supported models with an inference engine and API.
Check hardware and model compatibility.Inference servingA runtime for serving supported generative models.
Benchmark with your workload.Model serving on KubernetesServe and manage model workloads on Kubernetes.
Requires Kubernetes operations.Connect approved systems through controlled interfaces, and make long-running actions observable and recoverable.
MY TAKEMCP is a protocol, not a security boundary. Use least-privilege credentials, approval for consequential actions and isolation for untrusted execution.
A specification for connecting applications to tools and context.
Review each server, permissions and transport.Skills specificationA portable format for packaging agent instructions and supporting resources.
Treat external skills as untrusted until reviewed.Durable workflowsCoordinate long-running workflows and recovery.
Design idempotency and human review.MessagingMessaging infrastructure for services and event-driven systems.
Protect identities and network access.IsolationMicroVM technology for isolated workloads.
Isolation requires secure configuration and operations.Protect access to the platform, models, data and tools using several complementary controls.
MY TAKEIdentity, secrets, authorization, data protection and AI guardrails are separate layers. No prompt filter alone prevents every injection or data leak.
Manage identity and access for applications.
Integrate with existing identity policies.Secrets managementManage secrets and encryption with identity-based access.
Plan deployment and recovery.Policy engineEvaluate policies separately from application code.
Define and test enforcement points.Sensitive-data protectionDetect and help anonymise sensitive information.
Detection is imperfect; test on your data.AI guardrailsAdd programmable controls around LLM applications.
Combine with application security and evaluation.Test both useful behaviour and failure modes before expanding access or autonomy.
MY TAKECreate a representative test set and inspect retrieval, answers, permissions, unsafe tool calls and regressions. Human review remains important for consequential actions.
Evaluate prompts and test LLM applications for security risks.
Review configuration and data sent to providers.LLM vulnerability probingProbe language models for a range of failure modes.
A scan is not a guarantee of safety.Supply-chain scanningScan supported software artifacts and dependencies.
Use alongside patching and review.Make model calls, tool use, latency, errors and operational costs visible to the teams responsible.
MY TAKETracing may contain sensitive inputs or outputs. Minimise logged data, control access and define retention before using production data.
Track experiments, models and supported AI traces.
Check deployment and access controls.LLM observabilityInspect traces and evaluate LLM applications.
Review self-hosted and commercial features.TelemetryCollect and process supported traces, metrics and logs.
Avoid logging unnecessary sensitive data.MetricsCollect and query operational metrics.
Metrics complement traces and logs.DashboardsVisualise and investigate operational data.
Review the licence and deployment edition.Assign owners and policies to data, models and services; make adoption and cost decisions reviewable.
MY TAKEA data catalogue, a policy engine and a cost monitor support governance but do not create compliance by themselves. Controls depend on the organisation and jurisdiction.
Catalogue data assets, metadata and lineage.
Define owners and classification processes.Cost visibilityMeasure Kubernetes workload costs and allocation.
Not a complete model-token billing system.Artifact registryStore and manage container images and other supported artifacts.
Review provenance and access policies.Artifact signingSign and verify supported software artifacts.
Use with a defined trust policy.LICENSING / IMPORTANT DISTINCTION
I track the licences and product terms for the projects in this architecture and my agent directory. A repository licence does not automatically cover hosted services, dependencies, models, weights or datasets. Check the exact version and use case.
Project licence sources checked 2026-10-29. Standard labels reflect the reviewed root licence and GitHub's identification; exceptions and uncertainties are stated explicitly.
Branding rules apply from v0.6.6; earlier code and small deployments have different terms.
Source ↗Community and enterprise code have different terms; hosted access, white-labeling and client workflow editing require review.
Source ↗Additional conditions address multi-tenant service and frontend branding.
Source ↗The platform directory uses Polyform Shield; other repository portions use MIT.
Source ↗Modified Apache terms restrict some hosted or embedded third-party offerings; review branding conditions.
Source ↗Synthetic Data Service use is restricted; each release transitions to MIT on its change date.
Source ↗The published terms restrict commercial use unless a qualifying subscription or separate agreement applies; check section VI.
Source ↗The Codex repository uses Apache-2.0; OpenAI services, models and subscriptions have separate terms.
Source ↗Filter by project or licence type. This is a starting point for reviewing the actual terms, not a licence grant or a substitute for checking the relevant artifacts.
181 records
Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review source and licence obligations when distributing covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Review the restrictions in Elastic License 2.0, including limits on managed services.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Code and documentation are licensed separately; review the relevant files.
Source ↗The platform directory uses Polyform Shield; other repository portions use MIT.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗The README states MIT, but its linked root licence file was not found in this check.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The main licence is AGPL-3.0; browser patches and other components may have separate licences.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The repository licence reserves rights and refers to Anthropic commercial terms.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review source and licence obligations when distributing covered software.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Functional Source License applies first; each version changes to MIT on its specified change date.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Additional conditions address multi-tenant service and frontend branding.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗The README states MIT, but its linked root licence file was not found in this check.
Source ↗Licence obligations depend on the enabled components and build options.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Most code is Apache-2.0; enterprise directories and specifically marked files have commercial terms.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The repository licence restricts commercial use; verify the exact scope.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Service and enterprise access may be subject to different Google agreements.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The project offers a choice between MIT and Apache-2.0; check the version and included components.
Source ↗Retain required notices and observe the non-endorsement condition.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The README states MIT, but its linked root licence file was not found in this check.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗MIT applies outside the enterprise directories; those directories have separate terms.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗The root licence distinguishes MIT code from enterprise-directory terms.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The specification repository is transitioning licences; documentation and some contributions have different terms.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review source and licence obligations when distributing covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Modified Apache terms restrict some hosted or embedded third-party offerings; review branding conditions.
Source ↗Community and enterprise code have different terms; hosted access, white-labeling and client workflow editing require review.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices and check licence terms for models and third-party components.
Source ↗Review source and licence obligations when distributing covered software.
Source ↗The community licence includes a revenue threshold and competition restrictions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Most repository content is MIT; enterprise directories have separate terms.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Branding rules apply from v0.6.6; earlier code and small deployments have different terms.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗The Codex repository uses Apache-2.0; OpenAI services, models and subscriptions have separate terms.
Source ↗Review file-level source obligations when distributing modified covered files.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Both licence files are present; verify the terms for the component and release you use.
Source ↗Review source and licence obligations when distributing covered software.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Most repository content is MIT; the enterprise directory has separate terms.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗The README states Apache-2.0; a root licence file was not found in this check.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Permissive licence; retain the required copyright and disclaimer notices.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Use of the product is governed by Poolside’s end-user agreement.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Synthetic Data Service use is restricted; each release transitions to MIT on its change date.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗The repository covers documentation and press materials; the application has separate terms.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Retain required notices, mark changes and review the patent provisions.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Keep the copyright and licence notice when distributing copies.
Source ↗Review distribution and network-source obligations for modified covered software.
Source ↗The published terms restrict commercial use unless a qualifying subscription or separate agreement applies; check section VI.
Source ↗No records match. Try another search or type.
GitHub’s licence identification checks a repository licence file; it does not assess dependencies or every component. How GitHub identifies licences ↗
04 / PRACTICAL GUIDE
These patterns are starting points to investigate, not tested integrations or production-ready blueprints.
Start with a small set of permitted documents. Parse and inspect them, index content for retrieval, and build an answer workflow that can cite sources.
Example components: Docling + pgvector or Qdrant + Haystack. Enforce user access at retrieval; test relevance, citations, stale data and unsupported answers.
Explore knowledge tools ↗Define the task, permitted tools, stopping conditions and a human approval step for consequential actions. Start with read-only access where possible.
Example components: an agent framework + approved APIs or MCP tools + a workflow engine when durability is needed. Isolate code execution and review external tools.
Explore agent frameworks ↗Record the owner, intended users, data classification, model/provider, permissions, evaluation set and operational budget before broader use.
Before expansion: define access control, rollback, monitoring, incident response, data retention and a review process for versions and licences.
Explore operations ↗Goal: answer a bounded set of questions using only documents the requester is allowed to access.
Goal: introduce a model or agent tool through a reviewable process before wider deployment.
CHOOSING A STARTING POINT
Vector search: pgvector can fit an existing PostgreSQL deployment; a dedicated engine such as Qdrant or Milvus may be worth evaluating for different scale, filtering or operational needs. Test with your own corpus and permissions.
Model hosting: Ollama supports local experimentation; vLLM focuses on serving inference; KServe manages model serving on Kubernetes. These solve overlapping but different problems.
Open software vs. open weights: a permissive code licence does not automatically cover model weights, datasets, plugins or provider services. Check the exact versions and intended use.
External skills and tools: inspect and pin versions, test in isolation, and approve them before promotion to an internal catalogue. Limit runtime permissions and log consequential tool use; a registry is not a substitute for review.
CONTINUE EXPLORING
For a wider view of agent tools, explore my public directory. For an architecture conversation, connect with me.