Omega Web Pro combines AI-assisted website planning, controlled Pure HTML and WordPress generation, responsive Builder preview before purchase, lifetime same-domain Builder regeneration and a private paid-customer Website Editor with direct source-code editing and real-time sandboxed preview. The same platform also coordinates responsive image production, SEO and schema, accessibility, performance, security, quality validation, My Account licence management and complete deployable ZIP export.
Core differentiator
Omega Web Pro uses live preview at two different stages for two different jobs. The public Builder preview helps customers generate and inspect the website before buying. The private Website Editor preview lets purchased customers directly edit the licensed website source and see valid changes reflected in real time.
Generate the website first, then inspect the actual build in desktop, tablet and mobile preview modes before purchase. The preview works with the generated project rather than only a static design screenshot.
After purchase, open a licensed Website ID from My Account, select a project file, edit the source directly and see valid changes appear in the sandboxed preview beneath the code editor.
Universal Website Studio
Omega gives the customer a broad control surface rather than reducing every project to a single prompt. Explicit selections become authoritative project requirements, while Auto choices can be refined by the assisted planning layer.
Define industry, sub-industry, business type, operating model, positioning and custom requirements for organisations that do not fit a preset.
Specify countries, cities, regions, service areas, local/national/international scope and regional writing requirements.
Set target audiences, website goals, calls to action, conversion priorities, exclusions and desired user outcomes.
Start with a short idea or supply extensive project requirements, business rules, background material and production instructions.
Control tone, terminology, audience level, writing character and content priorities.
Add project-specific layout, visual and image instructions alongside structured design controls.
Website architecture
The page system is designed for small websites and much broader organisations without forcing every project into a fixed five-page template.
Core business, service, product, ecommerce, trust, publishing, education, hospitality, locations, support, careers, legal, campaign and utility page types.
Services, locations, products, case studies, team members and articles can expand structured lists into individual generated pages.
Add requirements outside the built-in catalogue without forcing the site into a closed taxonomy.
Large site builds remain inside a controlled page-count boundary with staged generation and validation.
Navigation, internal links, sitemap, schema strategy and production files derive from the same validated architecture.
Generated page identities are normalized to reduce malformed paths, duplicate page identities and broken architecture.
Complete design system
Builder controls cover the decisions that materially shape the finished website, from typography and colour through navigation, heroes, cards, spacing, imagery and motion.
Premium, luxury, corporate, industrial, editorial, technical, minimal, creative, SaaS, ecommerce, hospitality and more.
Primary, accent, background, surface, text, heading, header, menu and coordinated visual roles.
Heading/body stacks, scale, weights, spacing and text treatment.
Control content width, density, spacing rhythm and visual breathing room.
Header treatments, alignment, sticky behavior, dropdowns, mobile menus, mega-menu options and breadcrumbs.
Centered, split, media-first, statement, full-bleed and other hero directions.
Outlined, elevated, glass, editorial, product, testimonial and other presentation systems.
Control emphasis, visual treatment and motion intensity with reduced-motion awareness.
AI-assisted strategy
The external AI provider is constrained to structured planning. Omega validates the plan and remains authoritative for architecture, production code, preview and export.
Refine positioning, design direction, content emphasis, CTA strategy, image allocation and search intent from a compact normalized brief.
A deterministic local planning path can keep Builder operating if the external provider is unavailable, rejected or rate-limited.
Malformed, unsafe or incompatible planning data is rejected before influencing production.
Explicit Builder selections outrank assisted Auto suggestions.
AI returns constrained strategy rather than being given unrestricted control over final HTML, CSS, JavaScript, PHP or deployment files.
Omega can expand validated strategy across the requested architecture locally rather than requiring one giant model response per page.
Omega-controlled production
Planning, media, pages, platform packaging, preview and finalization operate through controlled production checkpoints.
Production state survives across stages so large builds do not depend on one browser-to-server request.
Pages are produced in controlled batches for larger projects.
Uploaded media is processed in coordinated stages alongside the website build.
Builder can retry temporary continuation failures instead of throwing away an otherwise valid project.
Architecture, design, content, media, SEO, accessibility, performance, security and export share one validated project plan.
Shared Builder decisions remain synchronized until Omega routes the project to Pure HTML or WordPress production.
Pure HTML production
Pure HTML is a first-class output target designed around semantic documents, local styling, portable JavaScript, responsive media and supporting deployment files.
Receive actual HTML pages instead of a proprietary visual-editor document.
Website styling is packaged with the generated project rather than depending on Omega's public site CSS.
Ordinary website behavior can remain portable without a heavy application framework.
Metadata, structured data, sitemap.xml, robots.txt, llms.txt and supporting crawl files can be generated from the architecture.
Pages, assets and deployment-support files are packaged into a downloadable project.
The exported Pure HTML website can run on compatible hosting independently of Omega Web Pro.
Native WordPress production
WordPress output is not produced by merely renaming HTML files. Omega uses a separate production path with WordPress-aware architecture, setup material and validation.
WordPress production remains isolated from Pure HTML production so each platform receives the correct files and behavior.
Use modern block/Site Editor architecture or classic PHP theme output where appropriate.
Packages can include theme files, generated content, setup/import material and Omega installation support.
Support Site Editor options, reusable patterns, posts, categories, tags, custom post types, search and comments.
WordPress mode converts contact behavior to WordPress mechanisms instead of carrying Pure HTML API endpoints into the package.
Required theme files, content consistency, slugs, links, setup components and unresolved placeholders are checked before acceptance.
Private paid-customer Website Editor
The Website Editor is available from My Account for active Website IDs already owned by the authenticated customer. It is not an arbitrary public upload surface: customers select only their purchased licensed projects and edit supported files inside their private project workspace.
Select a licensed website, browse the project's file list, open supported files and edit the actual source. The editor includes line numbers, cursor location, Undo, Redo, Find, Replace and Replace All.
For previewable files, valid current changes are rendered beneath the editor in the sandboxed live preview so code changes can be inspected immediately at desktop, tablet or mobile sizes.
When a newly introduced blocking issue is found, Omega identifies the responsible validation area and line, marks the affected editor line and displays the reason in the Omega Live Validation message.
Newly introduced blocking syntax, malformed-data, security or protected-domain issues are prevented from entering Live Preview or being saved until corrected. Accepted changes are checked again server-side.
Saved Website Editor revisions are versioned, giving the licensed project a controlled edit history while the customer continues to evolve the site.
Validate the complete licensed website and generate an updated signed licensed ZIP after the editor changes pass the required checks.
The editor's live-validation interface maps detected issues to fourteen responsibility areas:
The licensed root host remains permanent. The editor protects the licensed domain and home-page canonical host while still allowing legitimate internal page filenames and paths to evolve under that same domain.
Example: changing terms.html to terms-and-conditions.html and updating its canonical path is allowed when the canonical host remains the permanently licensed domain.
Responsive image production
Omega's image architecture validates source media, creates practical responsive derivatives and coordinates those files with the generated markup.
Modern responsive delivery can include AVIF, WebP, JPEG and PNG families with practical fallbacks.
Derivative widths are capped to the source dimensions rather than enlarging small originals.
A project can use a real uploaded logo and supporting website imagery for optimization, allocation and responsive production.
Generated markup coordinates responsive source sets, dimensions, alt text, loading behavior and fallbacks.
Branding can generate favicon.ico, PNG favicon sizes, Apple touch icons, Android icons and Windows tile material.
Where supported by the server libraries, broader package workflows can include GIF still, TIFF and BMP alongside web formats.
Pure HTML and WordPress exports receive platform-appropriate image integration while sharing validated source processing.
Preview health checks confirm generated image assets are available before final export is enabled.
SEO + structured data
Omega coordinates page-level metadata and site-wide crawl support from the generated architecture instead of bolting SEO on after the website has already been built.
Search-focused page metadata can be aligned with page purpose, topic and site positioning.
Schema strategy can vary according to page type and purpose rather than using one generic block everywhere.
Canonicals, heading hierarchy, semantic sections and crawl-oriented internal architecture are coordinated with production.
The sitemap reflects the requested website architecture.
Crawler-control files can be produced with handling for utility or non-indexable pages.
Omega can produce llms.txt from the public architecture as part of the generated website package.
Quality, accessibility, performance, security + metrics
Omega separates structural build-time readiness checks from real-world deployment measurements while coordinating the major quality categories through the same production workflow.
Landmarks, H1 structure, image alternatives, accessible naming, focus considerations and reduced-motion awareness are part of the build checks.
Local asset strategy, media dimensions, responsive image families, payload expectations and CSS/JavaScript health are evaluated during production.
Generated output, paths, preview boundaries, external targets and selected unsafe patterns are inspected before delivery.
Omega surfaces quality/metrics signals without mislabelling a build-time assessment as a deployed real-world Lighthouse result.
Generation and editor workspaces remain outside the ordinary public website directory and are accessed through controlled application routes.
Project paths are normalized and constrained so editor/preview operations remain inside the authorized project boundary.
Sandboxing and restrictive preview behavior reduce the attack surface presented by untrusted project code.
Generated stylesheets must be available to the Builder preview before export health can pass.
Generated JavaScript asset availability is checked in the preview environment.
Generated media must be available rather than enabling export while the preview is still missing core assets.
Supporting project input + forms
Supporting material can complement the authoritative Builder specification, while form behavior is adapted to the selected production target.
TXT, Markdown, HTML, HTM and XML can be used as controlled additional project context.
A supporting ZIP can be inventoried and selected readable content can inform a new build within controlled extraction limits.
Supporting material complements the normalized specification rather than silently replacing Builder requirements.
Pure HTML projects can use compatible server-side contact handling and authenticated SMTP where deployed appropriately.
WordPress packages use WordPress mechanisms such as native post actions, nonce verification and wp_mail instead of Pure HTML endpoints.
WordPress validation checks that incompatible Pure HTML contact references have not leaked into the WordPress package.
Private customer account
Customer accounts are purchase-created rather than publicly registered. One purchased account can hold multiple separately licensed domains, each with its own permanent Licence ID and Website ID.
View every active lifetime domain licence connected to the customer account, including Licence ID, Website ID, platform information and generation history.
Reopen supported licensed projects and regenerate the same permanently licensed domain without purchasing that domain licence again.
Open the private Website Editor for an active licensed Website ID and work directly with supported source files and real-time preview.
See unpaid checkout orders that belong to the signed-in account.
Resume an existing open Stripe Checkout Session for the exact pending order instead of creating a duplicate order.
Remove an abandoned unpaid pending order and expire the active Stripe Checkout Session where available, without touching paid records or licences.
View original paid lifetime licence transactions associated with the account while zero-dollar same-domain re-exports remain outside purchase history.
Update supported personal and contact details without altering permanent licence identity.
Change password securely, request verified login-email changes and use account recovery flows without changing Licence IDs, Website IDs or licensed domains.
Lifetime Single Website Domain Licence
The lifetime entitlement is attached to one normalized domain and includes both supported production platforms, future same-domain Builder generations, private customer access and licensed Website Editor use for that website.
One-time payment • one permanently assigned website domain
Not included: domain registration, web hosting and email hosting are separate customer responsibilities unless expressly supplied under another agreement.
Preview health + licensed export + portability
Omega validates the generated project and its preview health, then packages the selected production target into a downloadable licensed ZIP that can leave the Builder with the customer.
Required generated assets must be available to the preview before the final export path is enabled.
Receive generated website pages, assets and supporting files for the selected production target.
Move HTML, CSS, JavaScript, images and support files to compatible hosting independently.
Receive the generated theme, content/setup material and supporting package files.
Licensed ZIPs can carry protected project information used to validate future same-domain re-editing workflows.
The exported site's continued operation does not depend on keeping the deployed site hosted by Omega Web Pro.
Feature questions
Yes. The public Builder can generate the website and provide responsive desktop, tablet and mobile preview before the lifetime domain licence is purchased.
Yes. Purchased customers can return through My Account and use the Builder workflow again for the same licensed domain, including future redesigns and generations under the existing lifetime licence.
Yes. Active licensed Website IDs can be opened in the private Website Editor from My Account for supported source-file editing with real-time sandboxed preview and validation.
No. Builder preview is the generation preview used before and after purchase when working through Builder. Website Editor preview is the second real-time preview used while directly editing licensed project source files.
No. The permanent licensed host remains protected. Internal page paths and filenames can legitimately change while staying under the same permanently licensed domain.
No. The NZ$999 purchase is the lifetime licence for that one permanent domain. Future same-domain generations are recognized under the existing licence.
Yes. Multiple separately purchased domain licences can appear inside the same customer account. Each domain retains its own Licence ID and Website ID.
No. Compatible hosting is arranged separately by the customer. Pure HTML and WordPress packages are designed to be deployable outside Omega's own website environment.
Generate • Preview • Licence • Regenerate • Edit Code • Validate • Export
Start in the public Universal Website Studio. Generate and preview before purchase. Then return through My Account for lifetime same-domain Builder regeneration or direct real-time licensed source-code editing.
