Code without a system
The first result may look finished, but it has no knowledge of components, project rules or permitted changes.
Build a website with AI.
Take the whole thing with you.
Portable CMS for working with AI agents
2PIX brings together a local authoring environment, a secure content editor, managed components and external AI agents. Build as a team, publish anywhere and keep the complete editable source.
Free locally and in your own environment · speed, SEO and LLM readiness built into every build · FTP, Git or cloud · no mandatory 2PIX runtime
The first version is where the site begins,
not where the work ends.
Generating a screen is easy. The hard part is preserving the system, handing content to an editor, continuing safely with agents and avoiding lock-in.
Content inside the layout
Text and media are embedded in the markup. Every edit becomes another developer task.
AI changes too much
The agent works directly on files without knowing what it may change, who must approve it or how to roll it back.
The project stays locked in the service
Export ends the editing workflow — or the site still needs someone else’s runtime to keep working.
A fast website, readable by
search engines and LLM.
Speed, technical SEO and machine readability are part of the build
2PIX publishes an independent website, not a heavy editor shell. The content structure becomes clean markup, metadata and files that load well for people, search engines and AI services.
Public releasestatic site
Search dataSEO + JSON-LD
Access for AIHTML + llms.txt + MCP
Mediacompression + CDN
Performance by default
Less unnecessary runtime work
The static release needs no server-side CMS and never ships the editor with the public page.
- Only the code and files the page needs
- Local resources without mandatory third-party downloads
- Image compression and options for different screens
- Caching on regular hosting or CDN
Technical SEO from the build
Not a set of extensions after launch
Basic search requirements are formed along with the pages and checked before publication.
- Semantic HTML and clear URLs
- Titles, descriptions and canonical links
- Sitemap, robots.txt and social cards
- JSON-LD Structured Data
Content is read by machines too
Ready for LLM, AI Search and Content MCP
The content schema preserves the meaning of objects and relationships, and the content MCP provides search agents with all the permitted site information in an understandable and consistent form.
- Readable HTML without requiring the application to run
- llms.txt and structured data
- Content MCP for reading data, objects and relationships
- Stable sections, URLs and revisions
- Content is not locked inside a visual builder
This is a separate read-only content interface — not the team MCP used for development and not access to project tools.
One CMS for the entire
website lifecycle
A system, not a one-time result
2PIX preserves both the final page and the rules behind it, so people, agents and teams continue working within one controlled system.
Brief
Purpose, audience, content, limitations and outcome criteria.
personProject kit
Design settings, content schema, component registry, roles and publishing rules.
2PIXAgent change package
Codex or Claude proposes a verifiable change instead of editing files without controls.
agentPreview
The result is built as a separate revision with a clear visual diff.
2PIXReview
Comments, discussions and decisions remain linked to the screen and change.
teamRevision
The approved version becomes the new managed source for the project.
2PIXPublication
FTP, Git, your server or the cloud - with the same reproducible build order.
ownerAnalytics
Events are associated with content, components, and revisions, not just the page address.
nextThe developer has full control.
The editor gets only what they need.
Builds the site system
Authoring environment
A local application for developers, designers and agent applications.
- Designs screens, atoms, components and their variations.
- Builds data schemas from variables, objects and lists.
- Connects Codex, Claude and other agents through typed tools.
- Manages build, previews, publishing via FTP or Git, and portability.
- Works locally, with a team server or with a platform.
The complete project, code and rules remain with the team
Works within permitted limits
Content Editor
A separate shell for content editors and site employees.
- Changes texts, media, posts, lists and allowed properties.
- Adds and rearranges only the components assigned to their role.
- Sees colleagues’ changes live without overwriting their work.
- Submits a revision for approval or publication by role.
- Does not gain arbitrary access to the code and structure of the project.
Owner · Administrator · Editor - team roles; Guest - site visitor
Agents work inside the CMS,
not on top of files
Designed for agents, but not dependent on AI
2PIX does not bundle another closed model. It gives your agents project context and safe actions: read the schema, propose a change package, build a preview and check the rules.
AI builds the site.
You move the pixels.
The project is machine-readable
The agent sees not a random folder, but a project package: components, content schemas, design settings, restrictions and history.
Tools have strict types
Creating a screen, changing an object, replacing a file and starting a build are separate operations with separate permissions.
Changes stay separate from publishing
The agent can prepare the result, but the public version is determined by the roles, approval process, and project rules.
Ready for agent applications
Local applications will be able to assign tasks to agents through open and typed 2PIX tools.
Not everything.
Only what is ready to become part of the product.
2PIX separates one-off generation from a reproducible website system: every component has a contract, variants, content areas and usage rules.
Managed Components
Component Registry
A CodyHouse-level catalogue of tested sections, atoms and variants for the Dart and web SDKs, complete with property schemas, design settings and compatibility data.
Content defines interface
Portable content model
Variables, objects and lists work both locally and with external services. 2PIX uses them to build content-editor forms and component contracts.
Cloud or local files
Image processing
Images and file sets can be stored in the cloud with a CDN or near the site using relative paths. Local processing in Rust is responsible for compressing and creating preview images.
The system travels with the website
Project kit
Source files, schemas, design settings, the component registry, revision history and build rules stay together after export.
Content changes without a developer.
Public version only according to the rules.
The editor does not receive a button that immediately changes the public site, but a clear path from editing to an approved build.
EditingDraft in your field
PreviewLive version without publication
ReviewComments and discussion
RevisionApproved Condition
Build and publishBy role or after confirmation
Export means source code,
not a farewell card
Not tied to runtime
The site continues to open in 2PIX after being transferred to another developer. Everything necessary to continue working is stored next to the result - in the site package and source capsule.
Projectsources + project kit
Contentschematics + data
FilesCDN links or site directory
PublicationFTP · Git · cloud
Transferopening from hosting
Runtime2PIX is not required
Locally for one.
In your own environment for a team.
The mode is selected based on process and data requirements, not a tariff trap. The platform provides convenience, but does not become a mandatory point of failure.
Local work
The creation environment, content editor, and build run on the user's machine.
Transfer via FTP
A new team member enters the FTP credentials, retrieves the source capsule and continues working on the site.
Your own team server
The team deploys a synchronization server in its own environment.
Hosted team server
An isolated team server is created on a selected site without independent infrastructure maintenance.
Connecting external services
Cloud storage, analytics and other services are connected at the team's discretion.
For teams that hand websites over
The main value of 2PIX is revealed after the first release - when the project needs to be developed, agreed upon, transferred and supported by the team.
Agencies and studios
They launch projects faster, maintain their own component system, and deliver a secure content editor to the client.
Designers and developers
Work with familiar AI agents, but get a manageable list of differences and a transferable result.
Content and promotion
They change what is allowed, see the preview version and do not wait for the developer for each line.
Multi-site teams
Reuse components and schemas while preserving the individuality of each brand and project.
IT and security
Leave data and collaboration in their own loop or on an isolated team server.
Free on your infrastructure.
Cloud - as needed.
Pay for the convenience of cloud services, not for the right to own a website
Local work and a team server in its own environment are available for free. The subscription includes synchronization, hosted server, cloud data, file storage and CDN.
No commission from published sites. Cloud services can be disabled: the site package and the ability to work locally remain with the owner.
Local
For independent work
0 ₽no deadline
- Content creation environment and editor
- Code, data and files on your device
- Codex, Claude and other external agents
- Build and publish via FTP or Git
- Full editable source
Team in its own environment
For your own infrastructure
0 ₽on your server
- Own team server
- Simultaneous editing and synchronization
- Roles, rights, comments and discussions
- Own data and file storage
- Cloud independence 2PIX
Cloud capabilities
For teams without server maintenance
2 400 ₽per month · 100 GB included
- Hosted team server and synchronization
- 100 GB for cloud data and files
- Backups
- Compression, previews and CDN
- Maintained infrastructure 2PIX
+500 GB2,200 ₽ per month for each additional package
Find cloud options
Content analytics
Integration with Psssst
Psssst associates events, sessions, and conversions with specific content, component, variant, and revision. 2PIX turns into an analytical dashboard: the team sees not only the visit to the page, but also what content or change influenced the result.
Open Psssst- Component, Variant and Content
- Published revision
- Session and visitor journey
- Event and conversion
Communication and sales
Integration with WiHooks
WiHooks adds working scripts to the site: forms, surveys, chatbots and online chat. On the same basis, the site can be turned into an online store with a personal account, while maintaining content management in 2PIX.
Open WiHooks- Forms and surveys
- Chatbots and online chat
- Online store
- Personal account
Check the whole cycle
not a beautiful first screen
2PIX covers the entire workflow: create, edit, approve, publish, transfer and open again.
- Build a screen with an agent
- Edit content in the content editor
- Check out the change package and preview
- Publish via FTP or Git
- Transfer access to new team
- Open source and continue
In brief
This is a portable CMS for working with AI agents. The authoring environment builds the site structure along with external agents, the content editor manages what data is allowed, and the site package keeps the project portable.
2PIX does not tie a product to one model. Codex, Claude, and other agents connect as external agent applications through strongly typed tools and receive project information.
Yes, this is the basic principle of architecture. Code, content, images, files, and build can remain local. A team can connect its own or a hosted team server, and platform services remain optional.
Local work and team mode on your own server are free. The cloud plan costs RUB 2,400 per month and includes 100 GB for data and files. Each additional 500 GB package costs RUB 2,200 per month. When the cloud is turned off, the site and source remain with the owner.
The public version is built as a stand-alone website without the required server CMS. Along with the pages, semantic markup, metadata, sitemap, JSON-LD and llms.txt are generated, and images receive compressed versions for the desired screens.
A working website, an editable source code, content schemas, rules for working with files, a project kit and a source capsule. A new developer will be able to open a project from the code repository or hosting and continue working.
Only if the field or component is allowed by its role and publishing rules are met: automatically for the trusted scope or after verification and confirmation. Simply saving a draft does not change the public site.
In cloud mode - in the selected storage with CDN, preview images and compression rules. When working offline - in the site directory with relative paths; local processing in Rust will perform the compression and create the desired variants.
Describe the task, team composition, content requirements and publication method. We will offer the procedure and composition of the portable site package.
Agents should make a website faster to evolve, not become its dependency
For agencies, teams and independent creators
Let’s discuss a new website or the migration of an existing one — from the project package and managed content to publishing and handing over a working source.