Skip to content
Sencai.docs

Marketplace

Marketplace (/gravity/marketplace) is a catalog of ready-to-deploy applications published by Sencai and by other organizations, alongside a publishing flow if you want to offer your own.

Browsing and deploying

Section titled “Browsing and deploying”

The Apps tab lists every approved app, publicly - anyone can browse it, even signed out. Search by name or description. Opening an app shows its publisher, description, and (once approved) a Deploy button that pre-fills the instance creation wizard with the app’s image and its parametrized configuration, the same way a registry image does.

A listing consists of:

  • A name, description, and optional icon.
  • An image reference (registry/namespace/name:tag) - the container image that gets deployed.
  • A config template - a small JSON document that maps onto the instance wizard’s own fields (provider, region, instance type, root disk size, additional disks, tags, environment variables, and a cloud-init script), so deploying the app pre-fills those choices instead of leaving you to work them out from documentation.

Submitting your own app

Section titled “Submitting your own app”

Submit an app (/gravity/marketplace/submit) is open to any signed-in user; publishing under a specific organization requires an admin role in that organization (enforced when you submit, regardless of which organization you pick in the form).

The form asks for the organization to publish under, a name, a description, the image reference, and the config template as JSON. On submit, Sencai creates the listing as a draft and immediately submits it for review - if the review submission step itself fails, the draft is kept and you can retry from the app’s own detail page.

Review process

Section titled “Review process”

A submission moves through:

Draft → Pending review → Approved (or Rejected)

  • While pending review, only a platform admin can approve or reject it. Your organization can still withdraw it back to draft from the app’s detail page.
  • Approval is blocked if the submitted image has any open critical or high-severity vulnerability finding - the review screen shows exactly which findings are blocking it. Resolve them via Vulnerabilities (accept the risk or mark fixed) and the app can be approved once the scan clears.
  • If security scanning itself fails for a technical reason (rather than finding something), that’s shown separately as a scan error on the app’s own page - resubmitting triggers a fresh scan.
  • Once approved, the app appears in the public catalog. A platform admin can suspend it at any time, which removes it from the catalog without affecting instances already deployed from it.
  • If rejected, the reason is shown on the app’s detail page.

Versioning

Section titled “Versioning”

An approved app’s image reference and config template are locked - you can’t edit them directly once review has passed. There’s currently no in-app path to publish a new version of an already-approved listing; publish a new listing for a new image or configuration.

Revenue share

Section titled “Revenue share”

If your listing has a configured revenue-share fee, it’s shown as a percentage on the app’s own detail page (visible to your organization and to platform admins only) - the fee that applies is the one in effect at the time of each individual purchase, not retroactively affected by later changes.

What’s next

Section titled “What’s next”