Find anything. Even without the filename.

Search supported documents, photos, audio, and video by filename, contents, metadata, or meaning. EmbedCore indexes the folders you choose locally and keeps them current in the background.

Exact when you know it. Semantic when you don't.

Scroll

Search the way you remember. Use exact names when you know them, natural language when you don't, and filters when you need precision. EmbedCore keeps selected folders indexed in the background and can surface duplicate files without sending your library to a cloud service.

Privacy-First

Local by default.
Cloud only when you choose it.

In local mode, your files, embeddings, and metadata stay on your machine. Optional online providers can be enabled explicitly with your own credentials, but they are never required for core local search.

100%
Local mode available
0
Required cloud services
0
Required accounts
Multi-Modal

Multiple formats.
One search.

From documents to photos to music to video — EmbedCore modules declare the file types they support and bring those indexed modalities into one search interface.

The Basics

What is a
vector embedding?

It sounds technical, but the idea is simple. Think of it as giving supported content a set of coordinates — not for where it is, but for what it means.

Your file

A supported photo, document, audio track, or video from one of the folders you choose to index.

becomes

A point in meaning-space

A list of numbers (a "vector") that captures the essence of that file — its topics, mood, content, and context.

01

Files have meaning

A photo of a sunset, a jazz song, and an essay about nature are all different files — but they share something in common. Traditional search can't see that connection because it only looks at filenames and keywords.

02

AI reads the meaning

A compatible embedding model — local by default — converts supported content into a list of numbers. Think of it like GPS coordinates, but instead of marking a place on a map, they mark a place in "meaning space."

03

Similar things land nearby

Items processed by the same compatible embedding model get nearby coordinates when their meaning is similar. EmbedCore keeps model and modality indexes separate when their vector spaces are not compatible.

That's it. Vector embedding is just a way to turn "what something means" into numbers — so a computer can finally search by meaning, not just by name.

Architecture

Built to be extended.

Modules are standalone executables that communicate via a simple JSON protocol. Write them in any language — Rust, Python, Go, C++ — with zero framework lock-in.

Language Agnostic

Write modules in any language. If it can read stdin and write stdout, it can be an EmbedCore module.

Self-Contained

Each module bundles its own models and dependencies. Install or remove modules without affecting anything else.

Zero Lock-In

No framework assumptions. Modules choose their own ML runtime — ONNX, PyTorch, TensorFlow, or pure DSP.

module_protocol.json
{ "type": "handshake", "module_name": "audio-features", "version": "1.0.0", "capabilities": { "embedding_layers": [{ "name": "timbral", "dimensions": 128 }], "supported_extensions": [".mp3", ".flac", ".wav", ".ogg"] } }
01

File Detection

Filesystem watcher detects new and changed files in real time

02

Change Verification

Two-tier detection: fast mtime check, then SHA-256 hash for accuracy

03

Priority Queuing

User requests first, then new files, then reprocessing jobs

04

Dependency Resolution

Topological sort ensures modules execute in the right order

05

Concurrent Execution

Independent modules process files in parallel for maximum throughput

Pipeline

Intelligent
from ingestion to index.

The processing pipeline handles everything — from detecting file changes to orchestrating module execution — so your library stays indexed without you thinking about it.

Real-Time Watching

Filesystem events trigger processing automatically. Add files to a watched folder and they're indexed within moments.

Cycle Detection

Dependency graph analysis prevents circular module chains via depth-first search before any processing begins.

Local by Default

Core indexing and supported local models run on your hardware. Optional online providers are used only when you explicitly enable them.

Platform

One experience.
macOS, Windows, and Linux.

Built as a Tauri and Rust desktop app with a local background service. The first releases target modern desktop hardware, with local acceleration where available.

macOS

Desktop build optimized first for Apple Silicon, with Finder integration planned for fast search access.

Linux

Linux desktop builds for modern distributions, with packaging and acceleration support refined per release.

Windows

Windows desktop build using WebView2, with File Explorer integration planned for fast search access.

Desktop App. Local Background Service.

Choose the folders you want indexed, keep them up to date in the background, and search from one interface. Finder and File Explorer entry points are part of the V1 integration plan.

Coming Soon

The future of
local search.

EmbedCore is being built for people who believe their files — and the intelligence extracted from them — should stay on their machine. Be the first to know when it launches.

No spam. One email when we launch.