Deploying apps

A complete, no-experience-needed walkthrough for creating an instance of any Marketplace app — every field explained, for all three deploy types.

This page is the complete, step-by-step guide to creating an instance of any app in the Marketplace — written for someone who has never deployed anything to the cloud before. It explains every word, every field, and every screen you will see.

Before you start: words you'll see

A few words come up again and again while deploying an app. Here is what each one means in plain language, before you run into it on screen.

The three ways a Marketplace app deploys

Every one of the 26 apps in the catalog falls into one of three deploy types, shown as a colored badge on its card. The badge tells you which of the three guides below to follow — the fields you'll be asked to fill in depend entirely on this, not on which specific app you picked.

Guide 1: Creating a Managed Database instance

This guide covers the four Managed DB apps: MySQL, PostgreSQL, MongoDB, and Redis. "Managed" means NevTan takes care of running and generates a password for the database for you — you only decide its name, who can connect to it, and how big it should be.

1. 1
   Open the Marketplace

   From the console's sidebar, click Marketplace under the Operate section. You'll see a search bar at the top and a grid of app cards below it, each with a name, an icon, and a badge like "Managed DB" or "1-Click Deploy".
2. 2
   Find your database engine

   Use the Databases category link on the left, or type the engine's name (e.g. "PostgreSQL") into the search bar at the top. Every Managed DB app carries a blue Managed DB badge on its card.
3. 3
   Click the app's card

   Clicking a card opens a panel that slides in from the right-hand side of the screen. This panel is both the app's name/type and the form you'll fill in — there is no separate "read more first" page to visit before this.
4. 4
   Fill in the Database Name

   Type a name for your database, for example my-shop-db. This is required, and it's just a label to help you recognize this database later in your list of databases — it does not need to match anything else.
5. 5
   Fill in the Username

   Type a username for the database account NevTan will create for you, for example app_user. This is required. It can only contain letters, numbers, and underscores, and must be 16 characters or fewer. This is not your NevTan login — it's a separate account just for this database.
6. 6
   Choose the Network

   Pick Public if you want the database reachable from anywhere on the internet — access is still gated by the username and password from the steps above, but there's no separate address allowlist. Pick Private network if it should only be reachable from other things running inside NevTan, which unlocks an extra field for narrowing that down further (see the next step). If you're not sure, Public is the simpler starting choice.
7. 7
   Optionally set Trusted IPs

   This field only appears if you chose Private network. It lets you list specific internet addresses (IPs or CIDR ranges — a way of describing a whole block of addresses at once) allowed to connect. Leave it blank to allow anything on the private network to connect; fill it in to narrow that down further.
8. 8
   Choose a Region

   Open the Region dropdown and pick the data center location closest to where your users or your app actually are. This field is required — you cannot deploy without picking one.
9. 9
   Choose a Resource Size

   Pick Small (1 vCPU, 1 GB RAM), Medium (2 vCPU, 2 GB RAM), or Large (4 vCPU, 4 GB RAM). If you're just trying this out or building something small, Small is a reasonable starting point — you are not locked into this choice forever.
10. 10
    Optionally choose a Team

    If your account belongs to one or more teams, a Team dropdown appears, defaulting to "Personal (just me)". Pick a team here if you want everyone on that team to be able to see and manage this database too.
11. 11
    Click "🚀 Deploy Now"

    This button sits at the bottom of the panel and stays disabled (greyed out) until every required field above is filled in. Once you click it, NevTan starts creating your database.

After deploying (database)

The panel stays open and shows a colored status badge that updates on its own — you don't need to refresh the page. Here is what each status means:

Your connection details

When the status reaches ready, the panel reveals a Connection Details box with everything another program needs to talk to your new database:

• Host — the address of the server your database lives on.
• Port — a number that, together with the host, pinpoints exactly which service to talk to on that server.
• Database — the name you gave it in step 4.
• Username — the account name you gave it in step 5.
• Password — generated automatically for you. It's hidden by default (shown as dots); click the eye icon to reveal it, or the copy icon to copy it without ever displaying it on screen.
• URI — a connection string that bundles all of the above into one line that most database tools and programming languages can accept directly, so you rarely need to type out each piece by hand.

Guide 2: Creating a 1-Click Deploy instance

This guide covers every app carrying the green 1-Click Deploy badge — twenty apps, including things like Grafana, Gitea, Vaultwarden, and n8n. Despite the variety, every one of these apps uses the exact same short form to deploy — only the app itself differs.

1. 1
   Open the Marketplace and find the app

   From the sidebar, click Marketplace, then browse a category or search by name. Every 1-Click Deploy app carries a green 1-Click Deploy badge on its card.
2. 2
   Click the app's card

   A panel slides in from the right with the app's name and icon at the top, and the deployment form below it.
3. 3
   Check the Deployment Name

   NevTan pre-fills this with the app's name plus a few random characters (for example grafana-x7k2), so it's already unique. You can leave it as-is or change it to something you'll recognize more easily later.
4. 4
   Choose a Region

   Open the Region dropdown and pick where this instance should run. This is required.
5. 5
   Choose a Resource Size

   Pick Small (1 vCPU, 1 GB RAM), Medium (2 vCPU, 2 GB RAM), or Large (4 vCPU, 4 GB RAM), based on how much traffic or work you expect this instance to handle.
6. 6
   Optionally choose a Team

   If you belong to a team, pick it here to share this deployment with your teammates instead of keeping it personal.
7. 7
   Optionally review Environment Variables

   Click the "Environment Variables" row to expand it. Some apps pre-fill a few default settings here (for example, ones the app needs to start up); you can change any value, remove a row, or click "+ Add Variable" to add your own. If a note about auto-generated passwords appears here, it means this particular app will generate and show you a password after it deploys, rather than asking you to set one now.
8. 8
   Click "🚀 Deploy Now"

   This creates the instance and begins provisioning it, right inside the same panel.

After deploying (1-Click app)

The same status badge you'd see for a database appears here too, with one difference: instead of turning ready, a 1-Click app turns running once it's reachable.

Once running, the panel shows a clickable link to the app's live web address, plus a View deployment logs → button that takes you to its ongoing logs.

Guide 3: Deploying WooCommerce or WordPress

WooCommerce and WordPress are the two apps carrying the purple WordPress badge. Clicking Deploy on either one does not open the short form from Guide 2 — instead, it closes that panel and opens a separate, dedicated WordPress Deployment window, because setting up WordPress genuinely needs more information (its own domain, database, and admin account).

Step 1 — Add a domain. You need at least one address for your new site — a domain you already own, a free NevTan subdomain, or both.

1. 1
   Custom domain (optional)

   If you own a domain already (like mystore.com), type it into the Custom Domain field. You'll confirm you actually own it in the next step.
2. 2
   Platform subdomain (optional)

   Type a name into the Platform Subdomain field, for example myblog — NevTan completes the address as myblog.apps.nevtan.com for you. As you type, the console checks — in real time — whether that name is already taken, showing "Checking availability…", "Available", or "Taken — try another."
3. 3
   Click Continue

   You must fill in at least one of the two fields above. If you only used the free subdomain, there's no DNS to verify, so you're taken straight to Step 3. If you entered a custom domain, you move to Step 2 next.

Step 2 — Verify DNS (custom domain only). This step only appears if you entered a custom domain in Step 1. WordPress can't go live on your domain until you prove you actually control it, by pointing it at NevTan's server.

1. 1
   Copy the DNS record NevTan shows you

   The screen displays a table with a Type of A, a Name of @, and a Points to value that is NevTan's server address for your site.
2. 2
   Add that record at your domain registrar

   Log into wherever you bought your domain (this is outside of NevTan) and add an A record matching exactly what NevTan showed you.
3. 3
   Wait for DNS to spread

   This can take anywhere from a few minutes to about an hour. This waiting period is normal and outside NevTan's control — it depends on your domain registrar.
4. 4
   Click Verify Domain

   NevTan checks whether your domain now points to its server. If it does, you'll see a green "Domain verified!" message and a new Continue to Install button — click it to move to the next step. If not, you'll see a message explaining that it isn't pointing correctly yet — wait a little longer and click Verify Domain again.

Step 3 — Fill in the install details. This is the main setup form. It asks for more than a typical 1-Click app because it's setting up two things at once — the WordPress software itself, and the MySQL database it stores your content in.

Once every required field is filled in and a Server Configuration is selected, click 🚀 Install WordPress on Server.

Step 4 — Watch it install. This screen shows a status line at the top (for example "Provisioning environment…") and a live, scrolling log of exactly what's happening — installing Nginx (the web server), PHP, MySQL, and finally WordPress itself. This step typically takes about 2 to 4 minutes.

Step 5 — Finish WordPress's own setup. Once installation finishes, you'll see a success screen with your site's web address(es) and an Open WordPress Setup button. Clicking it opens WordPress's own, separate installation screen in a new tab — the same one every WordPress site in the world shows on first run. NevTan has already prepared the server and the database for you; this last screen is WordPress itself confirming your site title and admin details before your site is fully ready to use.

Understanding a failed deployment

Any of the three guides above can end in a failed status instead of succeeding. This isn't something to worry about — it usually just means a transient issue during setup, not a problem with your account.

• Open the deployment's logs (for 1-Click and database apps) or the installation log (for WordPress) to see what was happening when it failed.
• Try again — sometimes simply retrying, or picking a different region or resource size, resolves it.
• If it keeps failing the same way, that's worth reaching out about rather than repeatedly retrying the same configuration.

Finding your deployment afterward

Once something is deployed, here's where to find it again:

• Managed databases — appear in the dedicated Databases section of the console, alongside any database you created directly from there.
• 1-Click Deploy apps — appear under Your Deployments in the Marketplace tab; each entry links straight to its logs, domain, and resource settings.
• WordPress and WooCommerce sites — the success screen's "Go to Dashboard" button takes you back to your main console, where the new site behaves like any other project.