Apache Sling > Sling CMS > Administration > Deployment Models
Apache Sling CMS provides a number of deployment models for your solution needs.
The project creates a numer of existing models for different instance types.
An instance that is not part of a cluster of instances. In a standalone instance, the instance handled both authoring and rendering web content. Publishing content in a standalone instance is done by updating the sling:published property.
Standalone instances are published with the following feature:
org.apache.sling:org.apache.sling.cms.feature:slingosgifeature:slingcms-standalone:[VERSION]
An author instance is used to author the content of the site. It is not responsible for rendering the content. Content is published from the author instance to the rendering instance using Sling Content Distribution.
Author instances are published with the following feature:
org.apache.sling:org.apache.sling.cms.feature:slingosgifeature:slingcms-author:[VERSION]
A renderer instance is used to render the content of the site. It is not responsible for rendering the content. Content should not be authored in the renderer and instead should be published from the author instance to the rendering instance using Sling Content Distribution.
Renderer instances are published with the following feature:
org.apache.sling:org.apache.sling.cms.feature:slingosgifeature:slingcms-renderer:[VERSION]
There are a number of samples to help you understand how to deploy Sling CMS:
The vagrant directory contains a project to start Sling CMS in standalone mode in two CentOS 7 VMs one to run the CMS instance and one to run Apache Web Server.
The docker directory contains a project to start Sling CMS with an author-renderer pair with a separate container running Apache Web Server.
The klcodanr/com.danklco.sample.infra project contains a project to build a standalone composite node store Sling CMS instance.