Engine versions
See which versions are available for each database engine, and understand why the version you pick matters beyond creation day.
Before creating a database, the Create Database form shows the versions available for whichever engine you pick.
Picking a version
Choosing an engine on the form populates its version dropdown with the versions currently supported for that engine — pick the one you want, then continue with package and region. See Create a database.
Why the version matters
Version isn't a cosmetic choice — it decides what your app can rely on once it's talking to the cluster.
- Compatibility with an existing app — if you're moving an app, an ORM, or a data dump that was built and tested against a particular engine version, picking that same version avoids surprises from behavioral or default changes introduced in later releases.
- Feature availability — newer versions of an engine typically add capabilities, performance improvements, or query features that older versions simply don't have. If your app or your team is planning to use something version-specific, confirm the version you pick actually includes it before you build against it.
- Staying on a supported version — the dropdown only ever lists versions the platform currently supports, so choosing from it keeps you on a version that continues to receive engine patches through your NevTan subscription.
Migrating an existing app
When you're bringing an app to NevTan that already runs against a specific engine version elsewhere, match that version first. It's the safest default — you can always move to a newer version deliberately later, once you've confirmed your app is compatible with it.
Note
Version is fixed at creation time for a cluster. If you later need a different version, create a new database on that version and migrate your data across, rather than expecting an existing cluster to change engine version in place.
Tip
The set of supported versions is managed by the platform and changes over time — the version dropdown always reflects what's currently available, so there's nothing to keep track of yourself.
What each engine runs
| Engine | Version |
|---|---|
| PostgreSQL | 18, 17, 16, 15, or 14 — whichever you pick is exactly what's installed. |
| MongoDB | 8.0 or 7.0 — whichever you pick is exactly what's installed. |
| MySQL | 8.0 |
| Redis | 7 |
Important
MySQL and Redis clusters currently provision on a fixed engine version (MySQL 8.0, Redis 7) rather than the specific version chosen at creation — if your app depends on a MySQL or Redis feature from a specific later version, confirm it's available on these versions before relying on it.
Configuration NevTan does not expose
To keep every cluster predictable and easy to reason about, a few engine-level settings are fixed platform-wide rather than left as options on the Create Database form:
- No custom PostgreSQL extensions — clusters run with the engine's default extension set.
- No configurable Redis persistence mode or eviction policy — memory is capped per package with
allkeys-lrueviction. - No MongoDB replica-set option — every cluster is a single node.