Small production environment

A small production environment consists of a single server with template projects and no custom implementations. For example, sites with 20 pages or so each, constructed from a template that is mostly in “preview mode”.


  • 2 CPUs minimum
  • 40 GB HDD (GUI) and 30 GB (Core)
  • Windows Server
  • SQL 2012 Express
Additional considerations

Disable the following:

  • Desktop experience (required by Sitefinity CMS in order to generate video thumbnails.).
    If Sitefinity CMS is not be used for video libraries, we recommend using a Windows Server Core system where the overhead from the server GUI is nonexistent
  • Windows updates
    For a smaller website, the average consumption of IIS CPU is about 50-85%, and 500-800 RAM usage. SQL may be limited up to 1GB RAM usage.
    Since such a setup is reasonable generally for small businesses, appropriate hosting plans for this setup can start from a shared hosted solution to a dedicated VPs with 2-3 GB RAM ( approximately 1GB RAM for the operating system and the remaining RAM is used by Sitefinity). Thus, for the smooth operation of the system, you need between 500MB to 1GB of memory for the application pool under which Sitefinity CMS runs.

Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.

Get started with Integration Hub | Sitefinity Cloud | Sitefinity SaaS

This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.

Web Security for Sitefinity Administrators

This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.

Foundations of Sitefinity ASP.NET Core Development

The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.

Was this article helpful?