Documentation

Autonoma is a Windows desktop application. It runs on your machine, uses your accounts, and calls AI and data providers with API keys you supply. Nothing here requires a server of ours to be up.

These pages describe what the software does today. Where something is switched off by default or not implemented, that is stated rather than glossed over.

Start here

Install and licence — get it running and entered.
API keys — the app ships with none, so this is the step that makes anything work.
Social Studio — connect an account and plan your first posts.

The shape of the thing

Autonoma is around forty screens in one window, grouped into ten areas. You are not expected to use all of them — most people live in two or three and ignore the rest. Anything you have not configured reports itself as unconfigured rather than pretending.

Area	What is in it
Dashboard	Overview with system scan and bot controls, and an agentic CLI that can drive the rest
Analytics	Revenue and activity charts, revenue by stream and platform, CSV export
Income and publishing	Storefront, audiobook builder, a Library with real PDF/EPUB/audio readers, passive-income channels, creator marketplace and partner programme
Trading and crypto	Trading, wallet, multichain transfers, mining, claiming, token deployment — all off by default
Automation	Bots, connected platforms, pricing rules, campaigns, pipelines
AI and evolution	Provider keys, text/image/audio/video generation, a self-improvement loop, DAO governance, and the JK2 agent
Development	A full IDE with LSP and debugging, VPS management over SSH, Jedi Knight modding tools
Reverse engineering	Static analysis of executables, firmware, WebAssembly, Android and .NET
Communication	Discord bot and announcements, social accounts and the Social Studio
System	Background service, feature toggles, security centre, settings, logs

A full screen-by-screen breakdown, with the known limitations of each, is on the features page.

The crypto features are governed by explicit switches. Storing an exchange API key does not enable trading — the credential and the permission are deliberately separate decisions. See safety and dry run.

Where your data lives

Everything is under your user profile, not in the installation directory:

%USERPROFILE%\.autonoma\
  data\credentials\     your API keys, encrypted
  data\social\          connected accounts and the content plan
  data\safety\          the dry-run journal and stop file
  logs\                 application logs

The encryption key for credentials is generated once, on your machine, and stored alongside them. No other installation can read your credential file.

What it will not do

It does not upload your content anywhere except to the platforms you connect.
It does not publish anything without a named person approving it first.
It does not spend money, place an order, or sign a transaction while dry run is on, or while the relevant feature switch is off.
It does not ship with anyone’s API keys, and it never sends your keys to us.

Something here wrong or missing? Tell us — documentation that describes software that no longer behaves that way is worse than none.