▤ OMEGA WEB PRO DOCUMENTATION • PRIVATE WEBSITE EDITOR

Edit the Licensed Source Code with Real-Time Preview and Validation.

Omega provides two private editors for authorised purchased Website IDs: a dedicated Pure HTML source editor and a separate native WordPress website editor. It loads authorized project files, provides editor tools, validates current changes, mirrors safe edits into a sandboxed responsive preview, creates versioned saves and can generate an updated signed licensed ZIP after whole-project validation.

Open My Account → Documentation Hub Customer Support

Paid customers onlyLicensed Website IDs onlyDirect source editing2nd live preview14 validation responsibilitiesVersion historyUpdated licensed ZIP

LICENSED CODE EDITOR • LIVE PREVIEW • VALIDATE • VERSION • EXPORT

WEBSITE EDITOR● CURRENT PLATFORM REFERENCE

DocumentationAccessInterfaceLive PreviewLive ValidationSyntax + SafetySave + VersionsDomain ProtectionPHP BoundaryValidate + Export

✓ 14/14 validation responsibilities✓ Canonical host protected✓ Sandboxed preview

Omega Hosting • two dedicated, protected website editors

Separate editing workspaces for Pure HTML and native WordPress websites.

Omega uses the verified website's hosting record, platform and authorised Website ID to select its editor. The Pure HTML and WordPress tools are separate OVHcloud pages, not two modes of the older combined website-editor.php. Sign in through My Account and select your purchased website; do not choose a platform by changing the URL.

Pure HTML Website Editor

dashboard.omegawebpro.com/website-editor.php

Work with the site's authorised HTML, CSS, JavaScript and supporting project files. Use the code editor with Save, Undo, Redo, Find and Replace, a desktop/tablet/mobile sandbox preview, validation, version history, updated licensed ZIP export, Builder-source adoption and guarded Deploy / Update Live Website.

The selected Pure HTML site can also access its eight applicable Omega hosted Website Plugin implementations and compatible third-party HTML add-ons through the editor's website-specific plugin panels. The embedded Omega AI Agent assists with code, validation explanations and reviewable proposed fixes; customers approve and save changes themselves.

Native WordPress Website Editor

dashboard.omegawebpro.com/website-editor-wordpress.php

Work with native WordPress Pages and Posts, their HTML/block content and responsive WordPress preview, plus the integrated WordPress Manager for supported site administration. WordPress engine dashboards, the installed-plugin repository and one-at-a-time plugin administration workspace operate within the authorised editor.

Builder-generated WordPress theme/content changes, validation and live publication follow the WordPress-specific staging and deployment process—not the Pure HTML static-file editor. Saved WordPress database content and a published WordPress theme are distinct operations. The Omega AI Agent is also embedded here for page/code guidance, validation help and controlled, reviewable repair suggestions.

Both editors retain customer/Website ID checks and protected workflows. Each paid Omega Hosting purchase covers one website; only the eight engines appropriate to that website's detected platform apply. Both pages include the floating bottom-right Omega AI Agent for public web research with sources, NativeAI knowledge and planning, six-stage Builder guidance, code explanations, error/log review, website-scoped validation help and staged repair proposals. Customer-specific account, hosting and source assistance require a verified session and authorised Editor context; suggested changes require explicit review, saving and validation before publication, never silent live edits. Lifetime licence editing and licensed ZIP rights are separate from the paid hosting entitlement required to deploy. Hosting, editing, staging and publication remain subject to the selected site's permissions, entitlements and validation checks.

How the two editor workflows differ

HTML: open the selected Pure HTML Website ID, work in the protected code editor, inspect the responsive static sandbox, validate, save/version and deploy or export when authorised. WordPress: open the selected WordPress Website ID, edit native Pages or Posts and preview the WordPress-rendered result, manage supported WordPress settings and plugins, then separately validate and publish staged theme/content revisions where authorised. Neither editor grants access to another customer's website, and a WordPress database save is not a substitute for WordPress package deployment.

Built-in Omega AI assistance: A floating bottom-right Omega AI Agent is available in both the Pure HTML and WordPress Editor pages. It offers research with source links, Omega NativeAI knowledge/project planning, Builder specification guidance, source-code explanations, responsive coding examples, error-log debugging, SEO/accessibility/performance advice, licence/hosting guidance and website-specific validation assistance when authorised. For Editor repair candidates, review the changes, explicitly select Save All AI Fixes and then Validate Licensed Website where applicable. It never bypasses site authorisation or independently publishes proposed changes.

Website plugin dashboards: HTML and WordPress each use only their eight compatible hosted implementations of Image, Performance, Security, SEO, Web Metrics, Uptime & Availability, Accessibility Monitor and Scheduled Task Monitor. Each site's hosted plugin Enable/Disable state is independent. Supported installed third-party plugin dashboards open one at a time beneath the selected website's repository.

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).

Access boundary

Website Editor opens from the purchased customer's licensed website record.

It is not a public arbitrary-upload IDE.

🔐

Authentication

The customer must be signed in to the canonical Omega account associated with the website purchase or checkout.

Website ownership

The selected Website ID must belong to that account and have an active licensed-domain relationship.

FILES

Project scope

Only the authorized licensed project workspace/file set is exposed through the editor.

Customer workflow • two separate editors

Choose the correct editor, make a change, and confirm where it is saved.

Start from My Account and choose the purchased website. Omega checks the account, Website ID, domain, hosting eligibility and detected platform before opening the applicable editor. Do not change a URL parameter to try to open a different site or the wrong editor.

Pure HTML: website-editor.php is the source-file editor for an authorised Pure HTML project. WordPress: website-editor-wordpress.php is the separate WordPress Editor for an authorised native WordPress website. The platform should be selected from trusted website records, not by guessing which page to use.

Pure HTML: review the file, the sandbox and the saved revision

Choose an authorised Pure HTML website and a supported source file from Project Files. Review the current source before typing; unsaved work stays in the editor buffer until you explicitly save it.
Use Save, Undo, Redo, Find Next, and Replace as appropriate. Check the responsive sandbox at desktop, tablet and mobile widths; it is a preview, not the publicly deployed site.
Correct any newly introduced validation or domain-lock errors. Save the authorised changes, run Validate Licensed Website for full-project checks and review Version History when needed.
Use Generate Updated Licensed ZIP for an entitled export. Use Deploy / Update Live Website only after validation and when the selected website has an eligible active hosting deployment target. An export is not an automatic deployment.

WordPress: separate the live database, private source files and theme deployment

Choose an authorised WordPress website. In WordPress Source Code — Pages & Posts, select a Page or Post, use Load or Reload from WordPress, then inspect its WordPress block/HTML source.
Use the available Save to WordPress or equivalent explicitly enabled save operation to commit native Page/Post edits, and check the site's WordPress revisions. A private edited package, an unsaved source buffer and a live WordPress database record are different states.
Use the dedicated Live WordPress Preview for the selected native content at supported screen widths. The Static Snapshot Preview, where shown, represents a separate generated snapshot, not the authoritative WordPress render.
Use WordPress Management for supported site administration and plugin dashboards for compatible plugins. For a newly generated WordPress theme/content package, follow the displayed staging, full validation, and confirmed native deployment controls; if a save or deploy button is disabled, do not treat that operation as complete.

Protect your work: Do not assume Save, Preview, Validate, ZIP Export and Deploy are interchangeable. Check the success message and the actual selected website after each step.

Editor interface

The editor is designed for direct supported-file work, not just visual settings.

The current interface includes project/file selection, full-file editing and common text-editor controls.

☰

Project + file navigation

Choose the purchased website, then choose an authorized file from that project's sidebar.

Line-aware editor

Loaded file content is shown with line/cursor awareness.

↶

Undo + Redo

Reverse or restore local editing actions.

⌕

Find + Replace

Find Next, Replace and Replace All support controlled source editing.

Omega-hosted WordPress • first-time setup

Receive your WordPress setup email, then open the correct purchased website in Omega.

After a paid WordPress hosting website has been provisioned, Omega’s WordPress owner-onboarding email provides the new site's URL, its Omega Website Editor entry point, its WordPress administration URL, the assigned WordPress username and a WordPress password setup or recovery link. The email does not need to contain a password or a private recovery token.

What happens automatically before you edit: for an eligible paid WordPress hosting website, Omega’s background lifecycle prepares and checks the site's own WordPress database, installation and owner account after hosting provisioning. It avoids reinitialising WordPress that is already installed. Once ready for owner onboarding, the site-specific setup email provides the access details described below. DNS/HTTPS activation and deployment of generated WordPress theme/content remain separate from WordPress account initialisation.

Set up the site’s separate WordPress account

Open the WordPress password setup/recovery link for your own hosted domain if you want to establish credentials for direct WordPress administration. Your Omega Web Pro customer-account login and the website’s WordPress administrator credentials are separate; changing one does not change the other.

Sign in through My Account

Use your Omega account at My Account, then open Omega Website Editor. In Your Purchased Websites, select the verified, paid WordPress website you intend to manage, not another website under the same account.

Let Omega verify the Website ID and platform

Omega checks the authenticated customer, hosting entitlement, Website ID, canonical domain and stored platform. It loads that website’s authorised project, native WordPress management controls and matching plugins. The embedded WordPress-management experience uses secured, website-scoped access; the supported Editor workflow does not require a second manual /wp-admin/ sign-in.

Important: the WordPress setup email and the Omega hosting/DNS setup instructions serve different purposes. Each customer receives links and identifiers for their own website; example Website IDs and sample administrator usernames should never be copied to another site.

Website Editor • hosted plugin operations

Choose the website once; Omega loads the matching engine and plugin systems.

The authenticated Website ID governs project files, publishing and plugin access. The Pure HTML Editor keeps HTML source editing, unsaved work, validation and a sandbox preview; the separate WordPress Editor provides native WordPress source, preview, management and platform-specific plugin panels.

Omega Plugins: eight hosted plugin families

The site’s Pure HTML or WordPress hosting record selects the appropriate eight of sixteen implementations. Image, Performance, Security, SEO, Web Metrics, Uptime & Availability, Accessibility Monitor and Scheduled Task Monitor have independent persistent Enable, Disable and status controls for each authorised hosted website.

Third-Party Plugins: platform-specific discovery

For WordPress, browse and search the full public WordPress.org plugin repository with live, paginated results—not just Omega’s 52 curated starting choices. Review compatibility, install selected official plugins only with website-owner authorisation, manage the chosen WordPress website’s installed plugins, and open supported original plugin dashboards one at a time. For Pure HTML, search the public cdnjs browser JavaScript/CSS library directory or the wider npm package registry, with searchable results and pagination, for read-only research and discovery. The fourteen curated Omega HTML add-ons are a separate managed catalogue with Install, Enable, Disable, Status and supported Sync controls; npm/cdnjs search results are not automatically installed or executed.

Independent installation and permissions

Omega’s native hosted plugin entitlement does not automatically install third-party plugins. WordPress plugin installation, activation, deactivation and updates follow that site’s permission and compatibility checks; Pure HTML add-ons have their own installation and enablement states.

Original plugin dashboards • one at a time

Open supported original WordPress plugin dashboards inside Website Editor.

An installed WordPress plugin exposes Open Dashboard in the Third-Party Plugins workspace. Omega uses an authorised, site-bound gateway to present the original plugin administration screen and relay supported interactions, without requiring the customer to open a separate WordPress dashboard login. Selecting another plugin closes or replaces the previous dashboard.

Publisher-created screens

For tested plugins such as WooCommerce, the original WordPress administration interface appears inside the Omega workspace rather than a generic substitute. Available settings and actions are those supported by the plugin and the website’s WordPress administrator capabilities.

A single active workspace

Only the selected installed plugin’s dashboard is displayed at once. Installed inventory, version and status remain scoped to the selected Website ID; protected system plugins are not exposed as ordinary uninstallable add-ons.

Protected source and publishing

Opening a plugin dashboard does not replace the Code Editor, discard unsaved source, alter the responsive sandbox preview or bypass the existing validation and authorised Save/Deploy workflow. Compatibility varies by plugin, including advanced features and external services.

WordPress Management • live website

Edit live WordPress Pages and Posts without leaving Omega Website Editor.

When a verified Omega-hosted WordPress site is opened in website-editor-wordpress.php, its dedicated workspace provides both WordPress Source Code — Pages & Posts and an embedded WordPress Management workspace. These controls operate on the selected site's real WordPress database; Pure HTML source editing is handled by the separate website-editor.php page; static snapshot files are not live WordPress database content.

Load, edit and save native WordPress content

Choose Pages or Posts, select a WordPress document, then use Load, Reload from WordPress or Save to WordPress. The source panel edits WordPress page/post HTML and block markup. An authorised save updates the live WordPress content and retains WordPress revision history; unsaved edits are not automatically published.

◫

Preview native WordPress content in the dedicated editor

Use the native WordPress preview to inspect the selected Page or Post in the dedicated WordPress Editor, including supported responsive desktop, tablet and mobile layouts. Pure HTML file previews belong to the separate HTML Editor. A preview does not replace an explicit WordPress Save or a verified theme deployment.

Manage WordPress and installed plugins in place

The embedded WordPress Manager provides supported operations for Pages, Posts, WordPress settings, comments, classic menus, theme selection and installed-site inventories. The separate Third-Party Plugins area opens supported original installed-plugin dashboards one at a time, alongside the eight website-specific Omega Native Website Plugins.

✓

Validate, review history, export or deploy through protected controls

The relevant platform-specific Validate Licensed Website, Version History, Generate Updated Licensed ZIP and Deploy / Update Live Website controls remain on the same page. WordPress page/post saves and native WordPress theme deployment are different operations: editing the static HTML snapshot does not automatically publish a WordPress theme or database change. Protected deployment requires the matching eligible hosting source and validation.

Actions remain scoped to the authorised Website ID and permanent domain. The Pure HTML Editor and the dedicated WordPress Editor are separate pages, each with appropriate preview, validation, Omega engines and plugin controls; WordPress source and Manager tools belong to the WordPress page.

Second preview workflow

Valid edits can appear in the sandboxed responsive preview beneath the editor.

This is distinct from Builder preview because it is driven by the currently edited licensed project source.

🖥

Desktop

Inspect full-width changes.

▤

Tablet

Inspect intermediate responsive behavior.

▯

Mobile

Inspect narrow-screen behavior.

⛶

Refresh / full screen

Refresh the preview and use larger inspection when needed.

Omega AI Agent • both editors

Use Omega AI assistance without skipping review, validation or an authorised save.

Both editors include the floating Omega AI Agent in the lower-right corner. You can ask it to explain an error, research public technical documentation with cited sources where available, review HTML/CSS/JavaScript or WordPress-related code, propose a change, help with a Builder specification or explain site-specific plugin/hosting controls. Live research and answers remain subject to successful retrieval and verification.

Open the correct authorised website and relevant file or WordPress document first. Describe the exact desired outcome and paste the safe error text—not passwords, access tokens, database credentials or personal data.
Read the proposed change and inspect every affected file or document. Apply to Builder transfers a proposal into the Builder workflow; it is not a production website deployment.
Where the Editor offers Apply to Editor or Save All AI Fixes, the proposal is staged for review. Do not assume chat text or staged changes were saved or published automatically.
Perform the normal authorised Save, full validation and, only when applicable, confirmed deployment. If a validator reports new errors, correct them before publication.

Scope: AI assistance does not replace website ownership, permission, plugin entitlement, WordPress administration or production deployment safeguards. The Builder's 16 website-generation/validation engines are separate from the eight hosted Omega plugin families (16 platform-specific implementations).

14-responsibility gate

Newly introduced blocking issues can stop Preview and Save until corrected.

The live validator maps detected issues to the responsible production area and, where available, the exact line.

Website Specification

Checks project/specification consistency.

Brief Normalizer

Checks normalized project assumptions.

AI Planning

Checks planning-boundary expectations.

Plan Validation

Checks validated plan consistency.

Site Architecture

Checks document/page structural expectations.

Content Conversion

Checks transformed content data.

Design System

Checks styling/design structure.

Image Engine

Checks image-related project output.

SEO + Schema

Checks SEO data, JSON-LD and canonical rules.

Accessibility

Checks structural accessibility expectations.

Forms + Backend

Checks forms/server integration patterns.

Deployment

Checks deployable path/output expectations.

Quality / Metrics

Checks quality/readiness expectations.

Final Validation

Final combined gate before accepted operations.

Blocking examples

The editor checks more than one language family.

Validation can stop newly introduced invalid or unsafe content from moving into preview/save.

HTML

HTML structure

Malformed/invalid document structure can be detected.

CSS

CSS structure

Structural CSS issues are checked.

JavaScript

JavaScript structure is checked.

JSON

JSON + JSON-LD

Malformed JSON data and structured data can be rejected.

XML

Malformed XML can be rejected.

UTF

Data safety

Malformed UTF-8 and NUL-byte data are blocking conditions.

◆

Security patterns

Detected unsafe executable/exfiltration-style patterns can be blocked.

🔒

Canonical host

Attempts to change the protected home-page canonical host to another domain are rejected.

Accepted changes

Save is revalidated server-side and accepted saves create version history.

Client-side live validation improves feedback; server-side checks remain authoritative.

✓

Server-side revalidation

An edit that appears acceptable in the browser still passes authoritative backend checks before persistence.

≋

Version history

Accepted saves create versioned revisions so the customer can inspect or restore prior states according to the editor controls.

Unsafe change rejected

A blocking issue does not become a saved project revision simply because a browser request was submitted.

Permanent licence identity

The root licensed domain is permanent; internal page paths can evolve.

This protects the commercial licence identity without freezing every filename forever.

🔒

Home canonical host locked

The home-page canonical host must remain the permanently licensed normalized domain.

✎

Internal page changes allowed

A customer can legitimately rename an internal page and update its canonical path as long as it remains under the licensed host.

ZIP

Export recheck

Canonical/licence identity is checked again before updated ZIP generation.

Sandbox behavior

Customer-edited PHP is not executed by the Website Editor preview.

The preview is intentionally not an arbitrary server-side code execution environment.

PHP

PHP editing vs execution

A supported project file may be edited where the project workflow permits it, but customer-edited PHP is not executed inside the live preview.

SANDBOX

Sandboxed iframe

Preview script execution is constrained by the preview sandbox rather than receiving unrestricted application privileges.

APP

Omega application protected

Customer editing is scoped to the licensed project and is not permission to edit Omega Web Pro's own application source.

Project-level delivery

Validate the whole licensed website before generating the updated ZIP.

The open file is only one part of the project.

✓

Validate Licensed Website

Run broader project validation after completing edits.

ZIP

Generate Updated Licensed ZIP

Package the current accepted project as a signed licensed export.

↻

Regenerate instead

If the change is easier at specification level, return to Builder and regenerate the same licensed domain instead.

Plugin management • site-specific

Manage Omega hosted plugins and third-party repositories without mixing the two systems.

Eight Omega Plugin families, with one compatible set per website

The hosted website plugin system provides Image, Performance, Security, SEO, Web Metrics, Uptime & Availability, Accessibility Monitor and Scheduled Task Monitor. Each family has a Pure HTML and a separate WordPress implementation: sixteen implementations in the catalogue, but only the matching eight apply to an entitled website. Each plugin's Enable/Disable state is independent for that Website ID. These are not the Builder's sixteen generation engines.

Public third-party search is not the same as automatic installation

On WordPress, browse/search the full public WordPress.org repository through paginated results, in addition to the curated starter selection. Installation or activation must be requested for the selected authorised WordPress site. Review compatibility and required capabilities before proceeding.

On Pure HTML, discover browser libraries through the public cdnjs directory or search the wider npm registry. Discovery is not automatic execution or installation. The fourteen curated managed HTML add-ons retain their separate supported Install, Enable, Disable, Status and Sync controls.

Open Dashboard affects one installed plugin at a time

Where the selected plugin has a supported installed-plugin dashboard, Open Dashboard opens it inside the Editor's single-plugin workspace. Choosing a different plugin replaces the visible dashboard. If a plugin exposes unsupported or restricted management functions, it may require a separate authorised WordPress administrator workflow; never work around permission failures.

For full feature descriptions, see Omega Website Plugins. The Builder Engines page instead describes website generation and validation.

Omega Web Pro documentation

Use Website Editor when you want direct control of the licensed source.

Sign in to My Account, choose the licensed website and open Edit Website Code. Use Builder instead when the change is better expressed as a new website specification.

Open My Account →All Documentation

OMEGA WEB PRO HOSTING

Website Editor and hosted projects

The Website Editor remains the source-editing workspace for authorized customer projects. When Omega Web Pro Hosting is active, saved project versions can participate in the managed staging and production workflow.

Customer control plane

The Hosting Dashboard handles operational controls such as staging, production, backups, databases, SFTP and usage; the Website Editor handles source changes, validation, preview and versioned project editing.

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.

Billing documentation →

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.

Hosting documentation →

OMEGA HOSTING • PRODUCTION WORKFLOW

From Hosting Purchase to Live Website

Omega Hosting is an optional recurring service for one hosted website and is separate from the US$999 Lifetime Single Website Domain Licence. A hosting purchase is associated with the authenticated Omega customer account and the exact Website ID, domain, project and platform selected for that website.

Purchase + provision

After a Monthly, Annual or Two-Year Omega Hosting purchase is confirmed, Omega provisions the generated website into its assigned hosting environment. The hosted website then appears in the customer's authenticated My Account and Full Hosting Dashboard.

Hosting Setup Email + DNS

Omega supplies the required DNS instructions in the Hosting Setup Email and through authenticated hosting controls. The customer applies those records with the authoritative DNS/domain provider. Existing nameservers may remain in use unless the supplied instructions specifically require otherwise.

Verification + SSL

Provisioning or file upload alone does not make the public domain live. Omega verifies the public DNS connection; once the domain resolves correctly, SSL/TLS activation and certificate automation can proceed. The domain then resolves to the Omega-hosted production website.

Edit + update the live website

An active Omega Hosting customer can open the hosted project through My Account / Full Hosting Dashboard, work in Builder and/or Website Editor / Code Editor, save the project, then use Deploy / Update Live Website to update the existing production website.

Protected deployment

Before production activation, Omega verifies the authenticated account, Website ID, hosting entitlement, hosting allocation and permanent project source. Deployment uses validated project source, private staging, a pre-deployment restore point, production activation and post-deployment validation. If activation fails after the live site changes, Omega attempts automatic rollback.

Ongoing hosting controls

The Full Hosting Dashboard provides customer-facing access to deployments and deployment history, Domains & SSL, backups and restore points, databases, SFTP/access status, resources and usage, security status, billing and subscriptions, lifetime licences, activity/audit, support and account/privacy controls.

DNS responsibility: use the exact DNS records supplied for your website. Do not copy an IP address or DNS value from another customer's setup. Where available, My Account can resend the Hosting Setup Email. Domain registration is separate unless explicitly supplied, and correct DNS configuration and propagation are required before the public domain and SSL can become active.

CURRENT PRODUCTION WORKFLOW

Hosted website editing in production

For an entitled hosted website, the Website Editor is not an isolated download-only tool. My Account and the Full Hosting Dashboard provide authenticated entry points to the website's Builder/Editor workflow. The customer can edit and save the permanent project source, then use Deploy / Update Live Website from the hosting controls when the website is active and provisioned.

This hosted live-site workflow is separate from portable lifetime ZIP re-editing. Lifetime customers may reopen a signed same-domain ZIP through My Account; hosted customers can work against their authenticated hosted project and deploy the latest saved project to production through the protected deployment pipeline.