Korwin Analytical Operating System — analytical layer over the Ferus ecosystem. Data stays in Azure; Obsidian is the display.
Korwin Analytical Operating System — an Obsidian view that renders live operational dashboards from the Ferusnet backend (Jira, Freshdesk, CRM, tenant metrics) inside your vault. Data stays in Azure; Obsidian is only the display layer.
Published by Ferusnet.
Kaos opens a single custom view — "Kaos" — with tabbed panes for each connected service. Widgets are pulled on demand from the Ferusnet tenant tools API and rendered as tables, badges, bar charts and status tiles. Nothing is written back to the vault unless you explicitly enable the read/write vault-access mode.
Kaos is not a general-purpose analytics plugin. It only works if you have a Ferusnet tenant account and a Kaos API key issued by the Ferusnet identity service. If you are outside the Ferusnet organisation, this plugin will do nothing useful for you.
Requires Obsidian 1.11.4 or later. On 1.13.0+ the settings are also indexed by Obsidian's settings search.
Settings → Community plugins → Browse → search "Kaos" → Install → Enable.
ferusnet/kaos-plugin.main.js, manifest.json and styles.css from the latest
GitHub release..obsidian/plugins/kaos/ inside your vault.Open Settings → Kaos and fill in:
| Field | Meaning |
|---|---|
| API key | Your Kaos plugin key (starts with kaos_). Generate one by asking the Ferus agent "generate my Kaos plugin API key". Stored in Obsidian's OS keychain, never in data.json. |
| Theme | Dashboard palette — dark / light / follow the app theme. |
| Vault access | none (default), read, or readwrite. Controls whether the plugin may read notes for context or write reports back into the vault. |
| Share folder | Only used when vault access is readwrite — the folder where Kaos may create notes. |
Open the dashboard with the ribbon icon or the command palette entry "Kaos: Open dashboard".
The plugin talks to one external endpoint — the Ferusnet tenant-tools
API. All requests carry your API key in an Authorization header and
identify the plugin via a User-Agent. No third-party analytics,
telemetry, tracking or ad networks. No data is sent to Ferusnet unless
you invoke a dashboard action.
Your API key is written to Obsidian's OS-native secret storage
(macOS Keychain / Windows Credential Manager / libsecret on Linux). It
never appears in data.json, exported vault backups, or plugin logs.
Vault contents are only sent to the backend when Vault access is set
to read or readwrite, and only for the notes you explicitly attach to
a widget action. In the default none mode nothing from your vault
leaves your machine.
If a key leaks, ask the agent to
"revoke my Kaos plugin API key <key_id>" (single-key rotation) or
"revoke all my Kaos plugin API keys" (nuke every device). Revocation
takes effect on the next request.
MIT — see LICENSE.