Architecture
How the QuilrAI File Indexer builds and maintains a local filesystem index on the endpoint, driven by configuration from the dashboard, to resolve file paths for DLP scanning.
Dashboard / Extension
# File index settings
Root paths: /Users/alice/Documents
C:\Users\Alice\Documents
Ignore: node_modules, .git, *.tmp
Scan interval: every 60 min
Max files: 500,000QuilrAI File Indexer
Configure
Config Push
Pushed from dashboard
Root paths + ignore rules
Triggers immediate re-index
Mount Policy
Network shares excluded
Disk images excluded (macOS)
Tenant overrides supported
Scan
Full Scan
Parallel directory walker
1,000-file batch writes
Safety limits enforced
Safety Guards
Soft limit: reduces scan depth
Hard limit: prunes deepest paths
Timeout: prevents data loss on partial scan
Watch
Real-time Watcher
OS-native events (FSEvents / ReadDirectoryChangesW)
300 ms batch window
Atomic database updates
Serve
File Search
Filename lookup from index (phase 1)
Disk metadata verification (phase 2)
Platform search fallback
DLP Engine
File Path ResolutionUpload ScanningDownload ScanningDLP FindingsAudit Trail
QuilrAI
Pipeline Stages
Every index operation flows through these stages. Each stage is independently configurable from the dashboard.
Scheduling
Platform Support
Observability
Index state and scan history are available from the dashboard under File Index Status.
- Scan status: Idle / Running / Failed with last-run timestamp and duration
- File count: total indexed files and any paths pruned by safety limits
- Watcher activity: create, modify, and delete event counts
- Search performance: index hit rate vs. disk-verification fallback rate