Native content and preview
Choose WordPress Pages or Posts and work with real block/HTML content, WordPress document loading and a responsive preview. WordPress database content is not the older static generated-HTML snapshot.
Native WordPress generation • theme + content + setup package
WordPress AI Website Builder — generate a complete native WordPress website package.
Omega Web Pro turns one detailed website specification into a native WordPress build with theme architecture, generated site content, setup/import material, responsive media, SEO/schema, WordPress-specific validation, responsive preview and a complete downloadable ZIP. Omega-native AI knowledge assists planning; Omega generates the production website.
New dedicated Omega Hosting WordPress Editor
Edit and manage native WordPress sites in their own protected workspace.
The WordPress editor is dashboard.omegawebpro.com/website-editor-wordpress.php, separate from the Pure HTML website-editor.php. Customers enter through My Account; Omega verifies their purchased WordPress Website ID, hosting entitlement and canonical domain before opening the matching workspace.
WordPress management and plugins
Use the integrated WordPress Manager and the eight WordPress Omega engine dashboards. Browse and manage compatible third-party WordPress plugins; the installed-plugin management area opens one supported plugin dashboard at a time, without leaving the Editor.
Builder to live WordPress site
Review regenerated WordPress theme/content through the platform-specific import, validation and staged deployment workflow, with revision/history and guarded Deploy / Update Live Website controls. Saving a post and publishing a whole WordPress package are different actions.
The floating Omega AI Agent is embedded directly in the WordPress Editor. It can assist with public internet research and linked sources, six-stage Builder planning, WordPress page/post and theme-code explanations, PHP/HTML/CSS/JS debugging, SEO/performance/plugin guidance, error logs, validation issues and reviewable repair candidates. Authorised Editor context and WordPress permissions govern all site-specific assistance; no suggested change is silently saved to the WordPress database or deployed as a theme.
Direct WordPress administration credentials remain separate from Omega account credentials. Supported embedded WordPress management uses the already authenticated, authorised Omega website session and does not require a second manual WordPress dashboard sign-in.
New: lifetime-licensed WordPress editing without Omega Hosting
Private WordPress Website Editor — for WordPress lifetime licence holders without Omega Hosting
A customer who owns a lifetime licence for a WordPress website but does not have active Omega Hosting for that same Website ID uses the dedicated Private WordPress Website Editor. Sign in, select your authorised website in the customer Dashboard, and use its Edit Website action. This is a private project workspace, not a hosted WordPress installation.
- Source-code editing: browse and search the licensed WordPress package files, edit supported text source including theme PHP, CSS and other source, save changes privately, reload files, and use code-buffer undo and redo. Binary media remains in the package.
- Pages & Posts: select, load and edit the package's WordPress pages and posts as private content drafts, without requiring a hosted WordPress database.
- Responsive preview: inspect package markup and theme CSS at Desktop, Tablet and Mobile widths, refresh or expand to full screen, and resolve supported images from the private package. Preview is sandboxed and does not execute WordPress PHP, database queries or plugins.
- Website Builder continuation: return to the Website Builder for authorised regeneration, and load the latest Builder-generated WordPress package into the private editing workflow. Changes to a newly generated package still require review and private saving.
- Validation and recovery: run offline package-source validation, capture and inspect complete private package checkpoints, review version history, and download the latest edited WordPress ZIP.
- Five private Omega diagnostic dashboards: Image, Performance, Security, SEO and Web Metrics; each has independent per-website enable/disable state, an individual selectable dashboard, package reports and downloadable JSON findings. Image inventory/preview and explicit security malware scanning are available where supported. These are private-package diagnostics, not the five original live hosted WordPress plugin services or live visitor analytics.
Three distinct editing paths: website-editor.php is the Pure HTML Editor; website-editor-wordpress.php is for an authorised WordPress website with eligible active, provisioned Omega Hosting (including lifetime-licensed customers who also have that hosting); website-editor-wordpress-private.php is for lifetime-licensed WordPress customers without active Omega Hosting for that website. The Dashboard determines the correct editor from the website's platform and entitlements.
Hosting boundary: a lifetime licence allows the private WordPress project to be edited and its ZIP exported without buying Omega Hosting. It does not include live hosting, public deployment, live WordPress administration, live plugin execution, visitor-traffic metrics or server-side WordPress PHP rendering. Publishing to Omega Hosting requires a separate, eligible hosting entitlement for that same website.
Open your customer Dashboard to select the licensed website. The authorised private workspace is Private WordPress Website Editor (website selection and sign-in required).
What WordPress generation means in Omega Web Pro
A dedicated WordPress production system, not renamed HTML files.
WordPress is one of Omega Web Pro's two first-class production targets. It receives the same validated business specification, page architecture, design system, planning intelligence, image pipeline and quality responsibilities as Pure HTML, then branches into a WordPress-native renderer and validator.
Dedicated WordPress renderer
The WordPress path has its own renderer responsible for theme architecture, generated content, setup/import material, WordPress-specific behaviour and packaging.
Dedicated WordPress validator
The package is checked against WordPress-specific requirements rather than relying only on the generic site-quality checks used by the shared pipeline.
Complete platform package
The finished deliverable contains the WordPress theme, generated site content, setup resources, reports and installation material required by the selected build.
One specification, one selected renderer
Pure HTML and WordPress share the same Omega brain, but they do not produce mixed output.
The Universal Website Studio records one production target for each build. The shared specification is normalized and validated first; only then does Omega route the finished plan to the selected renderer.
Pure HTML path
Produces portable HTML, CSS, vanilla JavaScript, responsive media and deployment-support files with no CMS dependency.
WordPress path
Produces native WordPress theme, content and setup/import material with WordPress-aware validation and platform-specific behaviours.
Website scope
From a focused WordPress site to a large multi-page architecture.
The page count follows the website specification you create in the Builder rather than a fixed five-page template. The current production system supports up to 120 generated pages in one build.
Industry presets
Choose from 73 current industry starting points or define a custom industry and sub-industry.
111 selectable page types
The current catalogue contains 111 selectable page types across business, commercial, trust, ecommerce, content, education, hospitality, locations, careers, support, legal, campaign and utility requirements.
Repeatable page systems
Services, locations, products, case studies, team members and articles can expand from structured lists into their own generated pages.
Up to 120 generated pages
The current production build enforces a maximum of 120 generated pages in one WordPress website project.
Specification-first WordPress generation
You define the website before Omega creates the WordPress package.
WordPress generation starts from the same structured requirements as Pure HTML, including business facts, architecture, design direction, media and detailed project instructions.
Business + market requirements
Define industries, audiences, countries, regions, service areas, business model, project goals and regional writing requirements.
Page + content architecture
Select built-in pages, repeatable page families and custom architecture, then add detailed professional content requirements.
Design-system controls
Configure themes, colours, typography, spacing, widths, navigation, mobile menus, heroes, cards, imagery, galleries, buttons, CTA emphasis and motion.
WordPress-specific controls
Platform controls appear when WordPress is selected.
Omega keeps WordPress-only decisions out of Pure HTML builds while exposing the controls needed for a genuinely native WordPress package.
Theme architecture
Choose Omega-recommended block architecture, a modern block/Site Editor direction or a classic PHP theme direction according to the project.
Site Editor + reusable patterns
WordPress editing features can be included according to the customer's preferred editing model.
Posts + taxonomy
Posts, categories and tags can be selected as part of the WordPress content architecture.
Search, comments + custom post types
Native WordPress search, comments and suitable custom post types can be incorporated when enabled in the Builder.
AI-assisted planning without AI-written WordPress production code
Omega-native AI knowledge helps plan the site. Omega writes the WordPress package.
Omega Web Pro deliberately separates Omega-native AI planning from WordPress production. Omega-native AI knowledge helps with structured strategy but is not responsible for writing the finished theme, PHP, templates or deployment files.
Structured Omega-native AI knowledge planning
Omega-native AI knowledge can assist with positioning, design direction, layout strategy, CTAs, content emphasis, image allocation and search intent.
Validated planning data
The AI response must match Omega's expected planning schema before it can influence the production build.
Omega Native Planner
Omega-native AI knowledge and deterministic local planning operate inside the same controlled WordPress generation workflow.
Professional project input
The WordPress build can start from far more than a short prompt.
Omega combines structured controls with detailed free-form requirements and source material.
Advanced website brief
Provide up to 50,000 characters of website requirements, business rules, exclusions and technical direction.
Image guidance
Extensive image-placement and treatment instructions can accompany the uploaded project media.
Voice + layout instructions
Separate writing-voice and layout guidance can refine the generated content and presentation.
Supporting source material
Supported TXT, MD, HTML, HTM, XML and ZIP material can provide additional project context.
Modern WordPress theme architecture
Generate a WordPress package built around native theme files.
The exact tree depends on the selected WordPress architecture, but the dedicated renderer can produce the files needed for modern WordPress theme operation and editing.
style.css
The generated theme contains the WordPress theme stylesheet and identifying theme metadata appropriate to the package.
functions.php
Theme functions and WordPress-specific hooks are produced as part of the native architecture.
theme.json
Modern block-theme builds can include WordPress theme.json configuration for the theme design system and editor behaviour.
Templates + parts
WordPress templates and reusable theme parts can be generated for front-page, page, search, header, footer and related architecture.
Classic WordPress when required
Modern block output is not the only available architecture.
Projects that require conventional WordPress PHP architecture can select the classic theme direction instead of being forced into one editing model.
Classic PHP templates
Generate conventional WordPress PHP theme structures where the selected project architecture calls for them.
Same shared specification
The classic path still receives the same authoritative business, design, page and content requirements as the other Omega production targets.
Platform-specific validation
The resulting package still passes through Omega's WordPress-aware validation rather than bypassing the quality pipeline.
Generated WordPress content
Omega produces more than an empty theme shell.
The WordPress export includes generated site-content material so the website architecture can be established inside WordPress instead of recreating every generated page manually.
Generated page content
Omega packages the content associated with the generated website pages for use by the setup/import workflow.
Create or update pages
The generated setup mechanism can create missing pages or update matching generated page slugs when the content package is applied.
Static homepage setup
The generated homepage can be assigned as the WordPress static front page during the setup workflow.
Import-support material
The package can include WordPress-compatible content/import resources alongside Omega's generated site-content data.
WordPress setup architecture
The export includes installation and setup material, not just the theme.
The generated WordPress package has its own uniquely named theme, setup resources, content files, reports and installation instructions.
Theme package
A uniquely named WordPress theme package contains the selected architecture, generated design system and optimized assets.
Setup/import package
WordPress-specific setup resources configure the generated website content without exposing Omega's private server configuration or AI credentials.
Installation documentation
The package can include explicit installation guidance and build reports so the generated deliverable is easier to understand and deploy.
WordPress-native forms
The WordPress renderer replaces Pure HTML form endpoints with WordPress mechanisms.
The dedicated renderer does not simply carry the static-site contact endpoint into WordPress. Platform-specific form handling is converted to native WordPress behaviour.
admin_post integration
Generated form handling can use WordPress admin_post and admin_post_nopriv actions.
Nonce verification
WordPress-native request verification can use wp_verify_nonce as part of the generated form flow.
wp_mail delivery
WordPress form delivery can use the native wp_mail mechanism rather than the Pure HTML endpoint.
No leftover Pure HTML endpoint
The WordPress validator checks that inappropriate Pure HTML contact endpoint references are not left behind in the package.
Responsive image production
WordPress receives the same hardened image pipeline with platform-aware integration.
Uploaded media is processed through Omega's responsive image system before being packaged with the WordPress build.
Logo + supporting images
Projects can include a logo and up to 60 supporting website images for processing and allocation.
Responsive production formats
Production image families can include AVIF, WebP, JPEG and PNG derivatives with responsive source-set delivery.
No unnecessary upscaling
Omega constrains derivative dimensions rather than producing needlessly enlarged files beyond the useful source size.
Favicon + icon families
Logo processing can produce browser favicons, PNG favicon sizes, Apple/Android assets and genuine multi-resolution ICO packages.
SEO + structured data
The WordPress build carries the search architecture into the native package.
Omega's shared SEO responsibilities are resolved before the renderer branch, then translated into the WordPress output appropriate to the generated project.
Page metadata
Titles, descriptions and page-purpose information are generated around the resolved website architecture.
Canonical + social metadata
Canonical and social-sharing metadata are coordinated with the generated site structure.
JSON-LD schema
Structured-data output is generated from the website and page context rather than left entirely to post-build configuration.
Search-support architecture
Sitemap, crawl-support and related SEO responsibilities remain part of the shared Omega generation pipeline.
Checkpointed WordPress production
Large WordPress projects progress through controlled build stages.
Omega does not ask one AI request or one PHP request to create the entire WordPress site, process all media and package everything at once.
Plan
The normalized specification and structured strategy are resolved before production.
Initialize + media
The temporary workspace, shared site plan and responsive media families are prepared.
Generate pages progressively
Page generation advances in small checkpoint batches rather than forcing a large site through one long request.
Package WordPress
After shared generation, Omega runs the WordPress renderer, validator and packaging stages before publishing the preview.
Dedicated WordPress validation
The WordPress package is checked as a WordPress package.
Omega validates both shared website quality and platform-specific WordPress requirements before the generated build is considered ready for preview/export.
Required theme structure
Omega checks required directories and files, including valid theme data appropriate to the selected architecture.
Generated page consistency
Expected and actual generated page counts, slugs and generated content material are checked for consistency.
Link + placeholder conversion
The validator looks for unresolved Omega placeholders and inappropriate leftover .html references that should have been converted for WordPress.
WordPress-native integration
Setup tooling, contact-form conversion, native search when selected, content/import resources and build-report requirements are checked before export.
Shared build-time quality gates
SEO, accessibility, performance and security remain part of the WordPress workflow.
In addition to the dedicated WordPress validator, the generated website is assessed against Omega's broader build-time readiness checks.
SEO readiness
Page structure, metadata, H1 use, structured data, canonical information and crawl-support responsibilities are checked.
Accessibility readiness
Structural fundamentals such as landmarks, image alternatives, skip links and accessible names are assessed as part of the build-time audit.
Performance readiness
Omega checks generated asset patterns, image dimensions, responsive derivatives and other structural performance considerations.
Security readiness
The generated output is checked for unsafe URL patterns, inappropriate remote resources and expected hardening/integration requirements.
Responsive preview before download
Review the generated WordPress website before export.
Omega publishes the generated project through an isolated preview layer so the final package can be inspected before deployment.
Desktop preview
Inspect the generated design and content at a desktop-style viewport.
Tablet preview
Review the responsive layout at an intermediate width.
Mobile preview
Check how navigation, typography, cards, content and media adapt to narrow screens.
Isolated temporary delivery
The preview uses project-specific access data and restrictions rather than directly exposing the private build workspace.
Preview health gate
The final ZIP is enabled after the preview proves its core assets are healthy.
Omega does not assume that generation alone means the website is ready. The preview reports whether the generated core assets actually load.
Styles loaded
The generated stylesheet must be available to the rendered preview.
JavaScript loaded
The generated JavaScript asset must load successfully in the preview environment.
Images loaded
The preview confirms generated image delivery before the website download is exposed.
What the WordPress package can contain
A complete WordPress deployment package, not just a theme ZIP.
The exact tree depends on the selected architecture and features, but the generated package can include theme, content, setup and reporting material.
Generated theme
A uniquely named theme under the WordPress package containing the selected architecture, CSS, JavaScript, templates, parts and optimized assets.
Generated content
Omega site-content JSON and WordPress-compatible import material for establishing the generated website pages and content.
Setup / installer resources
A dedicated setup package or plugin can create/update generated pages and apply important site configuration inside WordPress.
Reports + instructions
Installation documentation and WordPress-specific build reports help describe what was generated and how the package should be deployed.
Best suited to
When WordPress is the right Omega production target.
Choose WordPress when the finished site benefits from native CMS editing and WordPress-specific content management after generation.
Editorial websites
Sites that need ongoing page/post editing, categories, tags and regular content publishing from the WordPress dashboard.
Business websites with staff editing
Projects where non-developer staff need a familiar CMS interface for maintaining content after deployment.
Block/Site Editor projects
Websites that benefit from modern WordPress theme architecture and visual editing through native WordPress tools.
Projects needing WordPress-native features
Sites that need WordPress search, comments, taxonomy, custom post types or other platform-specific capabilities selected in the Builder.
WordPress vs Pure HTML
Choose the production model that matches the website.
Both use the same specification-first Omega architecture, but the final operating model is intentionally different.
Choose WordPress when…
You want native CMS editing, block/Site Editor or classic PHP theme options, content import/setup tooling and WordPress-specific features after deployment.
Choose Pure HTML when…
You want a portable static-first website with no CMS dependency, direct source-file ownership and straightforward hosting.
The complete WordPress workflow
Specify → Plan → Validate → Generate → Package → Audit → Preview → Export.
The downloadable WordPress package is the result of a coordinated end-to-end production workflow.
Specify
Define the business, architecture, design, content, media and WordPress-specific requirements.
Plan
Use Omega-native AI knowledge or Omega Native Planner for constrained structured strategy.
Validate
Check planning data and preserve explicit customer selections as authoritative requirements.
Generate
Run the shared Omega engines and progressively generate the website architecture and content.
Package WordPress
Run the dedicated WordPress renderer for theme, content, setup/import and platform-specific behaviour.
Audit
Run shared quality checks plus the dedicated WordPress validation rules.
Preview + health-check
Inspect desktop, tablet and mobile output and verify that core generated assets load.
Export
Download the complete WordPress website package for installation on compatible WordPress hosting.
WordPress • AI-assisted • Omega-controlled
Define the WordPress website. Let AI assist the strategy. Let Omega engineer the complete package.
Build from a simple idea or a detailed professional specification, select the WordPress architecture you need, review the generated preview and download the complete native package.
Purchase options
Use the same generation platform with either managed hosting or lifetime licensing.
After generation and preview verification, choose US$9.99 monthly, US$99 annual, US$179 for two years, or the US$999 Lifetime Single Website Domain Licence. Recurring plans include managed Omega Web Pro Hosting while active; lifetime production hosting is separate.
After purchase • managed WordPress hosting
From WordPress setup email to the dedicated Omega WordPress Website Editor.
For an eligible, provisioned Omega-hosted WordPress website, the WordPress owner setup email identifies the website, provides its assigned WordPress username, WordPress administrator address, a password setup/recovery route and a link to Omega Website Editor. The Omega account and WordPress login are separate. You can set up direct WordPress login from the email, while Omega’s verified site session handles supported in-Editor WordPress management without requiring another WordPress login form.
Omega-managed WordPress is automatically prepared after eligible paid hosting is provisioned. The hosting lifecycle checks the customer’s authorised WordPress Website ID, prepares the separate WordPress database and core installation where required, configures the administrator and preserves an existing working installation. Its owner onboarding then provides the site-specific setup details by email. Website creation and hosting allocation come first; DNS/SSL readiness and confirmed deployment of the generated WordPress theme and content are separate steps.
Select your purchased WordPress website
Sign in through My Account and open Website Editor. In Your Purchased Websites, choose the correct paid hosting website; Omega verifies its Website ID, entitlement, platform and canonical domain before displaying the site-specific tools.
Edit real Pages and Posts
The native WordPress Source Code — Pages & Posts editor loads actual WordPress HTML and block markup. Select, load and edit a document, then explicitly Save to WordPress to update the live database and preserve WordPress revisions. Preview the saved live page at desktop, tablet or mobile sizes.
Manage and deploy without changing workspaces
Use the embedded WordPress Management controls for supported site administration, or open installed plugin dashboards from the Third-Party Plugins section. The dedicated WordPress Editor provides its relevant validation, revisions and protected native staging/publication workflow when the website and staged source are eligible. The separate Pure HTML Editor does not deploy WordPress themes.
Secure by website: each hosted WordPress site has its own authorised management context. Access to another purchased website requires deliberately selecting that website and passing the same ownership and platform checks.
WordPress help • build to live editing
After generation: follow the dedicated native WordPress editing workflow.
- Generate the native package: Choose WordPress in Builder and review the site specification, pages, imagery, theme, compatibility checks and validated output. The Builder's sixteen generation engines are production-building components, not the hosted plugin catalogue.
- Purchase or select an eligible website: From My Account, choose the specific purchased WordPress site. Omega uses its recorded ownership, Website ID, platform and hosting entitlement to present the correct Editor.
- Complete WordPress owner setup: If provisioned on Omega hosting, follow the site-specific WordPress account email for optional direct WordPress administration. Those credentials are separate from Omega's customer login and should never be provided to a chatbot or support ticket.
- Edit native content: Open the dedicated WordPress Editor, choose Pages or Posts, load the correct document and review its block/HTML content. Explicitly save with the available native WordPress save control and inspect the live WordPress preview.
- Edit a generated theme or package separately: Private package files, a previously generated static preview and live WordPress database content are not interchangeable. Check the specific staging/validation and authorised deployment controls before changing the live theme or publishing newly generated material.
- Maintain the installed site: Use the supported WordPress Manager, applicable Omega hosted plugin dashboards and WordPress.org third-party plugin management. A plugin is installed only when the owner authorises a compatible operation; a directory search alone does not install it.
If Save or Deploy / Update Live Website is disabled or reports a safety error, do not assume publication succeeded. Consult Editor instructions and Troubleshooting.
WordPress after generation • hosted management
Manage WordPress plugins and original administration screens from Omega Website Editor.
On an eligible Omega-hosted WordPress website, the dedicated website-editor-wordpress.php loads the eight WordPress implementations of the Omega hosted Website Plugins. Each can be independently enabled or disabled for that website without changing the other plugin implementations. These operational plugins are separate from the engines that generated the initial WordPress theme and content.
Browse the WordPress plugin repository
Search and browse the complete public WordPress.org plugin repository through live, paginated results—not only the 52 curated WordPress starting choices. After checking compatibility, selectively install or activate official plugins for the authorised WordPress website. Existing plugins, including previously installed privately distributed or premium plugins, appear in the website-specific installed inventory with versions, statuses, supported updates and a one-at-a-time original plugin dashboard where supported. This third-party directory is separate from the eight WordPress Omega Native Website Plugins.
Original publisher plugin dashboards
Open a supported installed plugin’s real WordPress administrative pages within the Third-Party Plugins section of Website Editor. WooCommerce and other WordPress plugin interfaces can render in the protected single-plugin workspace, with no separate customer WordPress dashboard login required for the supported workflow.
Preserved WordPress and Omega controls
Website-scoped WordPress capabilities and plugin requirements continue to apply. Switching plugins replaces the visible dashboard; the Code Editor, responsive preview, native Omega engines and authenticated publishing controls remain in their existing places.
WordPress help • AI and extensions
Omega AI, hosted Website Plugins and third-party WordPress.org plugins have different jobs.
Embedded Omega AI Agent
The dedicated WordPress Editor includes the floating Omega AI Agent for code explanations, Builder planning, validation-error interpretation, proposed fixes, plugin help and supported public web research. AI suggestions are reviewable proposals. Changes to the WordPress site remain subject to the Editor's actual save, stage, validation and authorisation controls.
Eight hosted WordPress plugin implementations
On eligible Omega-hosted WordPress websites, the applicable Omega Plugin dashboards are Image, Performance, Security, SEO, Web Metrics, Uptime & Availability, Accessibility Monitor and Scheduled Task Monitor. They are the WordPress half of the sixteen hosted plugin implementations, not the Builder's sixteen generation engines. Per-website Enable/Disable status is independent.
Full searchable repository, plus installed dashboards
Browse and search the full public WordPress.org plugin directory in paginated results. The curated WordPress selections are only starting suggestions; they are not the entire repository. Review compatibility before an authorised official plugin install or activation. Installed plugins with supported management interfaces provide Open Dashboard, one at a time, inside the protected WordPress Editor.
For details, see Omega hosted plugins and third-party repositories. Pure HTML library search via cdnjs/npm belongs to the separate Pure HTML Editor and does not install WordPress plugins.
OMEGA WEB PRO HOSTING
WordPress on Omega Web Pro Hosting
An active recurring plan can run the generated WordPress project through Omega Web Pro Hosting with managed project, staging and production controls. Database and backup functions are presented through the custom Hosting Dashboard.
Customer control plane
Lifetime-licensed WordPress output remains portable. The customer can keep the permanent same-domain build/edit/export rights and choose whether to attach Omega Web Pro Hosting.
Managed hosting plans
Monthly US$9.99 · Annual US$99 · Two Years US$179. Managed Omega Web Pro Hosting remains available while the recurring plan is active.
Lifetime software licence
US$999 one time for permanent supported build, edit and export rights for one licensed website domain. Production hosting is separate and can be added when required.
Current production customer architecture
Build, purchase, billing, hosting and editing continue through one authenticated Omega customer relationship.
For a first-time Omega Hosting checkout, Omega saves the selected plan and pending website to one restricted checkout-bound customer account before payment, sends a secure one-time account-setup email, and requires the customer to set a password and sign in before continuing to the required purchase acknowledgements and secure Stripe Checkout. Paid Hosting and Editor entitlement remain locked until Stripe confirms payment. For a first-time Lifetime Licence purchase, an existing account is reused where available, or the customer account is created after Stripe confirms the purchase. My Account is the commercial identity, website, licence and billing centre; recurring hosting customers can use the Full Hosting Dashboard while entitled; lifetime customers retain their separate same-domain software rights.
My Account
Purchased websites, subscription/renewal state, lifetime licences, Pending Checkout, Purchase History, profile/security, Builder and Website Editor entry points.
Billing Centre
Secure Stripe customer-portal access for the account's usable canonical production billing customer, including supported payment-recovery and subscription billing actions.
Omega Hosting Dashboard
Entitled operational hosting controls for project workspaces, provisioning, deployment, backups, databases, SFTP and usage, with customer-facing DNS/SSL state surfaced through Omega interfaces.