Extensible Open Network

An open ecosystem for everyone.

Project plan · Contracts · Contributing

EON is an umbrella, not a product. Everything under it is open source, non-profit, and built on shared contracts rather than a shared codebase by accident.

Two products today:

A media viewer built on a small core where everything else is a module — video, files, the marketplace, the creator tools. It speaks the Stremio addon protocol, so the existing addon ecosystem works, and it is written in Rust on top of Tauri and mpv.

The same core, compiled as an institutional product for schools and remote teaching. The open marketplace, arbitrary addon URLs, and open BitTorrent access are not hidden in that build — they are absent at compile time, and CI verifies it.

One umbrella, one core, two products. A student opens material downloaded at school with the same engine at home, and a teacher learns one creator tool.

flowchart TD
    SPEC["eon-stream-spec<br/><i>contracts: addon API, manifests,<br/>package format, signing</i><br/>Apache-2.0"]

    CORE["eon-stream-core<br/><i>module manager, addon protocol,<br/>signature verification, updater</i><br/>GPL-3.0+"]
    ENGINE["eon-stream-engine<br/><i>BitTorrent, sequential streaming,<br/>local HTTP, mpv IPC</i><br/>GPL-3.0+"]

    APP["eon-stream-app<br/><i>Tauri desktop client</i><br/>two build profiles: EON Stream · EON Edu<br/>GPL-3.0+"]

    EDU["eon-edu-server<br/><i>institution server: material<br/>distribution, catalogue, roles</i><br/>AGPL-3.0+"]

    SDK["eon-stream-sdk<br/><i>addon SDK, validator, examples</i><br/>MIT"]
    MKT["eon-stream-marketplace<br/><i>Git-based index, review tooling</i><br/>CC0 · Apache-2.0"]
    DOCS["eon-docs<br/><i>plan, policies, guides</i><br/>CC-BY-SA-4.0"]

    SPEC -.->|implemented by| CORE
    SPEC -.->|implemented by| SDK
    SPEC -.->|implemented by| EDU
    CORE --> APP
    ENGINE --> APP
    APP <-->|HTTPS| EDU
    MKT -.->|index consumed by| APP
    DOCS -.->|governs| APP

    classDef spec fill:#1f2937,stroke:#6366f1,stroke-width:2px,color:#e5e7eb
    classDef rust fill:#1f2937,stroke:#f59e0b,stroke-width:2px,color:#e5e7eb
    classDef aux fill:#1f2937,stroke:#4b5563,stroke-width:1px,color:#9ca3af
    class SPEC spec
    class CORE,ENGINE,APP,EDU rust
    class SDK,MKT,DOCS aux

The contracts come first and everything implements them. That is deliberate: the addon API, the manifest schema and the package format are the parts that cannot be changed later without breaking other people's work, so they live in their own repository, under a permissive license, versioned independently of any implementation.

Naming follows eon-<product>-<component>. Repositories that belong to the umbrella rather than to one product carry no product name.

Scaffold means the scope and contracts are written down but implementation has not started. The phase is stated so nobody mistakes a planned repository for an abandoned one.

Faz 0 — foundations. There is no usable release. The contracts are at v0 and explicitly unstable.

What EON Stream v1 will be, and nothing more: a Windows and Linux desktop application that resolves Stremio-compatible addons, plays with mpv, streams from BitTorrent sequentially, manages first-party modules with signature verification, supports declarative themes, passes a pinned addon compatibility suite, and ships in Turkish and English meeting a baseline accessibility bar.

Not in v1: marketplace, accounts, creator tools, material packages, music, mobile, code-executing plugins, Edu.

The project plan is the real roadmap. Its decisions are numbered and permanent — madde 22 means the same thing forever — and they are referenced from code comments, pull requests, and these documents. When something changes, that plan is what gets updated.

Stated up front because it defines the project as much as the feature list does:

• It hosts no content and indexes no content. It connects to endpoints the user adds.
• It ships with no sources and no addons preinstalled, ever.
• It publishes no guides, lists, or recommendations for obtaining infringing content, and does not allow them in its community spaces.
• It sends no telemetry. Not off-by-default-but-present: absent.
• It stores no Turkish national ID numbers and holds no student data — in EON Edu the institution is the data controller and runs its own server.

The full list, and the reasoning, is madde 29 of the plan. It is a design constraint, not a marketing paragraph.

Read CONTRIBUTING.md and the Code of Conduct. Contributions are taken under the DCO — sign off your commits with git commit -s.

Good first contributions right now are in eon-stream-spec: the v0 contracts are being written, and review of a schema before it hardens is worth more than a bug fix after.

Security issues: SECURITY.md — never a public issue.

_{The code is free; the name is not — see TRADEMARK.md.
Not affiliated with, endorsed by, or connected to Stremio.}