- Home
- Getting Started
- Account & Settings
- Roles & Add-On Access
- Settings
- White Label
- Operations
- Agentic & Architecture
- Overview
- AI Models & Runtimes
- Data & RAG
- AI Assistants
- Security & Governance
- Agents & Engines
-
Agents
- Overview
- Custom Agents
- Core Agents
- Core Agents
- Matrix Agent
- Audit Agent
- ETL / Parser Agent
- Reconciliation Agent
- Router / Triage Agent
- Critic / Linter Agent
- RAG / Knowledge Agent
- Analytics / Query Agent
- Scheduler / Planning Agent
- Notification / Alerting Agent
- Industry Agents
- Industry Specific Agents
- Patent Agent
- Customs Agent
- Compliance Agent
- Construction Agent
- Contractor Agent
- Real Estate Valuation Agent
- Litigation Agent
- Contract Audit Agent
- Clinical Audit Agent
- UTS Compliance Agent
- Fleet Ops Agent
- Financial Audit Agent
- RevOps Agent
- BOM Audit Agent
- EHS Compliance Agent
- Engines
- Add-On Modules
- Agriculture
- Automotive & Fleet Management Ops
- Construction
- Customs & Global Trade
- Ecommerce Operations
- Education
- Energy
- Financial Audit & Fintech Ops
- Government
- Healthcare
- Hospitality
- Insurance
- Legal
-
Manufacturing
- Manufacturing
- Overview
- Work Orders
- Production Scheduling
- Shop Floor Monitor
- OEE Dashboard
- Production Counters
- Secure File Sharing
- Plant & Process Setup
- Work Centers
- Bill of Materials
- Manufactured Products
- Work Instructions
- Quality Operations
- Overview
- Inspection Plans
- Quality Checklist
- Non-Conformance (NCR)
- SPC Charts
- Traceability (4M)
- Maintenance Operations
- Overview
- Asset Registry
- Preventive Maintenance
- Work Orders
- Spare Parts
- Reliability Dashboard
- Inventory Operations
- Overview
- Material Staging
- WIP Tracking
- Kanban Replenishment
- Material Consumption
- Assets
- Asset Health
- Patent & R&D Operations
- Real Estate
- RevOps
- Enterprise & Technical
-
Enterprise Operations
- Enterprise Operations
- Overview
- Enterprise Operations Guide
- Compliance & Docs
- Overview
- Approval Workflow
- Expiry Reminders
- Document Control
- Audit Trail
- Compliance Radar
- Contracts & Warranty
- Overview
- Active Contracts
- Warranty Check
- Service Billing
- Field Service
- Overview
- Dispatch Board
- Job Management
- Van Inventory
- Performance Dashboard
- Service Desk
- Overview
- Service Requests
- SLA Monitor
- Knowledge Base
- Procurement & Vendor
- Purchase Orders
- Vendor Portal
- RFQ Management
- QHSE
- Overview
- Incident Reporting
- Permit to Work
- Safety Inspections
- Advanced Finance
- Overview
- Profit & Loss Statement
- Budget Forecasting
- Expenses & Budget Management
- Payroll Logistics & Batch
- Investment Instruments
-
Security & Compliance
- Threat & Monitoring
- Overview
- Security Hub
- Security Audit
- IAM Visualizer
- Dependency Scanner
- Secret Scanner
- Secret Vault
- Traffic Monitor
- Audit Trail
- Threat Simulator
- Compliance Radar (MatrixAgent)
- Identity & Compliance
- Overview
- PPTX Auditor
- PDF Auditor
-
Engineering & Infrastructure
- DevOps & Infrastructure
- Overview
- Cron Builder
- CI/CD Pipeline
- Containers
- Log Streamer
- Secrets Management
- Health Monitor
- Infrastructure as Code
- Developer Tools
- Overview
- Nerve Center
- Git Diff Viewer
- Regex Tester
- JSON Transformer
- Workflow Optimizer
- Execution Replay
- Workflow Editor
- Dev Hub Terminal
- Security Hub
- Graph View
- Terminal Editor
- API Playground
- DSL Compiler
- Database Tools
- Overview
- Database Manager
- ORM Mapper
- SQL Formatter
- Schema Visualizer
- Visual Query Builder
- Seed Data Generator
- Custom Collections
- QA & Test
- Overview
- Flake Tracker
- Artifact Vault
- Web Test Module
- Test Plan & Runner
-
Data & Intelligence
- AIOps & Intelligence
- Overview
- Agents
- Agent Architect
- Model Center
- Prompt Lab
- Knowledge Base
- Agent Persona Editor
- Tool / Function Registry
- Observability & Logs
- DataOps & Analytics
- Overview
- Data Inspector
- AI Predictive Models
- Core Modules
- Ads & Social Media
- API & Integration
- App Groups
- Appointment Booking
-
Automation
- Automation
- Overview
- Workflow Editor
- Monitoring
- Execution Heatmap
- Workflow Pulse
- Trigger Control
- Task Scheduler
- Integration Hub
- Rule Engine
- Pipeline Designer
- Workflow Editor
- Overview
- Triggers
- Manual Input
- Data Sources
- Ecommerce
- Document Management
- Logic & Transform
- AI Agents
- Knowledge / AI
- Validation & Security
- Integrations
- Outputs
- Document Generation
- Image Generation
- Video Generation
- Coming Soon
- Call Center
- Collaboration
- Community
- Creative Studio
- CRM
- Fleet & Logistics
-
Finance
- Hub
- Finance Hub
- Accounting Hub
- Treasury & Banking Hub
- Commercial Accounts Hub
- Invoicing & Billing Hub
- Reporting & Analytics Hub
- Grid View
- Overview
- Accounting AI Assistant
- Treasury
- Invoice Manager
- Expense Management
- Financial Accounts
- Payroll
- Accounts Receivable
- Accounts Payable
- Bank Reconciliation
- Budget & Forecasting
- Expenses & Budget
- Profit & Loss
- Tax & Compliance
- Galleries & Curation
- Google Display Ads
- Human Resources
- Legal & Support
- Logistics
- Map Explorer
- Marketing
- My Workspace
- Plans & Pricing
- Point of Sale
- Product Management
- Purchase
- Sales
- Semantic Search
- Strategy & Fundraising
- Warehouse
- Website
- Productivity
- Project Management
- Documents
- Learning (LMS)
- App Factory
- Research
- Utilities
- Creativity
- Creator Tools
- Image Tools
- Video Tools
- Audio Tools
- Writer Tools
Embedding Model
Configuring the local Ollama model that powers ranking and ordering for Semantic Search.
Why Ollama, and Why Local
By default, embeddings for Semantic Search are computed by a local Ollama instance running on your own machine at 127.0.0.1:11434. (You can opt into a hosted model instead — see Hosted (Cloud LLM) Embedding below.) With Ollama this is a deliberate architectural choice: your knowledge library — potentially sensitive documents, notes, or internal material — never has to leave your computer just to be ranked. TotalApp's cloud-hosted server has no network path to your Ollama instance; the ranking always happens directly in your browser talking to your own machine.
This also means the Embedding Engine setting is completely independent of your Writer Engine choice (API, Local LLM, Ollama) for text generation — you can generate content via the Anthropic API while still using a local Ollama model purely for embeddings, or vice versa.
Screen preview
A quick look at the screens. Use the toggle in the corner of each preview to switch between the dark and light themes.
Assisted — I pick from ranked suggestions
Cosine similarity (raw, default)
nomic-embed-text via Ollama
Minimum 60% relevance before suggesting
Vectors stored locally, refreshed on edit
Used automatically when Ollama is offline
Runs in the background after each upload
Assisted — I pick from ranked suggestions
Cosine similarity (raw, default)
nomic-embed-text via Ollama
Minimum 60% relevance before suggesting
Vectors stored locally, refreshed on edit
Used automatically when Ollama is offline
Runs in the background after each upload
Assisted or automatic
Setting Up
- Install Ollama on your machine if you haven't already.
- Pull an embedding model, e.g.
ollama pull nomic-embed-text. - In TotalApp, go to Settings → AI Models → Embedding Engine.
- Confirm your Ollama connection is detected (test it under Text Generation Provider if it isn't showing as connected).
- Select your embedding model from the Semantic Search (Embedding Engine) dropdown — only models with embedding-oriented names (containing "embed", "bge", "nomic", or "minilm") are listed here, so it never gets mixed up with a text-generation model.
Hosted (Cloud LLM) Embedding
In Settings → AI Models → Embedding, set the provider to Cloud LLM (Hosted API) and pick a model from the Modelion or OpenRouter list. Semantic Search then ranks your sources with that model instead of Ollama, with no local install needed.
Two things to know before switching
Your text leaves your machine. With a hosted model, the text of your query and of every source being ranked is sent through TotalApp's server to the provider. Ollama never does this.
Changing the model makes stored vectors outdated. Vectors from different models cannot be compared. Each source remembers the model that produced its vector, so after any change of embedding model the old vectors are recomputed automatically the next time the sources are ranked (and sources saved before this was recorded are recomputed once). With a hosted model that means each source's text is sent again.
Model Separation — Why You Can't Pick a Chat Model Here
The Embedding Engine dropdown only lists Ollama models whose names indicate they're built for embeddings (e.g. nomic-embed-text, bge-small, all-minilm). General-purpose chat/completion models (e.g. llama3, deepseek, qwen) are excluded from this list — and, at runtime, TotalApp guards against calling a chat model's embedding endpoint by mistake. This keeps the two roles cleanly separated: one model type talks to /api/generate for writing, another talks to /api/embeddings for ranking.
Understanding Relevance Scores
Cosine similarity between two text embeddings ranges in theory from -1 to +1, but real-world scores from general-purpose models like nomic-embed-text cluster in a much narrower practical band:
| Relationship | Typical score |
|---|---|
| Completely unrelated text | ~20-40% |
| Related, relevant text | ~55-75% |
| Near-identical text | 90%+ (rare) |
Unrelated content rarely scores near 0% because language models share common "general language" structure across nearly any text. This is normal and expected — a 30% score on an unrelated document is not a bug. See the info tooltip next to Embedding Engine in Settings for the same explanation in-app.
What Happens Without an Embedding Model
Nothing breaks. My Knowledge and every Writer Tool's Attach Knowledge picker continue to work exactly as they did before Semantic Search existed — sources are listed in their original order, with a note that ranking is currently unavailable. Ranking and Automatic auto-attach are the only features gated on having an embedding model configured.
FAQ
nomic-embed-text is a solid general-purpose default. Smaller models like all-minilm run faster but may rank less precisely; larger models like bge-large are more accurate but slower to embed each source.