EchisMonitor/ EchisWorld

DESKTOP ANALYSIS, UNDER YOUR CONTROL

An analyst's workspace.
On your machine.

EchisMonitor is an early-stage project for a customizable desktop analysis workspace. Bring your research, your tools and your own way of working.

Explore the project

Planned forWindowsmacOSLinux

Public-source research

Illustrative layout · fictional sample data

LOCAL WORKSPACE

PROJECT MATERIALS

Source notes.md
Public dataset.csv
Research brief.pdf

ANALYST NOTES

Compare the original sources. Keep observations separate from assumptions.

Sample project / research

PROPOSED WORKFLOW

01Organize sources
02Run chosen tools
03Review findings

INTERFACE STUDY / NOT A RELEASED APPLICATION

A practical place to connect research materials, tool outputs and your own judgment.PROJECT / EM—001

01 / PRODUCT PRINCIPLES

Useful tools.
A workspace that is yours.

Our focus is on independent researchers, OSINT learners and analysts working with public information or data they are authorized to use.

01 / LOCAL DATA

Keep the core on your device.

We plan to keep project files, notes and workspace settings on the user's machine. The core workspace should work without a mandatory cloud account.

02 / USER-CONTROLLED TOOLS

Choose what connects.

Planned tool support includes utilities that work locally and optional connections using the user's own API credentials. Tool access and data sharing should be explicit.

03 / ADAPTABLE LAYOUTS

Arrange it around your work.

We want users to organize panels and select the tools they need inside the application, with a clear separation between source material, results and analyst notes.

02 / INTENDED WORKFLOW

From scattered material
to a clear working context.

The proposed desktop workspace would bring the steps of a research task together, while keeping the analyst responsible for interpreting the results.

  1. Build a local project.

    Organize research files and notes in a workspace that belongs to you.

  2. Use a tool deliberately.

    Choose a local utility or a configured provider for a specific, authorized task.

  3. Review the result in context.

    Compare outputs with the source material and keep your conclusions visible alongside your notes.

Local storage and online tools have different boundaries. The planned core keeps project data on the device. An optional online tool may send selected inputs to its provider; we intend to make those connections visible and controlled by the user.

03 / DEVELOPMENT

Start small.
Build something that works.

EchisMonitor is a student-led project currently in the concept and design stage. There is no released desktop application yet.

CURRENT / CONCEPT & DESIGN

Define the first workflow.

Set the initial research use case, workspace structure, tool boundaries and desktop architecture.

PROPOSED / FIRST PROTOTYPE

Build the local foundation.

Implement local project organization, a configurable interface and a small set of useful tools.

PROPOSED / PLATFORM VALIDATION

Test across desktop systems.

Review permission handling and packaging, then validate the application on Windows, macOS and Linux.

Claude as a development tool.

We plan to use Claude and Claude Code for architecture feedback, implementation, interface iteration, testing and defensive review of our own code and dependencies. External AI services are intended for development work; they are not a mandatory connection for the proposed desktop workspace.

Licensing is still being evaluated.

We are considering an open-source core. The repository, license and release model have not been finalized. The first priority is a focused, usable prototype with clear control over tools and data.

Follow the project here.

This page introduces the current direction. Prototype notes and release information will be added as development progresses.

PRE-PROTOTYPE