One name, two things.
The CMS lives perfectly well without the agency — people use it on their own. But a single window without a portable CMS could not promise a replacement specialist: the project would stay with whoever started it.
On the left — who you deal with. On the right — what your website runs on.
The contract, the price and the responsibility.
What makes the website portable.
Reliability here is not a promise to be careful — it is how the work is arranged, and every point can be checked.
The project is portable: content schema, components and build rules travel with the site, so the next specialist opens it and continues instead of starting over.
The public version works as a standalone site and does not need our runtime. Moving it to your own infrastructure is possible at any time.
The agent works inside the CMS in reviewable change batches, and a change is separate from publication: first a preview and a check, then the public site.
Your employee edits texts and photos in the fields their role allows. A saved draft does not touch the public version.
Before handover the brand accepts the site. That is the difference between “built it and vanished” and “we answer for the result”.
On the left — how a website lives with a classic CMS, a builder or a private contractor. On the right — what changes here.
In an admin panel on a server or inside someone else's service, with its limits and its subscription.
The public version is built as a standalone site; it does not need our runtime.
Depends on the server, the template and the set of extensions.
Pages are built in advance; there is no server-side CMS in the public version.
SEO is bolted on with an extension after launch.
Markup, metadata, a sitemap, structured data and a file for AI services are part of the build.
The editor easily touches the structure and the layout.
Only the fields the role allows are editable; the structure of the site is out of reach.
Generates a whole page and edits files at random.
The agent works inside the CMS in reviewable change batches; publication is a separate step.
Sources on someone's laptop, or the project locked inside a service.
The project is portable: another specialist opens it and carries on.
Whoever took the job. Once they vanish, the matter is closed.
The brand: acceptance before handover and a replacement at our cost.
The technical details, for those who want to know what they are paying for. The full description lives on the product's own website.
Code, content, images and the build can stay local. A team connects its own or a hosted server.
Variables, objects and lists describe the content explicitly and travel with the site.
Roles decide which fields and components are available. Saving a draft does not change the public version.
The product is not tied to a single model: agents connect as external applications through strictly typed tools.
An agent's work arrives as a batch of changes you can see and reject, not as files edited at random.
The public version is built without a mandatory server-side CMS — hence the speed and the smaller attack surface.
Semantic markup, metadata, a sitemap, JSON-LD and llms.txt are produced together with the pages.
Compressed responsive variants and a CDN in the cloud, or local processing; publishing over FTP, Git, your own server or the cloud.
The public version does not need our runtime and keeps working without support.
Access for your employee from day one, not “ask the developer”.
The content schema, the rules for files and the project kit are part of the site, not our inside knowledge.
Handed over after two years of work with us: your own team can carry the site on.
2PIX CMS is a separate product with its own website
If you want to dig into the system itself, the technical part lives there in full: how the creation environment is arranged, what the editor actually sees and how a project moves between teams.
We will match a specialist, name the deadline and build the site at a fixed price.