Skip to main content
The marketplace offers application templates with configuration forms, resource estimates and deployment instructions. The public packaging source is suji-hq/suji-templates.

​
App guides

The dashboard is the reference for current availability, versions and any disabled installs. These guides describe the packaged setup; a listing is not a stability certification or a guarantee of every upstream feature.

​
How an install works

  1. Open an app in Apps and select Install.
  2. Choose an existing running VPS or create one with enough resources for the OS and all its apps.
  3. Complete the app’s required settings and review exposure and resource requirements.
  4. Deploy and follow progress. The app may still require an owner account, channel pairing or other first-run setup.
  5. Use the connection details shown by Suji. Exposed web apps have an HTTPS URL; non-web services use their documented protocol and port.
See Install your first app. CPU and memory estimates help with sizing; they do not reserve capacity or guarantee performance.

​
Validation, licences and support

Suji validates the manifest and Compose structure, permitted image registries, ports, mounts and declared resource limits. These checks constrain packaging; they do not certify upstream code, security, legal compliance or fitness for your workload. Image tags and bundled dependency versions vary by template, so inspect the source and release notes when reproducibility matters. Each application has its own licence and may include paid features or external API costs. Check the upstream terms for your intended use. A public template does not mean all bundled software shares an open-source licence. Use the app’s listed upstream resources for application-specific help. Report packaging problems through the templates issue tracker, and Suji platform issues through dashboard Support. You manage application configuration, access, data and updates.

​
Updates and contributions

Review release notes and take an appropriate backup before choosing Upgrade. Suji retains named data volumes during an upgrade, but the application may migrate their contents; retaining a volume does not make a migration reversible. Manifests use automatic, manual or breaking-changes-flagged as upgrade-policy metadata. The dashboard’s upgrade action asks for confirmation; the policy label is not a compatibility guarantee or a promise of a detailed migration diff. Customized Compose installs have separate editing and upgrade restrictions. To propose an app, follow the templates repository contributor instructions and open a pull request. Accepted changes must pass catalogue synchronization before they appear. Sync can be triggered by a webhook or the periodic job; there is no guaranteed publication time.

OpenClaw guide

Configure the gateway and channels.

App concept

Installs, data and lifecycle actions.