Supported Database Engines
Skytells supports five managed database engines — PostgreSQL, MySQL, MariaDB, MongoDB, and Redis. Each runs as a container inside your project's private network with auto-generated credentials and a unique internal port.
Skytells provisions the database engine you choose as a managed container inside your project. The container gets an internal host and port on the project's private network, auto-generated credentials, and a ready-to-use connection URL — all shown in the database overview immediately after creation.
Choose your engine at creation time. The engine type cannot be changed after the database is created.
PostgreSQL
Reliable relational database. The recommended choice for most production workloads — structured data, complex queries, foreign keys, and ACID transactions.
| Property | Value |
|---|---|
| Default internal port | 5432 |
| Connection URL format | postgresql://username:password@internal-host:5432/database-name |
| Best for | Web apps, APIs, transactional data, analytics |
PostgreSQL is the default selection in the New Database dialog. It supports full SQL, JSON columns, indexing, and a rich ecosystem of extensions.
MySQL
Popular open-source RDBMS. Widely supported across frameworks, ORMs, and hosting ecosystems. A solid choice if your stack or team already works with MySQL.
| Property | Value |
|---|---|
| Default internal port | 3306 |
| Connection URL format | mysql://username:password@internal-host:3306/database-name |
| Best for | Web apps, CMS platforms, frameworks with MySQL-first ORMs |
MySQL is compatible with most SQL-based ORMs and libraries, including Prisma, Sequelize, SQLAlchemy, and Laravel's Eloquent.
MariaDB
Community-driven MySQL fork. Drop-in compatible with MySQL and often used where performance characteristics or licensing of MySQL are a concern.
| Property | Value |
|---|---|
| Default internal port | 3306 |
| Connection URL format | mysql://username:password@internal-host:3306/database-name |
| Best for | MySQL-compatible workloads, teams preferring a fully open-source stack |
MariaDB uses the same wire protocol and client libraries as MySQL. Most MySQL connection strings and drivers work with MariaDB without changes.
MongoDB
Document-oriented NoSQL database. Stores data as flexible, schema-free BSON documents. Suited for workloads where the data model evolves frequently or where a document structure fits naturally.
| Property | Value |
|---|---|
| Default internal port | 27017 |
| Connection URL format | mongodb://username:password@internal-host:27017/database-name |
| Best for | Content management, catalogs, user profiles, event data, flexible schemas |
MongoDB's aggregation pipeline, indexing, and geospatial query support make it suitable for a wide range of read-heavy and analytical workloads beyond simple document storage.
Redis
In-memory key-value store. Operates entirely in memory for extremely low-latency reads and writes. Commonly used as a cache, a session store, a pub/sub message broker, or a job queue backend.
| Property | Value |
|---|---|
| Default internal port | 6379 |
| Connection URL format | redis://:password@internal-host:6379 |
| Best for | Caching, sessions, rate limiting, queues, pub/sub, leaderboards |
Redis data structures — strings, hashes, lists, sets, sorted sets, streams — let it handle many coordination and caching patterns that would otherwise require a separate service.
Redis stores data in memory. By default, data is persisted to disk periodically, but Redis should not be treated as a primary database for data that cannot be reconstructed. Use Redis alongside a relational or document database, not as a replacement.
Default Ports Reference
| Engine | Default Internal Port |
|---|---|
| PostgreSQL | 5432 |
| MySQL | 3306 |
| MariaDB | 3306 |
| MongoDB | 27017 |
| Redis | 6379 |
These are the internal (container) ports. When you expose a database to the internet, you choose a separate external port that must not conflict with any other service running in the same project.
Related
- Databases Overview — internal vs. external credentials, the security model, and how databases fit into a project.
- Create a Database — step-by-step provisioning guide.
- Enterprise Network — how internal hostnames and ports work inside a project.
How is this guide?
Overview
Skytells managed databases run as containers inside your project's private network. They are internal-only by default and reachable by all apps in the same project without any configuration. You can expose a database to the internet when needed.
Create Database
Step-by-step guide to provisioning a managed database inside a Skytells project — choose an engine, configure credentials, and connect your apps over the private network in minutes.