Table of Contents

Requirements

Platform, runtime, and hosting requirements for DynamicWeb 10

Use this page to identify the baseline requirements for developing, running, and hosting DynamicWeb 10.

If you are looking for step-by-step setup instructions, use the installation guides instead.

Warning

Runtime and framework support

DynamicWeb 10 currently supports both .NET 8 and .NET 10 during the transition period.

Use the SDK or runtime that matches the DynamicWeb release you are installing or upgrading to. For more information, see DynamicWeb 10 moving to .NET 10.

Browser support

The DynamicWeb administration interface supports current versions of modern browsers:

  • Chrome
  • Edge
  • Firefox
  • Safari

Local development requirements

For local development, we recommend:

  • Windows 10 or 11, Linux, or macOS 10.15 or newer
  • A supported .NET SDK installed:
  • An IDE such as Visual Studio 2022 or Visual Studio Code
  • A local SQL Server instance, a SQL Server in Docker, or access to an external SQL Server
  • SQL Server 2019 or newer with compatibility level 150 or higher

The exact setup depends on the installation path you choose:

Self-hosted Windows and IIS requirements

If you host DynamicWeb 10 on Windows and IIS, these are the minimum baseline requirements.

Minimum hardware

  • Quad-core CPU or equivalent
  • 8 GB RAM
  • Fast storage with backup and redundancy in place

For PIM-heavy solutions, we strongly recommend at least 12 to 16 GB RAM and fast SSD or SAN-backed storage.

Minimum software

With this baseline, a solution should be able to handle moderate traffic, but actual capacity depends on implementation details, integrations, indexing load, media processing, caching strategy, and module usage.

For IIS-specific setup details, see Running in IIS.

Docker and container hosting

DynamicWeb 10 can also run in containers, but container hosting has different operational requirements than IIS-based hosting.

When running in Docker:

  • Do not set CPU and memory limits too low
  • Plan persistent storage for the Files folder
  • Plan how the database is hosted and backed up
  • Consider multiple containers and load balancing for production traffic

For production container hosting, orchestration platforms such as Kubernetes or K3s are recommended.

For implementation details, see Running in Docker.

After confirming the requirements, the next pages are usually relevant:

Improve this doc
To top