App Platform: Creating and Running Your Environments

The App Platform runs WordPress, WooCommerce, Magento, Nextcloud, Twenty, Ghost, Langflow and Mautic for you — each in its own sealed environment, with its own database, storage and network boundary. You create and manage everything yourself in the Radibase panel: pick a product and a plan, switch on the features you need, add your sites and domains, and click Install. This guide walks through the whole lifecycle.

Concepts

  • Environment — what you buy: one product (for example WordPress or Nextcloud) on one plan, in one region. It holds the database, storage and pods of your applications, isolated from every other customer.
  • Instance — one application inside the environment. A WordPress environment can hold many sites (each one an instance); the other products run one instance per environment.
  • Plan — the size of the environment: CPU, memory and disk, reserved for you.
  • Feature — a capability we run for the whole environment, with its own pods and resources carved from your plan (for example Redis for WordPress, or office and Talk for Nextcloud).
  • Extension — software installed into one instance, with no pods of its own (for example WooCommerce on one WordPress site).
  • Domain — a hostname an instance answers on. An instance can have several; one of them is the primary.

Plans and resources

Every plan is a number of quarters; one quarter is 4 vCPU, 16 GB RAM and 100 GB disk.

  • Standard — 1 quarter: 4 vCPU, 16 GB RAM, 100 GB disk
  • Pro — 2 quarters: 8 vCPU, 32 GB RAM, 200 GB disk
  • Pro Plus — 3 quarters: 12 vCPU, 48 GB RAM, 300 GB disk
  • Business — 4 quarters: 16 vCPU, 64 GB RAM, 400 GB disk
  • Business Plus — 5 quarters: 20 vCPU, 80 GB RAM, 500 GB disk
  • Enterprise — a custom size (multi-region Sofia–Amsterdam, replicated databases and more), on request

Two products differ: Magento starts at Pro, because the full Magento stack needs it, and Ghost is offered from Standard to Pro Plus. Current prices are on the App Platform page.

The plan's resources are split between the pods of your environment automatically — application pods, database, cache, background workers and any features you switch on. Memory and disk are reserved for you (request = limit); CPU runs up to your plan's full limit. On Shared CPU the physical cores are shared at a deliberately low ratio; on Dedicated CPU your cores are backed 1:1 by physical hardware. Isolation, memory, disk and features are the same in both.

Every fixed plan runs at least two application pods, so your sites keep serving while a pod restarts or moves to another node.

Creating an environment

  1. In the panel, open App Platform Environments and click New.
  2. Enter a Name (for you) and a Code — a short lowercase identifier (letters, digits, dashes). The code names your environment everywhere on the platform and cannot be changed later.
  3. Choose the App Platform Type (the product) and the App Platform Plan. Only the plans available for that product are offered.
  4. Choose where it runs: Cloud Provider, Cloud Region and Data Center (Sofia or Amsterdam), and the Kubernetes Cluster — Shared CPU or Dedicated CPU.
  5. Tick the Features you want (see below) and save. The vCPU, RAM and disk of the environment come from the plan.
  6. Open Instances on the environment and add your first instance: a Name and a Code (for WordPress, the code of the site), and tick any Extensions.
  7. Open Domains on the instance and add its domain(s). Mark one as Primary; the others redirect to it.
  8. Back on the environment, click Install Env.

Nothing is created in the cluster until you click Install Env — you can prepare everything first.

What Install Env does

One click does the whole setup, then reports what it did:

  • Credentials — generates every password and key your environment needs (database, admin account, SFTP and so on) and stores them in the platform's secret store. You see them under Secrets on the environment and on each instance.
  • Ports — assigns the ports for SFTP, the database tunnel and (Magento) the CLI workspace, shown under TCP Ports.
  • Configuration — writes your environment's configuration (product, plan, features, instances, extensions, domains) and the platform deploys it: pods, database, storage and network policies.
  • Edges — turns on automatic TLS for your domains, opens your SFTP and database-tunnel ports on our edge, and (Nextcloud Talk) the call relay.
  • Where to point things — writes the IP your domains must point to (dns_a, under the instance's Params) and the IP for SFTP and the database tunnel (sftp_ip, under the environment's Params).

Install is safe to repeat: run it again after any change — a new plan, a feature switched on or off, a new site, a new domain — and it applies only the difference. Your data stays in place.

Features and extensions

Features and extensions have no price of their own: they are part of your plan. A feature takes its resources from the plan, so the panel offers a feature only on plans where it fits next to your applications.

Features (per environment)

  • Redis object cache — WordPress, from Standard. A cache server for all sites of the environment. Uses 0.5–1 vCPU and from 256 MB.
  • Collabora Online — Nextcloud, from Pro. Real-time document co-editing. Uses 2 vCPU and 4 GB.
  • OnlyOffice — Nextcloud, from Pro. Real-time document co-editing; you can run it next to Collabora. Uses 2 vCPU and 4 GB.
  • Talk — Nextcloud, every plan. Chat and audio/video calls; from Pro the high-performance call backend for larger meetings is added automatically. Uses 0.5 vCPU and 1 GB.
  • Talk Recording — Nextcloud, from Pro, together with Talk. Uses 3.5 vCPU and 7 GB.

All four Nextcloud features together need Business or above.

Extensions (per instance)

  • WooCommerce — WordPress, from Standard. Installed and activated on that site at install; the plugin is yours afterwards (switching the extension off does not uninstall it). We recommend the Redis feature with it.
  • AI connector — WordPress. Coming soon.

To switch one on or off: tick or untick it on the environment (features) or the instance (extensions), save, then click Install Env or Install Instance. Switching a feature on or off is a rolling change — your sites keep serving.

Domains and DNS

DNS stays with you, wherever your domains are registered.

  1. Add the domain under Domains on the instance (mark it Enabled; one domain per instance is Primary).
  2. Click Install Instance (or Install Env).
  3. At your DNS provider, create an A record for the domain pointing to the IP in the instance's dns_a param.

By default your domains are served from the shared IP of our EU edge (the dns_a value). If you need a dedicated IP — for allowlists, compliance or a partner's firewall — ask us through a support ticket; we set it up and update dns_a.

The TLS certificate is issued automatically on the first visit once DNS points to us, and renewed automatically. Additional domains of an instance redirect to its primary domain.

Renaming, disabling or deleting a domain removes its certificate permission right away; remove the DNS record yourself when you no longer need it.

Access: admin, SFTP, database, CLI

Your passwords are under Secrets — on the environment, and for WordPress also per site. Use Get From Vault to show the current value.

Admin accounts

  • WordPress — /wp-admin on the site's domain, user admin, password wp-admin-password-<site code>.
  • Magento — the admin path of your store, user admin, password admin-password.
  • Nextcloud — user admin, password admin-password.
  • Mautic — user admin, password admin-password.
  • Langflow — user admin, password superuser-password.
  • Ghost and Twenty — the owner account is created for you, with the password owner-password.

The admin (or owner) account of every product except Langflow gets the email address in the environment's admin_email param. On the first Install Env it is set to the email of your Radibase account; to use another address, add admin_email under Params before the first install. The account is created once — change the email later in the application itself.

SFTP (WordPress, Magento) — connect to the sftp_ip of the environment on the SFTP port shown under TCP Ports. On WordPress every site has its own SFTP user (the site code) and password (sftp-password-<site code>), restricted to that site's files. On Magento, SFTP uses the CLI login (user magento, password cli-password).

sftp -P <sftp port> <site code>@<sftp_ip>

Database tunnel (WordPress, Magento) — a forward-only SSH tunnel to your own database server, for your own tools (MySQL Workbench, DBeaver, the mysql client). Log in as user dbtunnel with the password dbtunnel-password, then connect your client to the forwarded port with the database user and password of the site.

ssh -N -L 3306:<type>-<env code>-db:3306 -p <dbtunnel port> dbtunnel@<sftp_ip>

Here <type> is wp or mg. On WordPress each site's database user is <site code>_usr (dashes become underscores) with the password db-password-<site code>.

Magento CLI workspace — SSH on the CLI port as user magento (password cli-password): bin/magento, Composer and n98-magerun2 on the live codebase.

Changing your plan

Choose another plan on the environment, save and click Install Env. The change applies in place: pods roll one by one, the database keeps its data, and the disk grows online. Disks grow but never shrink — moving to a smaller plan keeps the larger disk until you ask us otherwise.

If a smaller plan has no room for a feature you use, switch the feature off first.

Deleting

Deleting cannot be undone — download what you want to keep first.

  • Delete Instance (WordPress sites) — removes the site: its files, its database and database user, its domains and their certificates, and its secrets. Other sites of the environment keep running.
  • Delete Env — removes the whole environment: all instances, the database and every volume, the ports, the certificates and the secrets.

Both ask you to type delete to confirm. If a step fails (for example a temporary connection problem), clicking the button again continues where it stopped. DNS records stay with you — remove them at your DNS provider.

Notes per product

  • WordPress — many sites per environment, each a separate installation with its own database, user and SFTP account (not WordPress multisite). Minor security releases apply automatically; major updates are yours.
  • WooCommerce — a WordPress environment with the WooCommerce extension on the store's site; add the Redis feature for a growing store.
  • Magento — Magento Open Source 2.4 in production mode, with its own OpenSearch, Redis and cron worker. One instance serves all your storefronts: add each storefront domain to the instance, then map it to a store in the Magento admin.
  • Nextcloud — one instance for your whole team, users and groups managed in the Nextcloud admin; office and Talk are features.
  • Twenty — your own CRM with its own PostgreSQL and background worker; invite your team from Twenty's settings.
  • Ghost — a cache tier in front of Ghost serves your public pages from memory; configure newsletter sending in Ghost's settings.
  • Langflow — private by default (no auto-login). Bring your own LLM provider keys; inference runs at the provider, not in the environment.
  • Mautic — configure your sending (SMTP) in Mautic's settings; segments, campaigns, the message queue and broadcasts run on schedule in a worker sized from your plan.