Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Kumu Self-Hosted Enterprise Overview

Jeff Mohr
May 17, 2019

Kumu Self-Hosted Enterprise Overview

Jeff Mohr

May 17, 2019
Tweet

More Decks by Jeff Mohr

Other Decks in Business

Transcript

  1. Kumu Enterprise (Self-Hosted) Kumu Enterprise allows you to harness all

    the power and functionality of Kumu’s cloud platform within the safety and security of your own servers. All you need is a compatible virtual machine environment. • Be up and running in minutes by simply downloading our virtual image and loading it to your virtual machine • Access Kumu Enterprise via any modern browser from within your private network • Have peace of mind knowing that we have zero access to your Enterprise installation (and any related data) and you maintain control of your firewall OVERVIEW
  2. Requirements Kumu Enterprise is delivered as a virtual machine image

    that includes all software required to get up and running. You'll also need a compatible virtual machine environment (VMWare or VirtualBox), and we suggest the following hardware minimums: • Processor: Two 2.0 GHz cores (or equivalent) • Memory: 10GB • Disk: 100 GB root partition • Storage: SAN or locally attached Any virtual environment which supports OVF images (the industry standard Open Virtualization Format) will do fine. We officially support VMWare and VirtualBox environments. OVERVIEW
  3. Security Kumu Enterprise is designed to run behind the host's

    own firewall. Kumu has no access to the server unless specifically granted access by the host. Data is stored locally on the machine and backups are the responsibility of host. Internally the machine includes it's own firewall, only exposing the required ports necessary for operation (80/443 for the app and 22 for ssh). Internal services (such as the database services) only listen for connections on the local loopback address. Patching of the core operating system and running services is managed by Kumu. This includes patches for functionality, stability, and non-critical security updates. These updates will typically be released once per month and delivered via a downloadable link. Critical security patches will be released immediately as they become available, outside of the standard product release cycle. OVERVIEW