The marketplace is the catalog of apps you can install on a Suji VM. Each entry is a vetted compose template with a fill-in-the-blank form for credentials, ports, and feature toggles. The full source lives in suji-hq/suji-templates — anyone can read it, propose a new app, or audit how an existing one is wired.Documentation Index
Fetch the complete documentation index at: https://docs.suji.fr/llms.txt
Use this file to discover all available pages before exploring further.
Currently available
| App | What it is | Exposable | Status |
|---|---|---|---|
| OpenClaw | Multi-channel AI messaging bot (Telegram / Discord / WhatsApp / Slack) | ✅ | Stable |
| n8n | Workflow automation — visual node-based pipelines | ✅ | Stable |
| Ghost | Modern blogging / newsletter platform | ✅ | Stable |
| NocoDB | Open-source Airtable alternative | ✅ | Stable |
| Plausible | Privacy-friendly web analytics | ✅ | Stable |
| Wiki.js | Open-source wiki / knowledge base | ✅ | Stable |
How an install works
- You click Install on an app’s marketplace page.
- You pick the VM to install on (must have free capacity).
- You fill in the form — required secrets, optional toggles, subdomain suggestion.
- Suji renders the compose, ships it to your VM via cloud-agent, runs
docker compose up -d, wires the Cloudflare Tunnel ingress. - Status flips to
running. The app is reachable at its*.suji.frURL.
What’s vetted
Before an app lands in the catalog, the maintainer team checks:- Image source — official upstream image or a trusted publisher.
- Pinned version — no
:latest, no floating major (:1). Exact tag. - Sane compose — no
privileged: true, nonetwork_mode: host, no host port bindings, no bind mounts outside the install’s volume. - Form completeness — every required env in the compose is either user-input or auto-generated.
- Resource cap —
deploy.resources.limits.memoryset, ≤ recommended VM size. - Documented license — real SPDX, not in the denylist.
Adding a new app
The catalog is a public repo. To propose a new app:- Fork suji-hq/suji-templates.
- Copy an existing app’s folder (the repo’s README is the contributor guide).
- Edit the
compose.yaml,manifest.yaml, andicon.svgfor your app. - Open a PR — the team reviews against the checklist above.
Updates after install
Each app has an upgrade policy in its manifest:automatic— safe to upgrade in place. The dashboard offers a one-click upgrade when a new catalog version lands.breaking-changes-flagged— stateful apps with migrations or known break-points. The dashboard surfaces a diff for you to acknowledge first.
Next
OpenClaw guide
Full ops guide for the OpenClaw install.
App concept
What an “install” is and how it relates to the VM.