Database engines available on your server
The database engines JSOPanel supports and how they're made available to customers.
JSOPanel supports three database engines (MariaDB, PostgreSQL, and MongoDB), so your customers can use whichever fits the application they're running. From the Databases page, an account chooses an engine from a dropdown when creating a new database, and can create as many as its package allows.
MariaDB
The most common choice, and the default expectation for applications like WordPress, Joomla, and most PHP-based software. It's selected by default and most one-click application installers use it automatically.
PostgreSQL
A good choice for customers running applications that specifically require it, or who prefer its feature set for more complex data needs.
MongoDB
A document-oriented database, useful for customers building applications, particularly Node.js applications, that are designed around this style of data storage.
Installing PostgreSQL and MongoDB
MariaDB is always available. If PostgreSQL or MongoDB aren't installed on your server yet, the Databases page tells you so and shows only the engine dropdown for what's actually installed. Once you install one, it becomes available to every account whose package includes the Databases feature, there's no separate per-package setting for which engine an account may use.
Controlling access to databases generally
Whether an account can reach the Databases page at all is controlled by the "Databases" feature on the package it's on, see the article on creating and editing packages. An account without it sees no Databases page and is refused if it tries to reach the address directly.
Managing databases without extra software
JSOPanel includes a built-in, web-based database browser (Adminer), reached with a single sign-on click from the Databases page, so customers can view and edit their data, run queries, and manage users without installing any separate database administration tool.
Per-account Redis
Accounts can also be given their own private Redis instance for caching on the same Databases page, controlled by the "Redis" feature on their package. Each account gets its own separate instance, reachable only from inside that account, rather than one instance shared across the server.