MichaelZelbel/menerio

Menerio

What it is

Menerio is a central event hub for personal data.

Project status: Alpha Menerio is usable but still evolving. APIs, data structures, and UI may change without notice. Some features are partially implemented or experimental. We recommend it for early adopters and contributors who are comfortable with rough edges.

It connects multiple apps into a single system by capturing and distributing events. Instead of isolated tools with their own data silos, Menerio acts as the backbone that keeps everything in sync.

Each connected app remains the owner of its data, while Menerio ensures that relevant changes are shared across the system.

Why it exists

Most apps today operate in isolation. Data is fragmented, duplicated, and quickly becomes inconsistent.

Menerio solves this by introducing a simple principle:

• Every record has one clear owner
• All changes are emitted as events
• All connected apps stay in sync through a central event bus

This enables a system where:

• Data remains consistent across apps
• Ownership is always clear
• Integrations become simple and scalable

The goal is not to replace apps, but to connect them into a coherent system.

Core Concepts

Single Source of Truth

Each piece of data belongs to exactly one app. Other apps receive synchronized copies but never become the source of truth.

Event-Based Architecture

All changes are emitted as events (e.g. event.created, event.updated). Menerio stores and distributes these events to subscribed apps.

Hub-and-Spoke Model

Apps do not communicate directly with each other. All communication flows through Menerio as the central hub.

Synchronization with Ownership

Changes made in one app propagate back to the owning app through Menerio, ensuring consistency without conflicts.

Features (Current State)

• Central event ingestion and storage
• Event distribution to connected applications
• Basic data synchronization model
• Supabase-backed data layer