Our own identity
No dependency on a third-party identity provider. A short-lived access token with rotating renewal, stored only as a hash. Two roles: manager and member.
Platform
Kodzonia Online.
The third phase of the product: from a single-user application to a multi-user platform, with accounts, shared projects, managed credentials and per-call cost auditing.
The brain stays local, the data and the credentials move to the cloud.
The structural decision
Two alternatives were rejected explicitly: running the agent loop on the server, for cost and complexity, and a fully remote workspace, as too big a jump. What moves is only the model call and the project's persistence. The tools stay where the code is.
Invitations that expire
A random token sent by email, persisted only as a hash, valid for seven days. Plus the invariant that protects the customer: the last manager of a project cannot be removed or demoted.
Credentials on the server
A connection belongs to the project, not to the account. The secret never sits on the connection row: it lives in the encrypted vault, under a separate master key.
Auditing before quotas
Version 1 measures: one row per call, with model, tokens and duration. The hard limit arrives in 1.1, built on the data already collected — in the right order.
Where we are
6 of 7 subprojects shipped
- 01
Server foundation
CompleteAccounts, projects and invitations.
- 02
Connections and vault
CompleteProvider credentials managed on the server.
- 03
LLM gateway
CompleteThe call goes through the server, which injects the credential and audits it.
- 04
OAuth migration
CompleteProvider sign-in driven by the server.
- 05
Project data
CompleteConversations, pools, journal, schedule and memory over the API.
- 06
Web panel
CompleteConfiguration, usage and administration in the browser.
- 07
Final cutover
OpenThe last step: the project stops depending on the local file.
The road to SaaS is already built.
The cutover is what is left. This is the right moment to talk about scale.