The studios

A studio is a workspace for making one kind of thing. There are four of them for producing work, and a fifth idea — studio mode — for running several at once across as many screens as you have.

Nothing here is a wizard that hides what it did. Every studio writes real files to disk that you can open in something else, and tells you when a dependency is missing rather than producing an empty result.

Ebook Studio

Income and publishing → Storefront

One place to produce every kind of book.

Two paths run through it. The first is a written book — an AI-written guide or a novel, aimed at an audience you describe — which comes out as EPUB, PDF and cover art: ordinary files on your disk that you can upload to whichever store you sell through. Gumroad is the only one Autonoma publishes to directly; everywhere else, including KDP, is an upload you make yourself.

The second is low-content: planners, journals and workbooks, the format KDP is full of. Same catalogue, different production line.

Whatever you make lands in one catalogue with a publishing checklist beside it.

The checklist is manual on purpose. Amazon has no API for this, so anything claiming to “publish straight to KDP” is either lying or driving a browser and hoping. Autonoma walks you through the upload instead of pretending.

Audiobook Studio

Income and publishing → Audiobooks

Takes a book you have and narrates it.

Audition voices before committing, narrate chapter by chapter, and manage the finished files. The output is a real audiobook with real chapter markers, not one long file.

Mastering and M4B chaptering need ffmpeg on your machine. If it is missing the studio says so up front rather than producing an unchaptered file and letting you find out later.

Social → Studio

Compose quote cards, plan a month of posts in a single paste, and publish under your own name — or under whichever connected account you choose.

It has more written about it than the others because publishing under someone’s name is where the consequences live. A book you did not mean to make sits on disk; a post you did not mean to send is already gone.

So a named person has to approve a plan before anything leaves the machine, and a post aimed at a disconnected account cannot be approved at all.

The full Social Studio guide →

MediaStudio Pro

AI and evolution

Editing for what you generated, and for footage you already had.

Upscaling — Real-ESRGAN for PNG, JPEG, WebP and BMP images, which needs your own Replicate key; and a high-quality ffmpeg lanczos resample for video, which needs no key. Only the image path is AI, and this line used to call both of them “AI upscaling”.
Automatic subtitles, transcribed from the audio and burned in
Scene detection, giving you cut points
Trim, join, extract audio, mix in a second track
Filters — greyscale, blur, sepia, sharpen, fade
Export up to 8K

These are real operations through ffmpeg and Replicate, not previews. Every one writes a real file to disk.

That honesty has a cost: the ffmpeg operations need ffmpeg installed, and the AI ones need your own Replicate key. Both report themselves as unavailable rather than failing halfway through a long export.

Working across more than one window

The CLI detaches; the IDE remembers layouts

Two real things, described plainly.

The CLI opens in its own window, so you can keep a command line beside whatever area you are working in without giving up a pane. While it is detached the CLI tab shows where it went rather than starting a second transcript.

The IDE saves and loads named layouts. Arrange the editor, terminal, problems and file tree as you want them, save that arrangement under a name, and load it back later. Nothing is bundled — the list starts empty and fills with the ones you make.

This section used to describe “Studio mode” — several top-level windows, each a workspace with its own dock layout, sharing a selection between them, with six studio presets and six layout presets listed in two tables. None of that is in the application. It belonged to the retired Qt-widget dashboard (ui/dashboard_components/studio_window_manager.py), and nothing in the shipped app reaches it. The Dashboard area has exactly two screens, Overview and CLI. Documentation describing software that no longer behaves that way is worse than none, which is what the note at the foot of every page here says.

What none of them do

No studio uploads anything to a service you have not connected, and none of them send money. Publishing to a storefront needs that storefront’s credentials; posting under an account needs that account connected and a named approval; and payouts throughout Autonoma are recorded against a transaction you made in your own payment provider, never initiated.

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