Layout structure
Sections, rows, containers, nesting, and spacing logic survive through the universal layer before target generation begins.
Builder portability infrastructure
Move websites between builders without rebuilding them.
Universal By Foundation translates Elementor, Divi, and code-based layouts into structured builder output with route-aware preservation, validation, and export-ready JSON.
Why this exists
Most sites are trapped inside the builder they were born in.
Redesign means rebuild. Client migration means rebuild. Agency handover means rebuild. Universal By Foundation breaks that loop by translating layout structure into a neutral intermediate format before generating the destination output.
That is the category proposition: site portability for builder ecosystems, not just file conversion.
What transfers
Structure first. Content next. Fallbacks visible.
Core content
Headings, text, images, buttons, pricing, tabs, accordions, sliders, forms, menus, and loop-aware structures are carried with route-specific handling.
Unsupported content handling
Unsupported elements are preserved, flagged, or downgraded safely. Nothing is silently discarded just because a widget family is not native to the target.
Not every widget maps 1:1 yet. Unsupported elements are preserved or flagged, never silently discarded.
Supported routes
Trust grows when the status is honest.
Stable and beta routes are labeled clearly so buyers know where the product is strong and where review is still required.
Elementor → Divi
Agency standardisation
Move Elementor layouts into Divi output
Builder-to-builder portability for teams standardising on Divi without rebuilding inherited Elementor sites from zero.
- Stable route
- Validation-aware output
- Fallback-safe behavior
Elementor → Divi 4 Legacy
Stable route
Use Elementor to Divi 4 Legacy conversion
Convert Elementor source content into Divi 4 Legacy output with route-aware validation.
- Stable engine route
- Catalog entry enriched from route truth
- Validation-aware output path
Elementor → Elementor
Re-export and audit
Clean and re-emit Elementor structures through the universal layer
Useful for validation, cleanup, and portability checks before larger migrations.
- Re-export path restored
- Shortcode handling improved
- Useful for route diagnostics
Elementor → HTML / Code
Stable route
Use Elementor to HTML / Code conversion
Convert Elementor source content into HTML / Code output with route-aware validation.
- Stable engine route
- Catalog entry enriched from route truth
- Validation-aware output path
Divi → Elementor
Legacy rescue
Move Divi layouts into Elementor output
Useful for inherited client sites, legacy rescue work, and teams moving into Elementor-based delivery.
- Divi 4 legacy aware
- DSM deterministic coverage started
- Elementor output generation stable
Divi → HTML / Code
Stable route
Use Divi to HTML / Code conversion
Convert Divi source content into HTML / Code output with route-aware validation.
- Stable engine route
- Catalog entry enriched from route truth
- Validation-aware output path
How people access Universal By Foundation
One engine. Multiple entry points.
The engine stays protected on our side. Customers access it through a hosted workspace, connectors, and controlled integrations instead of receiving the conversion brain itself.
Website workspace
The main product experience is a chat-style conversion workspace with route selection, preflight, review warnings, downloads, history, and billing.
WordPress plugin
The Lite plugin should act as a connector, not a local engine. It authenticates the site, exports source data, sends jobs to Universal By Foundation, and receives the result without exposing core conversion logic.
ChatGPT and Claude connectors
The first AI access layer should start with ChatGPT and Claude so users can send jobs into the same engine from the tools they already use.
Later connectors
Figma, Webflow, Framer, Gemini, and future connectors can arrive later once the main routes, entitlement model, and operational security are proven.
Use cases
This is for people who inherit messy reality and still need to deliver.
Agencies
Migrate inherited sites, standardize delivery, and reduce rebuild hours when clients change stack or hand over unstable builds.
Freelancers
Reuse work across client ecosystems and turn migration jobs into faster, higher-margin deliverables.
Designers & developers
Translate polished layouts or raw code into builder-compatible structures without surrendering the whole handoff to one proprietary ecosystem.
Honest by design
Not everything converts 1:1 yet. Nothing is silently lost.
Visibility
Stable and beta routes are labeled clearly. You should never have to guess whether a route is trustworthy enough for production work.
Preservation
Fallback behavior is explicit. If parity ends, the output tells you where and how, instead of quietly pretending everything mapped cleanly.
Pricing
A token-based model with room to grow.
Free
Capped and ad-supported
Enough to prove the idea on selected routes like Elementor to Divi, Divi to Elementor, and early Figma-to-builder experiments, with no plugin or connector access.
Lite
Daily reset access
For individuals who want the full route set with a daily token allowance that resets like a modern AI workspace.
Pro
For developers and designers
Higher token budgets, deeper history, better throughput, and connector access for people using Universal By Foundation as part of real delivery work.
Agency
Team seats and rollout
For studios and agencies managing multiple users, higher-volume conversion work, route planning, and client-facing operational workflows.
Free stays restricted. Lite, Pro, and Agency should include the website workspace plus the WordPress, ChatGPT, and Claude access paths.
Run your first conversion
No call booking. No sales gauntlet. Bring a file, choose a route, and see the output.
The product should sell itself through a real first conversion, not a long qualification flow.