Publish your application

What can be listed

Business applications

An application of the Business OS: its own repository with a maludb-os.json manifest, installable by the kernel's app_install.php, following the integration contract. Build it with the htmx-php-builder plugin and it fits from the first commit.

Desktop applications

A native application for the MaluOS Desktop (GNOME 50, Ubuntu 26.04 base), packaged as a .deb. Packages published on apt.maluos.com install from the MaluApps window; packages hosted elsewhere are listed with a download link and install notes.

Utilities

Command-line tools, services, libraries and Claude Code plugins that work with MaluDB or MaluOS: an apt package, a GitHub release with a checksum per file, a Homebrew formula or a plugin marketplace.

The catalogue entry

Add one object to data/apps.json in github.com/maludb/maluapps. The required keys:

{
  "id": "my-app",                      // lower-case, hyphens; the URL is maluapps.com/apps/my-app
  "name": "My App",
  "tagline": "One sentence, under 90 characters.",
  "description": ["A paragraph.", "Another, if needed."],
  "category": "business" | "desktop" | "utility",
  "icon": "box",                       // a Feather icon name (feathericons.com)
  "publisher": "Your company or name",
  "license": "MIT",
  "version": "1.2.0", "updated": "2026-10-29", "status": "stable" | "beta" | "early",
  "kind": "deb" | "web" | "release" | "source",
  "package": "my-app",                 // kind deb: the apt package
  "catalog_key": "my_app",             // kind web: the key in maludb-os.json
  "requires": ["maluos-desktop"],      // or ["office"] for a Business OS app
  "platforms": ["MaluOS Desktop 26.04"],
  "repo": "https://github.com/you/my-app", "docs": "https://…",
  "downloads": [{"label": "…", "url": "https://…", "size": "12 MB", "platform": "amd64", "checksum": "https://…"}],
  "install": [{"title": "On MaluOS Desktop", "steps": ["Plain text.", {"cmd": "sudo apt install my-app"}]}],
  "features": ["…"], "tags": ["…"]
}

Run php bin/validate-catalog.php before you open the pull request; it checks the keys, the icon and the links.

What we check

The software does what the entry says and installs with the steps given, on a current MaluOS.
Source is public and the license is stated. Binaries come with a checksum or a signature.
A Business OS application honours the kernel's contract: single sign-on at its sso_path, people and access through the directory API, agents through the kernel's chat endpoint and never a model key of its own.
Nothing phones home beyond what the description says.

Questions, or an application that is not on GitHub: write to Kinetic Seas through the contact form on the site.