Local access

PROJECT HISTORY

From an open laboratory to local-first memory

ArchitekIA did not start as a local vault. The domain was acquired on October 6, 2025 to experiment, connect tools and learn in real conditions. The current version makes a different choice: each tool remains independent and ArchitekIA focuses on local personal memory.

The domain becomes an experimental ground

architekia.com is registered. The first goal is not a frozen product but a public meeting point for testing ecosystem components.

V1

Version 1 · The laboratory

First interfaces, flows and centralization experiments. ArchitekIA acts as an experimental front door to understand how several tools can cooperate without multiplying user journeys.

V2

Version 2 · The API hub

ArchitekIA becomes a large-scale centralization test. Flows from WebPion, ITYLOS, 0bla and other ecosystem components are brought into one interface through APIs. The experiment validates use cases but also exposes a limit: a central hub can recreate a dependency that independent tools do not need.

The tools become independent

Projects gain their own interfaces, use cases and roadmaps. Systematic centralization becomes less useful. ArchitekIA no longer needs to be the technical center of the ecosystem.

V3

Version 3 · Memory that stays with you

The project is rebuilt around local-first architecture: no mandatory account, encrypted browser storage, imports, organization, search, backups and voluntary sharing. ITYLOS and 0bla become optional complementary services, never mandatory dependencies.

What is now stable

ArchitekIA has one clear job: capture, organize, retrieve and protect personal memory. Other ecosystem tools remain separate and can evolve without forcing a vault migration.

This changelog documents major product eras. It is not intended to list every technical patch or intermediate build.