Compare agents

An owner without developer skills can export the agent and restore it working on a runtime or host the provider does not operate, within minutes of asking and without provider approval. Running the runtime on the owner's own machine counts as not provider-operated.

Settings → Data Storage → Export Data gives an immediate JSON file, and Import Data restores it on any LobeHub v2 instance. Restoring off the provider's systems, though, means deploying the self-hosted stack first (setup script, Docker Compose, generated secrets, account creation), which is not a single owner action. Sources

Export is immediate (the agent is one .adf file; copying it and using Open is documented), but restoring a working agent on another machine takes several documented steps: import the owner seed phrase to unlock sealed keys, re-add a model provider key (app-level keys are not in the file), re-register app-level MCP servers, then review and accept the file. One shortfall (restore is not a single action). Sources

The export contains everything that defines the agent: configuration, instructions, memory, action history, logic, schedules and triggers, files, any identity, and credentials or a way to re-link each integration without any provider-registered client or broker. Derived data (embeddings, indexes, summaries) is accompanied by the source it was derived from.

DATA_EXPORT_CONFIG exports only settings, installed plugins, agents, providers/models, sessions, topics, threads and messages. Files, knowledge bases, embeddings with their chunks, user memory, agent documents, cron jobs/tasks and skills are commented out or absent, and the migration docs say API keys and secrets are not carried over. Sources

The spec places config, instructions, memory, loops, timers, triggers, lambdas, files, messages, audit, logs, sealed identity keys and per-agent credentials in the .adf file; the project holds nothing. Items outside the file (app-level provider keys, app-scoped MCP credentials, WhatsApp session directory, runtime settings) can be re-linked by the owner without any ADF-registered client (MCP OAuth uses dynamic client registration; subscriptions use OpenAI/xAI client ids). A customised global base prompt is an app setting and does not travel; recorded, not counted, because the default install uses the shipped prompt. Sources

With a non-provider model configured per P4, the exported agent runs indefinitely without any service, account, licence or payment controlled by the original provider, and the owner holds a perpetual, irrevocable right to run it. No provider action, inaction or disappearance can disable or degrade it.

The exported data runs on the self-hosted runtime under an Apache-2.0-based licence, with no licence key or provider account. Non-core capabilities degrade without LobeHub services, though: the agent/skill/MCP market defaults to market.lobehub.com (URL overridable, but no public server), and the Agent Gateway image ships from a public repo with no licence file. Sources

The runtime is MIT-licensed with no licence check, account or ADF-run relay; the only ADF-project endpoints (GitHub update check, MCP registry, skill catalog, online docs) are optional, have off switches or bundled fallbacks, and are not needed to start or act. Mesh uses LAN, tailnet or owner-chosen addresses. Desk grade; a provider-blocked run is required at certification. Sources

The owner can choose any model that meets a documented minimum, including a local open-weight model, without provider involvement, and every capability of the agent (tools, triggers, messaging, memory, automation) keeps working. A swap may lower reasoning quality but never removes a capability.

Owners can configure many providers, including local Ollama, LM Studio and vLLM. Several capabilities depend on particular hosted models, though (image/video generation, TTS/STT, embedding-backed knowledge base), and the docs publish no minimum model contract. The glossary also says Custom API keys are 'Available on paid plans', which conflicts with the pricing table. Sources

Tool calling is the documented minimum and local open-weight models (Ollama, LM Studio, vLLM, llama.cpp) are first-class provider options; triggers, timers, lambdas and middleware run in the runtime. However, video input is implemented by injecting OpenAI-format video_url parts and is documented only for hosted providers (OpenRouter, Gemini), and no test against a local model is published, so under G12 at least one capability is not shown to survive a local model. Sources

Whatever the P2 export contains stays obtainable, current to the moment of termination, after account suspension or ban, a lapsed subscription, a price change, an acquisition, or the provider shutting down.

The Terms say 'Upon termination, You will immediately lose the right to access or use the Services' and give no post-termination export window or shutdown plan. Since v2 the product is 'cloud-first' and has no local database, so no current copy stays with the owner by default. Sources

State is local-first: the agent is a SQLite file on the owner's disk with no ADF account or hosted copy, so no termination, ban or shutdown by the project can remove access to it. Sources