Deployment
Local-firstThe fully local tier uses a local Ollama host. The hybrid tier deliberately sends selected hard tasks to a cloud API.
A local-first AI agent workflow for builders who are willing to manage their own hardware, models, permissions, and storage. Local software can avoid a recurring base subscription; hardware, electricity, and any cloud fallback remain separate costs.
Cost structure
Core software: Local software can start at $0 in subscription fees, but there is no zero-cost deployment: choose compatible hardware and a model before relying on this workflow.
Optional upgrades: Ollama Pro is $20/month for cloud capacity. A cloud API fallback is optional and token-priced; local sync or hosted deployment are separate choices.
Variable costs: Hardware purchase or depreciation, electricity, storage, backups, maintenance time, and any cloud-model/API use are not included.
Deployment and pricing boundaries checked against official product sources on July 28, 2026.
Decision profile
These labels describe the complete setup. They do not make a blanket privacy, licensing, or commercial-use claim for every component.
The fully local tier uses a local Ollama host. The hybrid tier deliberately sends selected hard tasks to a cloud API.
Review each model license, integration permission, data flow, and organization policy before business use.
Ollama can run local and open-weight models, but the stack also includes proprietary software choices and an optional hosted API.
Expect terminal setup, model and hardware selection, local storage planning, and careful approval of any agent or integration permissions.
The agent layer of the stack. OpenClaw can connect to a local Ollama host or a hosted model provider. Treat every skill, integration, and permission as a separate data-flow and security decision. See our OpenClaw ecosystem guide →
Use Ollama as the local model runtime. Its local mode can run models on your own hardware; cloud features are a separate choice with separate usage and privacy boundaries. OpenClaw and AnythingLLM can connect to the local API.
Use this layer only when you need document retrieval or a local workspace interface. Its desktop and self-hosted routes can connect to local models; choosing a cloud provider changes the data-flow boundary.
Use a local knowledge vault to keep files under your direct control. Optional sync and integrations are separate choices with their own storage and data-flow implications.
Use a cloud fallback only when a local model repeatedly fails on a task. DeepSeek API pricing is token-based, so cost depends on the selected model and actual input/output volume. Treat the fallback as an intentional exception to the local data boundary.
Open slot
Required. Choose a model that fits the available memory, storage, and desired task quality; model license and hardware requirements must be checked separately.
Every swap has a cost. Here's exactly what you give up — and whether it's worth paying to keep.
You lose: some model capability, speed, or context capacity on harder tasks
Start local, test the actual task, and add a cloud fallback only when the task repeatedly needs more capability than your chosen local model and hardware can provide.
You lose: cross-device sync and version history
Local-only Obsidian is the point of this stack. Skip Sync unless you need multi-device access — iCloud folder sync or a git repo are zero-cost alternatives.
Use this stack as the workflow map, then compare the core tools before you pay for them.