Project heritage
From search infrastructure
to a broader engineering laboratory.
Egothor began in 1998 as a search-engine project. Over time, the same engineering programme explored language processing, distributed services, crawling, network geolocation, sensor gateways and experimental data platforms. This page preserves that lineage without presenting retired systems as current products.
Core lineage
Egothor Search Engine
An open-source Java full-text search engine with dynamic index updating, transactions, plagiarism detection, incremental updates, common document formats, an extended Boolean model and a language-independent stemming approach.
Historical summary ↑J5M
A lightweight distributed-application layer built around cooperating services, remote-object discovery, direct or remote invocation, lifecycle control and hot-spare service instances.
Historical summary ↑Bobo
A distributed crawler and virtual-entity platform that grew from the crawling requirements of Egothor into a general architecture for autonomous web-facing components.
Galeo
Research into IP geolocation using a model that treated network paths as heterogeneous rather than assuming a single constant propagation behaviour.
Egothor3 / Q!D
An experimental database direction initiated in 2012; the later Q!D implementation used the J5M platform to explore alternative processing models for large data collections.
Current Egothor generation
Radixor renews the language-processing line, ZeroEcho expands into modern cryptographic engineering, conflux provides focused application infrastructure, MethodAtlas applies evidence-oriented engineering to software assurance, and EGOTHOR v4 brings the project family back to full-text search for regulated environments.
Current projects →Applied systems
The wider project family also included systems built around networking, sensors and data acquisition. On Leo Galamboš's historical project list these include SNOG (sensor-network gateway), SafetyCare (GPS/GSM assistance application), Cyclone (distributed feed crawler and analyser) and RaSPEL (LoRaWAN-to-REST bridge/controller).
What carried forward
The individual systems are different, but several ideas recur: move complexity away from critical runtime paths; make service behaviour explicit; prefer compact data structures; allow components to be replaced or evolved independently; and keep enough technical evidence around a claim that another engineer can challenge it.