Work iblis
desktop

Iblis

Local-first AI music workstation for Windows — an Electron shell with a hot-swappable plugin architecture.

Iblis is a local-first AI music workstation for Windows 11. It runs offline by default — no cloud, no account — as an Electron shell where everything beyond text-to-song (image generation, stem splitting, BPM/key detection, waveform visualization, a node editor, a file-explorer view) is a hot-swappable plugin. Themes and skins are first-class and orthogonal to plugins, driven by a unified design-token vocabulary. In alpha and shipping: the Windows installer, auto-update channel, signed plugin host, generation engine, skin system and track library are all live.

Last updateAug 24, 2026 LicenseNOASSERTION PrimaryTypeScript
  • TypeScript
  • Electron
  • Svelte
  • Vite
  • Python
  • essentia.js
  • aubio
  • PHP
  • just
  • GitHub Actions
  • Windows 11
Iblis — Local-first AI music workstation for Windows — an Electron shell with a hot-swappable plugin architecture.
Iblis media
Iblis media
Iblis media

Iblis is a local-first AI music workstation for Windows 11. It is built to run entirely on the user's machine — offline by default, no cloud dependency, no account or sign-in. The application is an Electron shell with a deliberately small core; almost every capability is a plugin.

Plugin-first architecture

  • The shell ships only text-to-song. Image generation, stem splitting, BPM/key detection, waveform visualization, the node editor, and the file-explorer view are all hot-swappable plugins against a strict plugin contract.
  • Plugins and skins are orthogonal — skins never reach into plugin logic and vice versa.
  • Skins are first-class. Four ship by default — dark-3d (the default, red/blue lens styling), light-paper, infernal, and cathedral — all expressed through a single shared design-token vocabulary so themes are live-swappable without touching component code.

How it's wired

The workstation is strict TypeScript on Electron, with a Svelte + Vite renderer. Audio analysis runs in-process via essentia.js and aubio for tempo and key detection; the generation engine is a Python model server the shell talks to over a neutral engine-provider interface, so no single model's dialect leaks into the host. The public site and release channel at iblis.meiuxmeiux.com is a small PHP application (phpstan level 7+) that serves a signed release catalog — a versioned JSON manifest plus detached signatures — so the installer can verify and pull the latest signed build. All developer workflows go through just; CI runs on GitHub Actions.

Status

Iblis is in public alpha and shipping continuously. Live today: the Windows installer and auto-update channel, the signed plugin host and plugin SDK, the generation flow, the skin/design-token system, and a track library with search, folders, sorting, and detected BPM/key badges on every row. Current work is the v2 engine contract — a closed-set, strictly-parsed descriptor format that lets third-party generation engines plug in without trusting their claims. CHANGELOG.md and ROADMAP.md on the site render straight from the repo, so the public history is the real one.

Straight from the source

The project's own README.

Rendered in place — every link, image, and code block carried over from the repo. The page below is what a contributor would see opening the project for the first time.

Iblis

Local-first AI music workstation for Windows 11. An Electron shell with a strict plugin architecture — every capability beyond text-to-song (image gen, stem split, BPM/key detect, waveform vis, node editor, file-explorer view) is a hot-swappable plugin. Themes/skins are first-class and orthogonal to plugins.

Brand parent: Meiux Meiux LLC. Owner: Jack (saintpetejackboy). Site: https://iblis.meiuxmeiux.com (vhost on this server). Repo target: github.com/saintpetejackboy/iblis (private).

Getting started

just doctor       # check prerequisites
just dev          # run the Electron shell with HMR (desktop required)
just site-dev     # site only (PHP built-in server)
just site-deploy  # production Composer install + checked Apache reload

See docs/quick-start.md for the full walkthrough.

Where to look

You want to… Read
Understand the project scope and rules docs/00-charter.md
Pick up the repo cold (human or AI) docs/quick-start.md
Understand the architecture in one page docs/architecture.md
Author or modify a plugin docs/feature/plugins.md
Author or modify a skin docs/feature/skins.md
Add a waveform visualization docs/feature/waveforms.md
Touch the audio engine plugin docs/feature/engines.md
Add a processor (stems, BPM, key) docs/feature/processors.md
Edit the website docs/feature/website.md
Calibrate the Lucifer running-gag tone docs/feature/copy-and-tone.md
See what's planned vs shipped ROADMAP.md / CHANGELOG.md

The website renders CHANGELOG.md and ROADMAP.md directly from this repo. There is no second copy.

House rules

Enforced by review and (where possible) by CI. Full list in docs/00-charter.md §House-Rules. Highlights:

  • Files soft-cap ~400 LOC, functions ~80 LOC, CSS ~250 LOC. Split when a file is doing two things, not when a counter ticks.
  • Strict TypeScript; PHP at phpstan level 7+.
  • No secrets in source; .env only.
  • Additive-only DB migrations.
  • All dev workflows go through just.
  • No emojis in product copy. Ever.

Status

The Windows installer, auto-update channel, signed plugin host, ACE-Step engine, skin system, generation flow, and library core are live. Run just pickup for the exact released versions, any active human-test wait, and the next concrete step; CHANGELOG.md and ROADMAP.md carry the public history and direction.

Build something like this

Want a tool like this for your shop?

We've shipped this kind of thing before. Twenty-minute intro call, no slides.