Vosetu CMS
منصة إدارة محتوى متعددة المستأجرين — تثبيت واحد ومواقع غير محدودة.
One installation, sites that live under their own names
Vosetu CMS is a multi-tenant content platform that publishes independent websites at the same time behind a single installation. Each site lives under its own domain, its own theme, its own set of languages and its own content; the only thing they share is the engine underneath. A visitor never notices the platform — what they see is a site designed for that brand alone.
On the content side the management surface is Vosetu Studio: you first pick your site, then edit that site's pages, sections, menu and texts. The panel is not installed per site and does not keep separate versions — the same Studio rebuilds itself according to the schema of the site you selected.
- Domain-based tenant resolution: a request is bound to a site by the address it arrives at
- The theme is chosen at runtime — no new installation for a new site
- Content, menu, language and theme are fully separated per site
- This product's own website is a tenant on the very same platform
Vosetu Studio: eight faces of management
A panel should not be a system you must learn before you can enter content. Every screen in Studio serves one question: how do I change that thing on the site?
In-place editing
In the site preview you click on the text and fix it right there; you never hunt for which field lives where.
Page editor
A page's blocks are reordered, hidden and added; each block's settings and the collection feeding it are chosen.
Content tree
A page → section → sub-field hierarchy; content sits in the same order as its placement on the site.
Menu editor
A drag-and-drop menu tree: parents, children, order and links — all from the panel.
Forms & inbox
Every form submission from the site is grouped by form and collects in the panel with read state.
Interface texts
Buttons, labels, empty-state copy: all 445 interface keys can be overridden per site.
SEO assistant
A 0–100 score per page, warnings for missing titles or descriptions, and a one-click meta suggestion.
Visit analytics
Our own measurement: daily visits, most-read pages, sources, language and device breakdown.
What is inside the engine
Multi-tenancy
When a request arrives, the platform first decides which site it belongs to: the address is matched against registered domains, and that site's theme, language and content are loaded. Because the decision happens at runtime, opening a new site needs no new server, no new installation and no new deployment — one record and one domain are enough.
- Domain → site matching (the www variant is normalised)
- Every record carries a site id; queries are filtered by it
- A preview cookie lets you browse a site before it goes live
The content model and addressing
Content lives in a single structure whatever its type: settings, lists, blog posts, services, references, menus, form messages and page compositions are different types of the same model. Every record takes its address from its place on the site — the page, the section on that page, the sub-field of that section. So 'the top heading on the contact page' is found by address, not by searching.
- 13 content types plus page/block composition
- Multilingual fields in one record; an empty language falls back to the main one
- Admin-only fields never leak into the public output
Themes and page composition
Themes are not colour variants of one another; each is designed from scratch with its own skeleton, components and typography. Page composition, meanwhile, comes from content: a page's blocks are ordered, hidden and configured from the panel. If there is no record, the theme renders its own default composition — so a site that never touches the page editor still works perfectly.
- Sector-specific themes that do not resemble each other
- Block order and settings come from content, not from code
- A new theme is a coding job — visual theme editor · soon
SEO, speed and measurement
Each site's sitemap and crawler directives are produced for its own address; two tenants never see each other's map. Page metadata, cross-language alternate links and structured data come from the engine's shared layer rather than being left to the theme. Visit measurement does not go outside: our own counter runs, and it collects no personal data.
- Per-address sitemap and crawler directives
- Alternate-language links and structured data in the engine
- Visit analytics that sends no data to third parties
The capability catalogue
- Domain-based site resolution
- Theme per site
- Language set per site
- Create a new site from the panel
- Start by cloning an existing site
- Preview before going live
- Site status (live / closed)
- 13 content types (settings, lists, blog, services, projects, references, FAQ…)
- Page → section → sub-field addressing
- Rich-text editor (images, tables, links)
- Paste cleanup
- Draft / published state
- Ordering and featuring
- Version history and rollback · soon
- Reorder, hide and add blocks
- Block settings (heading, layout, limit)
- Collection binding (by tag or featured)
- Live preview in a split screen
- Device preview (desktop/tablet/phone)
- Sector-specific ready themes
- Turkish / English / German
- Language per field, empty falls back to the main one
- 445 interface strings overridable per site
- One-click AI translation
- Language-based URL structure (/tr, /en, /de)
- Page title, description and slug
- Per-address sitemap
- Crawler directives (robots)
- Alternate-language links
- Share card images and tags
- Structured data (schema.org)
- SEO score and suggestions per page
- AI-suggested meta description
- Visit analytics that collects no personal data
- Daily chart, top pages, sources
- Language and device breakdown
- Freely defined forms
- Inbox grouped by form
- Email notification on submission · soon
- Publish on your own domain
- SSL certificate and routing setup
- Container-based deployment
- Centralised logging and error tracking
- Fast delivery through page caching
- Media library (file upload) · soon
- Email/password sign-in
- Email verification and password reset
- Per-user list of accessible sites
- Administrator and site-owner distinction
- Granular role/permission management · soon
How it runs: cloud or your own servers
The common use is the cloud side: your site lives in the installation we operate, and all you need to do is point your domain at it. Certificates, backups, upgrades and monitoring stay with us; you deal only with content. For a company with several brands, or an agency publishing sites on behalf of clients, this is where the real gain sits — the fifth site does not cost more to run than the first.
The second option is running the platform on your own servers. When data must not leave the corporate network, or when you operate your own infrastructure, the same engine is installed on your side: the same panel, the same themes, the same content model. There is no feature difference between the two options; the only difference is who operates it.
In both cases the content database is yours and can be exported. If one day you decide to go another way, you are left holding the theme code and structured content — nothing stays locked inside the platform.
- Cloud: point your domain, we handle the rest
- On-premises: the same engine, on your servers
- No feature gap — only who operates it
- Content is exportable; no lock-in
A new site live in five steps
1 · Open the site
Create the site record from the panel; if you like, clone an existing site and start with its content.
2 · Pick the theme
Attach the theme that fits your sector; if you need a bespoke design, we code the theme — the engine stays the same.
3 · Enter the content
Write the copy page by page and section by section, build the menu, fill the languages; translation is one click.
4 · Arrange the page
Order the blocks, hide the ones you will not use, choose what the lists show — all while watching the preview.
5 · Connect the domain
Point the domain at the server and set up the certificate; the site goes live at its own address.
Technology
- .NET 9 Web API
- PostgreSQL
- Dapper + parameterised SQL
- Redis
- Centralised logs (Elasticsearch)
- Next.js 16 + React 19
- Server-side rendering + page caching
- Multilingual routing
- Per-address sitemap/robots
- Structured data layer
- Angular 20 (standalone, zoneless)
- Library-free rich-text editor
- Docker containers + Jenkins
- Reverse proxy + automated SSL
- 102 server-side automated tests
A content management system is good to the degree that it does not discourage the person entering content. Every extra minute spent in the panel is, in truth, the reason a site goes un-updated; so Studio's design goal is not the number of features but the number of clicks it takes to change one line of text.
Frequently asked
What is Vosetu CMS?
Vosetu CMS is a multi-tenant content management platform that publishes multiple websites from a single installation. Each site runs on its own domain, theme and languages; content is edited from a shared panel called Vosetu Studio.
Can I manage several sites from one panel?
Yes. When you sign in you first choose the site; each user reaches only the sites they were given access to. Opening a new site needs no new installation, and you can start by cloning an existing site along with its content.
Can I publish on my own domain with my own design?
Yes. The site is published on your own domain and the theme is designed for that brand — themes are not colour variants of one another. You can start from one of the ready themes or have a bespoke theme built; the engine is the same either way.
Can I build a multilingual site, and who does the translation?
Turkish, English and German are supported, and which languages are enabled is decided per site. You can write the copy yourself or use one-click AI translation and then edit it. When a language is left empty the page falls back to the main one instead of breaking.
What comes ready on the SEO side?
Page titles and descriptions, slugs, share-card tags, alternate-language links, structured data, plus a sitemap and crawler directives generated for each site's own address all come ready. The panel also shows an SEO score per page with warnings for missing fields.
Are there a media library, version history and granular roles?
All three are marked 'soon' in the catalogue: today images are used as theme assets or external links, content history is not kept, and access control is limited to an administrator/site-owner split. Rather than describing them as if they existed, we prefer to say they do not.
See your site on Vosetu CMS
Let us talk about how many sites you have, which languages you publish in and where the design should land; we will choose the deployment model together. You will be talking to the team that wrote the platform, not a sales team.