Your project's site on your own domain — no server needed

The site is an extension of your DynapiCMS project. Content is described in content types; pages are assembled from routes, templates, and flows; publishing is a button.

1. Describe the content. Articles, products, services — content types with the fields you actually need. Every record is available over GraphQL right away — your site's pages read it, and so does anything else.

2. Assemble the pages. Each route gets a Liquid template and queries against your content. Forms, emails, redirects, members-only sections — flows. Ready-made presets cover the standard parts: a page, a login, a form with a captcha.

3. Publish. The site opens at name.dynapi.ru or on your own domain — the HTTPS certificate is issued automatically. A content edit shows up on the site within seconds.

Subdomain and your own domain. An address like name.dynapi.ru works out of the box; a custom domain connects through a DNS record and a check in settings. Once the primary address is set, the subdomain and www send visitors to it with a 301 redirect — search engines see one address.

Flows. Forms with a submission journal, email from your own domain, webhooks, redirects, cookies. Visitors can create accounts on the site — members-only sections build on ready-made login presets.

Templates and static files. Liquid pages, shared layouts, styles, scripts, images. Your markup isn't boxed into a builder's grid — any layout goes.

Content queries. The project's GraphQL query library: every page fetches exactly the data it needs.

Drafts and publishing. Site changes are prepared as drafts with a preview — drafts stay invisible to search engines. Publishing is a separate button; sitemap.xml and robots.txt update themselves, and missing pages serve your own 404.

The site starts on a subdomain like name.dynapi.ru — nothing to configure. For your own address: add an A record (for a domain like client.ru) or a CNAME (for www.client.ru) with your DNS provider, enter the domain in the site settings, and wait for the check. The platform issues and renews the HTTPS certificate itself — no extra server required. Any connected address can be set as primary; the rest redirect visitors to it with a 301.

Yourself: routes, templates, and flows are screens in your project's Site section; content is edited in records, no markup touched.

A contractor or studio: each client gets a separate project with its own domain. No data migration precedes the handover — the data is already in the client's base.

An AI agent: the platform ships a ready-made skill for agents — describe the task, and the routes, templates, and flows get assembled from it.