UCloudCMS Getting started

CMS for your own infrastructure

Your websites.
Your data.
Your rules.

Manage content, add modules and grow your websites on your own hosting. Your code, database and media stay with you.

In development · architecture MVP

UCloudCMS installation diagram: websites, core, modules and data on the owner's infrastructure
UYour infrastructure01 / 03
Corporate website
Catalog
Media and articles
SHARED COREUCloudCMSContent · access · configuration
ModulesThemesAPI
CodeDatabaseMediaUnder your control

UCloudCMS technologies

PHP and Twig. Choose MySQL or PostgreSQL for your database.

PHP 8.3Server-side runtime
MySQL 8.0Database
PostgreSQL 17Database
Twig 3Page templates
CachingFile cache or Redis

01 — Features

From site structure
to system updates.

Dedicated tools for content, access and extensions. One administration panel to manage them.

01 / CONTENT

Pages you can
structure your way

A page tree, content types and custom fields. Articles and news with publication controls.

StructureArticlesFields
02 / CATALOG

Products and media
in one system

Prices, stock levels, photos and a file manager. Image processing and thumbnail generation.

CatalogFilesWebP
03 / ACCESS

Each role has
its own permissions

Control access to modules and individual actions. Separate website data and restore deleted items from the trash.

UsersRolesTrash
04 / ANALYTICS

Understand what
your visitors care about

Page views, traffic sources, UTM campaigns and goals. Reports for each website without requiring external analytics.

AnalyticsUTMGoals
05 / SETTINGS

Update your details.
Not your templates.

SEO, email and media in site settings. Phone numbers, business details and shared blocks in configuration. Custom fields in dictionaries.

SettingsConfigurationDictionaries
06 / MAINTENANCE

Keep backups.
Track changes.

Backups, license management and update checks have dedicated tools in the administration panel.

BackupsLicensingUpdates
Multiple websites

One installation.
Separate sites and themes.

Assign themes to individual websites and keep their data separate. Multisite availability and limits depend on your license.

02 — Architecture

Extend your website.
Not the core.

The core, modules and themes are separate packages. Presentation is separate from data, and each package has its own version.

Installation requirements
01

Modules for each task

Add functionality through extension packages with declared dependencies.

02

Themes separate from content

Twig templates receive prepared data through API connectors, without direct SQL access.

03

Verified updates

Ed25519 signatures, package compatibility checks and a backup snapshot before changing versions.

03 — Licensing

Your infrastructure.
A license for the product.

UCloudCMS is distributed under a commercial license. Your website files and data reside on the infrastructure you choose.

Activation

Activate with an issued key and verify the license's digital signature.

Features

Your license defines the edition, features and limits.

Hosting

Hosting and server administration are arranged separately.

Before installation

Prepare the environment
for your project.

The project is in development. Agree on the edition, license terms and required modules before deployment.

What you need

  • PHP 8.3 with the required extensions
  • MySQL 8.0 or PostgreSQL 17
  • Nginx or Apache 2.4, and HTTPS
  • Access to website and background task configuration
Frequently asked questions

Questions and answers

Before you begin.

Is this a cloud service?

This version of UCloudCMS is designed to run on the owner's infrastructure. You choose the server and keep your code, database and media there.

Can I manage multiple websites?

Yes, if your license includes multisite support. The license specifies the number of websites and other limits.

Can I create my own modules and themes?

Extensions and themes are packaged separately. They declare compatibility with the core and connect through defined contracts.

What happens during an update?

The system checks the release signature and compatibility. It takes a snapshot of files and the database before making changes, with rollback to that snapshot if an error occurs.