Accounts and app-to-app calls — outside the Linux desktop.
CommunicationBuilt-in💎 Premium available
Included — no install needed
About
The account layer that sits outside the Linux desktop: public users who sign into apps' public pages, and the switchboard for the app-to-app API. Each profile also carries its own regional preferences across devices and can invite new users when the administrator enables invitations.
What it does
Public user accounts, independent from Linux logins, for apps' public pages.
The app-to-app API gate — enables one app's backend to call another's in-process, off by default per app.
For any app that exposes one, the individual actions its API offers — name, parameters and description — auto-discovered from its own code, so the admin can see exactly what an integration would be able to call before enabling it.
A directory of installed apps' public pages.
A Store tab where each profile picks which of those apps sits on its own home screen — removing one only hides the card, so nothing the app saved is lost and it can be added back at any time.
Per-profile home screen, sort order and category kept on the server, so the same account opens the same way on a phone and on a computer.
Per-profile date format, time format and currency preferences shared by public apps across devices.
Seven-day single-use invitation links, which can be combined with closed public registration for invitation-only accounts.
Public user management for the admin.
💎 With Premium
Credits
Every public user gets a credit balance, and any installed app can spend from it or grant to it through the Platform API — a charge per generation, a reward for finishing something, a refund when a job fails. Spends are atomic and idempotent: a retried request returns the original result instead of charging twice, and two requests racing against a balance that only covers one of them cannot both succeed. Users see their balance and every transaction on their public pages; the administrator can top up or correct any balance from Apps Hub. Without a licence the balance does not exist at all, and apps that ask for it are told so, so they fall back to working for free rather than showing a lock.
Credit-priced actions
Installed apps declare the optional actions they can charge for, and Apps Hub discovers them automatically — no configuration file to write and nothing to wire up per app. The administrator sets a price per action from Apps Hub, either from the app's own row or from one list of every priced action on the installation, and the charge is resolved and taken entirely on the server, so an app never decides what it costs. Leaving a price at zero keeps the action free. Without a current licence every price is paused rather than lost: users are charged nothing, the saved figures stay put, and renewing brings them straight back.
Custom public app names
Assign a separate public display name to Apps Hub or any published app without changing its internal identifier or URL. The custom name follows the app across the public directory, page title and navigation. Inside the desktop the rename control remains visible without Premium and opens the subscription prompt; public pages simply keep using their original names.
Lets any installed app call another's app_api.py functions in-process, gated per target app.
Your privacy choices
We use essential storage to keep the website secure and working. With your permission, we also use Google Analytics to understand site usage and improve mvmOS. You can change your choice at any time in Cookie settings.