Control
Users should see where data lives, which trackers run and what gets synchronized.
About
Daily data transformed into a controllable runtime.
Trackers Lens comes from a simple and demanding choice: build tools that stay readable, local and honest as the project grows.
It is not only a dashboard. It is a way of working: less noise, more control, more care for detail. Every tracker, lens and workspace should shorten the distance between data, decision and real interface.
Manifesto
The manifesto behind Trackers Lens
Local-first
The runtime starts in the browser and IndexedDB: cloud only when it is truly needed.
Composability
boxLens, boxTracker and workspaces should connect without becoming a rigid structure.
Precision
Every panel should explain what it measures, where it comes from and when it was updated.
Privacy
Permissions, API keys and automations must stay explicit and governable.
Resilience
Trackers, retries, logs and monitors should make errors and runtime states readable.
Simplicity
Add power without adding confusion: fewer layers, clearer intent.
Evolution
Plugin today, cloud dashboard tomorrow, dedicated app when the runtime is mature.
Openness
Assets, templates and marketplace should encourage reuse, study and collaboration.
Discipline
Daily quality: document, test, refine and make the product clearer.
Carlos Malleux
Trackers Lens did not start as another generic app. It started as a need: controlling data sources, automations and interfaces without losing clarity.
Over time it grew by removing ambiguity: boxLens for visualization, boxTracker for collection, workspaces for composition, IndexedDB to keep the runtime close to the device.
The goal is not to create a closed box, but to make data more usable, direct and verifiable, with AI and automations serving the user.
Trackers Lens is the result of that process: a local-first ecosystem designed to become a professional app without giving up control.