Your CMS. Your infrastructure.
Host the CMS on infrastructure chosen for your project. Keep control of content, theme and team access, and decide who is responsible for operations.
A project you can hand over and develop.
A theme is an independent package of templates, components and settings. Its source can be kept in Git and handed to another developer. Content lives in structured entries and blocks. The work an agent leaves behind stays in the CMS and remains editable by people.
Choose the people who work on it.
Bring together employees, studios, content teams, SEO specialists and agents. Grant each participant the permissions their task requires. The owner manages accounts, tokens, activity history and revocation. Change teams without giving every participant unrestricted control.
Core and design have separate lifecycles.
CMS core updates use the release mechanism. Themes have their own versions and can be checked as candidates on real content before activation.
Operations still require a plan for updates, backups, monitoring and recovery, with a named person responsible. These arrangements depend on your infrastructure and support agreement.
Your CMS on your infrastructure.
Hosting that fits the project.
Describe the expected workload, integrations and access requirements. Agree the hosting arrangement and responsibilities among the owner, technical team and suppliers. If a server or website already exists, begin by assessing that environment; for a new project, infrastructure preparation belongs in the launch plan.
-
About the product
Explore
A CMS for a complete, manageable website.
-
Migration
Explore
Move an existing project with a plan.
Continue exploring
-
Agent workflow
Explore
From tasks to reviewed changes.
Questions and answers
Can I host the website on my infrastructure?
Yes. Progressive CMS can run on the server selected for your project, with content, theme and management in that environment.
Is an agent needed for every page view?
No. An agent creates or changes the site; visitors use the published website. Content can also be maintained manually.
Who applies updates?
Progressive OS publishes releases. The owner or responsible operator applies them through the CMS update mechanism.