Aether is the web ecosystem runtime and application shell of the Rymory platform. It carries authentication, session orchestration, cross-app navigation and multi-tenant context — invisibly, across every application.
Most identity systems give you an auth endpoint. Aether gives applications a place to live.
You do not see Aether. You see the applications it carries.
JWT authentication, federation, role hierarchy, session tokens. The ground truth of who you are.
App orchestration, config-driven routing, SSO propagation, template engine, multi-tenant context. The medium everything runs in.
Notes, Drive, Planner, Passwords — applications that live inside the runtime, authenticated by the identity layer.
"Aether is not the authority.— Aether Runtime, design principle
It is the environment."
Every application, route and navigation structure is defined in JSON config. Same runtime, infinite configurations.
Cross-domain login and logout flow built in. One session travels to every connected application automatically.
appId, merchantId, projectId, roleId — carried in every request. Applications always know their tenant scope.
w_artfactory for public pages. w_default for authenticated panels. Swappable per-application, even per-user.
EN, TR, RU built in. Language detected from browser, stored in context, applied across every view.
Each app is an isolated module. Notes, Drive, Planner, Passwords — same shell, different configs. New apps drop in.
Authentication, JWT issuance and session validation are handled entirely by Rymory. Aether consumes the identity — it does not produce it.
Between identity and application lives the runtime. Config loading, route orchestration, SSO propagation, template selection — all Aether.
Notes, Drive, Planner, Passwords — each app is a module. Same shell. Different config. New applications drop in without touching the runtime.
Lemoras is not a framework. It is a living ecosystem of applications built on top of Rymory identity and Aether runtime.
Aether was not designed. It emerged. Starting in 2017 as the frontend layer of the Lemoras ecosystem, it accumulated patterns over years of real production use — config-driven routing, cross-domain SSO, multi-tenant context, plugin-style app loading.
At some point, the infrastructure had clearly outgrown its label. This was no longer a "UI project". It was a runtime. An environment. A medium. The word "Aether" — the ancient concept of the invisible medium that carries everything — was the only name that fit.
Aether is developed as an independent runtime project, while remaining the official runtime layer of the Rymory ecosystem.
Aether is part of the Rymory open ecosystem. Build your own applications on top of it, fork it, extend it.