0.9 is out.
Quick context if this is your first time: Ideon is a self-hosted visual workspace, an infinite canvas where you drop blocks for your Git repos, notes, tasks, files, and now automation. Everything about a project in one place.
The last release post ended with “move from visibility to control.” This is the start of that.
Webhook block: drop one on the canvas, it becomes a live HTTP endpoint. CI pipeline finishes, monitoring alert fires, form submits, POST to the URL and Ideon reacts. Configure what happens: set a block’s visual state, change its color, create a Kanban task, prepend text to a note. Runs server-side, no open browser tab needed.
Cron block: same action set, triggered on a schedule instead of an event. Preset or custom cron expression.
LaTeX block: several people asked for it. Write $...$ or $$...$$, toggle preview, done. Turned out to look better on the canvas than I expected.
Proxy / Header Auth: probably the most relevant one for this crowd. Already running Ideon behind nginx mTLS, Traefik, or Authelia? You can now configure it to read user identity straight from the headers your proxy injects. No OAuth round-trip, no separate IdP. A few env vars, and all auth events still go to the audit log.
Still open source, still self-hosted only.
Looks very interesting! Two questions:
From a quick look around in the repo, I couldn’t find which CRDT lib you’re using. Which one are you using? I’ve used yjs in the past but getting the document out of yjs into a db was a pain.
Second: we’re also building a tool that connects a lot of information because research tools are very fragmented as well. What is your philosophy on how to connect the information while still keeping things structured and understandable? We’ve found that e.g. node networks are incredibly hard to understand when the data and logic behind them gets complex. We also found that when users are not restricted in their information entering (e.g. a markdown file), most will not enforce their own structure and it gets disorganised quickly. Did you try to solve that or is it more the users problem?