Docs/Deployment

Operating System Compatibility by Deployment Type

DBConvert Streams now ships through two main distribution paths:

  • desktop apps for local installation
  • Docker-based deployment for local and self-hosted environments

This page describes compatibility by deployment model instead of treating all operating systems as one installation path.

Desktop app compatibility

Desktop apps are available for:

Use the current install surface for desktop downloads and package variants:

Docker deployment compatibility

Docker remains the recommended self-hosted deployment model for server and team environments.

Verified Linux host environments

DBConvert Streams Docker deployments have been validated on these Linux hosts:

  • Ubuntu 20.04 LTS
  • Ubuntu 22.04 LTS
  • Debian 10
  • Debian 11
  • Debian 12
  • CentOS 7
  • CentOS 8
  • CentOS Stream 8
  • CentOS Stream 9
  • Fedora 33+
  • RHEL 8
  • RHEL 9
  • Amazon Linux 2
  • Amazon Linux 2023

Windows and macOS with Docker

Windows and macOS can also run local Docker-based setups, typically through Docker Desktop.

Use these pages when you want the Docker route instead of the desktop app:

System requirements

Desktop apps

General minimum expectations:

  • 2 CPU cores
  • 2 GB RAM minimum
  • 1 GB free disk space

Docker deployments

For Docker-based environments, use at least:

  • Docker Engine 24.0 or newer
  • Docker Compose v2.20 or newer
  • 2 CPU cores minimum
  • 2 GB RAM minimum
  • 2 GB free disk space

Production-oriented self-hosted environments should plan for more memory and CPU headroom than local evaluation installs.

Cloud hosting

DBConvert Streams can also be deployed on cloud infrastructure that supports Docker-based hosting, including AWS, Google Cloud, Azure, DigitalOcean, Hetzner, Vultr, and similar VPS or VM platforms.

Use the deployment guides under /deployment/* for the provider-specific Docker path.

Reporting compatibility issues

If you hit an OS-specific issue, include:

  1. operating system and version
  2. whether the issue is in the desktop app or Docker deployment
  3. Docker version and Compose version if applicable
  4. a concise reproduction path
  5. logs or screenshots where relevant