Marketplace · Overview
Docs / Marketplace

Overview

One-click deploy of popular open-source apps — databases, CMS, e-commerce, dev tools, and monitoring — from the console.

The Marketplace lets you deploy popular open-source applications with a single click from the console. Browse a curated catalog by category, pick an app, confirm its configuration, and NevTan provisions it for you — no Dockerfiles or manual setup required.

New to cloud hosting?
Every page in this section is written assuming no prior experience — technical words like "container", "region", and "environment variable" are explained the first time they matter. If you want the full glossary and a complete, click-by-click walkthrough up front, start with Deploying apps.

Why it exists

A lot of what teams self-host is the same handful of well-known software — a database engine, a CMS, a storefront, a dashboarding tool. Working out a container image, wiring up configuration, and picking sane defaults for each of these is repetitive work that has nothing to do with your actual product. The Marketplace exists to skip that: pick a known-good app from the catalog and NevTan handles the image, configuration, and rollout for you.

The catalog spans five categories — databases, e-commerce & CMS, developer tools, monitoring, and security — with twenty-six apps between them. Each app ships with sensible defaults so it runs immediately after deploy, and every app in the catalog has already been packaged and tested to run cleanly on NevTan.

CategoryExample appsTypical use
DatabasesPostgreSQL, MySQL, MongoDB, Redis, Elasticsearch, ClickHouseA self-managed engine, or one not covered by managed Databases
E-commerce & CMSWooCommerce, WordPressAn online store or a content site, on WordPress
Developer toolsGitea, code-server, Adminer, n8nSelf-hosted git, a browser IDE, DB admin, or workflow automation
MonitoringGrafana, Prometheus, Uptime Kuma, Netdata, Grafana LokiDashboards, metrics, logs, and uptime checks for your own infrastructure
SecurityVaultwarden, HashiCorp VaultA self-hosted password manager, or a secrets store for your apps

Browse by category

Each category has its own page listing every app in it and how to deploy them.

Marketplace app vs. deploy your own repo

Both paths end up as an ordinary App Platform project, so the choice is really about where you're starting from — well-known software you just want running, or your own code.

Marketplace appDeploy from git
You start fromA pre-packaged, tested imageYour own repository and branch
Setup effortA short config formFramework detection or a Dockerfile
Best forWell-known self-hosted software (databases, CMS, dev tools, monitoring)Your own application code
CustomizationWhatever the config form exposes, then unlimited once deployedFull control from the first commit
Auto-deploy on pushNo — there's no repo of yours to watchYes, via auto-deploy
Ongoing managementSame App Platform project toolsSame App Platform project tools

How it works

Browse catalog
category or search
Pick an app
read details + options
Configure
review defaults in a form
Deploy
one click
Manage as a project
logs, domains, resources
  1. Open the Marketplace tab and browse the catalog by category, or search for an app by name — no sign-in required just to look around.
  2. Click into an app to read its description and see its configurable options before committing to a deploy.
  3. Review the configuration form — most apps deploy immediately with sensible defaults, so this step is often just confirming them.
  4. Click Deploy. NevTan creates a project for the app on the App Platform, the same way a git-based deploy would.
  5. Manage it like any other project: logs, custom domains, resources, and lifecycle.
Note
Deployed marketplace apps run as projects on the App Platform. Once deployed, everything you know about projects — logs, custom domains, and resource presets — applies exactly the same way as for a project you deployed from your own git repo.
Tip
Not sure which app fits your use case yet? Start with Browsing apps to see categories, search, and featured picks before deploying anything.
Important
The config form only exposes the settings the app's package was built with — it isn't a full settings UI for the underlying software. If you need to go further, you're not stuck: the deployed project is a normal App Platform project, so you can still edit its Dockerfile, add environment variables, or change its resource preset after the fact.

In this section