no open core.
the whole platform.
the server that holds your keys, the console that manages them, the libs that talk to apis: all readable, auditable, forkable. and self-hostable.
№ 01 — the platform
the product itself, in the open
opened on 22 june 2026. the vault, key resolution, the authorization guards: nothing hides behind a proprietary edge.
the repo you enter through: what oto is, its architecture, its licence, how to contribute.
the core: mcp server + rest api, credential vault, orgs, authorization. it injects your keys at call time — and its code is right here.
the management console: accounts, organizations, connectors, procedures. the front that drives the backend, with no secret in the browser.
the command-line facade: the same connectors, outside any ai. handy locally, in scripts, in ci.
the claude code plugin: a self-configuring mcp connector. the shortest way into oto.
№ 02 — the libs
three bricks, on pypi
the connector library (oto.tools): the layer that talks to APIs, no CLI. consumed by the oto CLI and the mcp server.
french public-data connectors: recherche entreprises, sirene (43m-establishment stock over duckdb/parquet), inpi, bodacc, dvf, légifrance, case law. the engine behind oto's french data.