New Visitor
Open Builder without purchasing, define the website, generate it and inspect the responsive public Builder preview.
Open Builder →This is the central documentation hub for the complete Omega Web Pro platform: Universal Website Studio, website specification, AI-assisted planning, blueprints, page architecture, staged generation, Pure HTML and native WordPress production, responsive images, SEO and schema, accessibility, performance, security, Web Metrics, the public Builder live preview, secure Stripe purchase, purchase-created customer accounts, lifetime domain licences, the private Website Editor with its second real-time sandboxed preview, version history, validation, updated licensed ZIP export and deployment.
Start here
Omega Web Pro is best understood as a website lifecycle rather than a one-time AI generation screen. The Builder handles specification, generation and preview. Purchase creates the permanent licence and customer account. My Account then gives the customer two lifetime editing paths for that licensed domain.
Open Builder without purchasing, define the website, generate it and inspect the responsive public Builder preview.
Open Builder →Purchase the NZ$999 Lifetime Single Website Domain Licence through secure Stripe Checkout. Confirmed payment creates the permanent licence and customer account setup flow.
Purchase & Licence Guide →Use My Account to manage licences, reopen Builder, edit licensed source code, resume or delete pending checkout orders, view paid purchase history and manage account security.
Open My Account →Complete documentation library
The buttons below define the permanent public documentation URLs for the supporting guides. Existing product pages are linked where they already provide the authoritative guide; the remaining dedicated documentation pages can be created at these exact URLs next.
Universal Website Studio documentation
The customer can begin with a short idea or provide a detailed professional specification. Explicit Builder choices are requirements; Auto choices can be resolved through the assisted planning layer.
Choose from 73 current industry starting points, select multiple relevant industries where appropriate, or define a custom industry and sub-industry.
Select from 105 built-in page types plus custom requirements across business, commercial, ecommerce, content, support, legal, campaign and utility needs.
Services, locations, products, case studies, team members and articles can expand structured lists into individual generated pages.
The current browser and server generation paths enforce a maximum of 120 generated pages per website build.
Provide up to 50,000 characters of project requirements, background, business rules, exclusions and detailed production instructions.
Control theme, colours, typography, content width, spacing rhythm, corners, shadows, backgrounds, header, navigation, mobile menu, hero, cards, imagery, gallery, buttons and motion.
Request secure contact forms, newsletter sections, booking/quote CTAs, search UI, galleries, testimonials, catalogues, pricing tables, analytics hooks, cookie banner shells, RTL and multilingual-ready structure.
Controlled TXT, Markdown, HTML, HTM, XML and ZIP source material can supplement—but does not silently replace—the authoritative Builder specification.
AI + generation architecture
The generation system separates planning from production so an external AI response does not become unrestricted production code.
Builder inputs are combined into one authoritative brief covering business identity, architecture, design, content, media, features and platform requirements.
When configured, a compact structured strategy request can refine positioning, content emphasis, calls to action, image allocation and related planning choices.
Deterministic fallback planning can continue the same workflow when the external provider is unavailable, rejected, rate-limited or otherwise unusable.
Structured planning output is checked before it can influence generation. Explicit customer selections remain authoritative.
Builds progress through initialization, media, page batches, finalization, platform packaging, validation and preview publication rather than one oversized request.
Temporary continuation failures can be retried so a substantial build is not automatically discarded because one stage briefly fails.
Production targets
Both start from the same validated specification, then branch into platform-appropriate architecture, forms, files, validation and deployment packages.
Produces semantic HTML5 pages, local CSS, vanilla JavaScript, responsive images and supporting deployment/crawl files in a portable website package with no CMS or database dependency.
Uses a dedicated WordPress renderer and validator. It can produce block/Site Editor or classic PHP theme architecture, generated content material and setup/import components.
Media + SEO + accessibility + performance + security + metrics
These are build-time readiness systems. Deployed Lighthouse, Core Web Vitals, penetration testing, legal review and manual accessibility review remain separate deployment-time responsibilities where required.
Uploaded media is validated and can produce AVIF, WebP, JPEG and PNG responsive derivatives without unnecessary upscaling, plus favicon and multi-resolution ICO families.
Image Engine →Checks titles, descriptions, H1 structure, canonicals, Open Graph, JSON-LD, sitemap, robots, llms.txt and utility-page indexing behavior.
SEO + Schema →Structural checks include landmarks, heading organization, image alternatives, skip links and accessible names. This is readiness auditing, not WCAG certification.
Checks local assets, third-party dependencies, image dimensions, payload discipline, CSS integrity and responsive media strategy.
Performance →Reviews generated output for selected unsafe patterns, remote script concerns, external-target handling, private project boundaries and deployment hardening expectations.
Security →Build-time diagnostics are deliberately distinguished from browser runtime metrics such as LCP, CLS and INP. Measure those on the deployed URL using appropriate browser tooling.
Web Metrics →Two separate live-preview systems
The first is a public generation preview. The second is a private licensed-code editing preview available after purchase.
After generation, Builder publishes the temporary project into its controlled preview environment. The customer can inspect desktop, tablet and mobile views before purchase.
A purchased customer opens one of their own active Website IDs, selects a supported project file, edits the source and sees valid changes in the sandboxed preview beneath the editor.
Private Website Editor
The Website Editor is not a public arbitrary-code upload surface. It is tied to the authenticated purchased account and verified licensed Website ID.
Purchased websites appear as selectable project controls. The selected project loads its own authorized filenames into the file sidebar.
Supported files load into the editor with line numbers, cursor position, Undo, Redo, Find, Replace and Replace All.
Newly introduced blocking issues can be shown at the responsible line with the validation area and reason.
Blocking syntax, malformed-data, security or protected-domain issues can prevent changed content from entering Preview or Save until corrected.
Accepted editor saves create versioned revisions for the licensed project.
Whole-project validation can be run before generating an updated signed licensed website ZIP.
Purchased customer My Account
There is no public Create Account registration flow. The first confirmed paid licence purchase creates the customer account using the purchaser email and starts secure account setup.
View each licensed domain, Licence ID, Website ID, supported platforms, generation count and other permanent commercial identity information.
Reopen supported licensed project data and regenerate the same permanent domain without purchasing that domain licence again.
Open the active licensed Website ID in the private Website Editor for direct source editing, real-time preview and validation.
View unpaid checkout orders associated with the currently authenticated customer account.
Resume the exact existing open Stripe Checkout Session rather than silently creating a duplicate pending order.
Remove an abandoned unpaid pending order and cancel/expire its active Stripe Checkout Session where available. Paid records and issued licences are protected.
View original paid lifetime domain licence transactions. Future zero-dollar same-domain generations or exports are not recorded as new NZ$999 purchases.
Update personal and contact information without changing the permanent licence-domain relationship.
Change password, request a verified login-email change and use password recovery while keeping Licence IDs, Website IDs and licensed domains permanent.
NZ$999 Lifetime Single Website Domain Licence
The licence is a commercial identity record, not merely a download token. The customer account can hold several licences, but each website domain has its own Licence ID and Website ID.
| Licence Element | How It Works |
|---|---|
| Price | NZ$999 one-time for one Lifetime Single Website Domain Licence. |
| Licensed Domain | Permanently assigned normalized domain. A different domain requires a separate licence. |
| Platforms | Licence rights include future Pure HTML or WordPress generation for that same domain; one production target is generated at a time. |
| Builder Rights | Unlimited future same-domain generations/re-edits under the existing licence. |
| Website Editor Rights | Private direct source editing for the active licensed Website ID, including preview, validation, version history and updated ZIP generation. |
| Account Ownership | Account ↔ Licence ID ↔ Website ID ↔ licensed domain relationship remains protected. |
| Hosting / Domain Registration | Not included in the NZ$999 licence unless supplied under a separate agreement. |
| Future Same-Domain Exports | Recognized under the existing licence rather than treated as a new paid purchase. |
Export, hosting and deployment
Temporary generation workspaces and previews are not the production website. The authoritative package comes from the generated project and the applicable licensed export workflow.
Download the generated source project after the required generation/preview/licence gates complete.
Place the generated website files in the intended hosting document root without accidentally nesting them inside an extra wrapper directory.
Use the generated theme, setup/installer material, content JSON/WXR and installation instructions with a compatible WordPress environment.
Pure HTML server-side contact functionality requires compatible PHP/hosting and authenticated SMTP configuration. WordPress packages convert form handling to WordPress-native mechanisms.
The customer remains responsible for domain registration, DNS and hosting configuration unless separately supplied.
Test navigation, responsive behavior, forms, HTTPS, redirects, canonicals, sitemap, robots, schema, Lighthouse/Core Web Vitals, accessibility and security on the final deployed URL.
Support, policies and customer responsibility
Generated content, AI-assisted planning and readiness checks still require customer review before publication. Customers remain responsible for the accuracy, lawfulness and suitability of the websites they deploy.
Quick answers about Builder use, platforms, licences, accounts and exports.
FAQ →Help with Builder, generation, purchases, licences, My Account, Website Editor, export and deployment.
Support →Commercial and service terms governing Omega Web Pro use and purchases.
Terms →Rules covering generated content, platform abuse, illegal/harmful use, licence abuse and customer responsibility.
Acceptable Use →Information about privacy and personal-data handling.
Privacy →Intellectual-property and copyright information.
Copyright →Omega Web Pro's own accessibility information and accessibility expectations.
Accessibility →Contact Omega Web Pro for sales, customer and general enquiries.
Contact →Build • Preview • Licence • Regenerate • Edit Code • Validate • Export
Start in Builder, return here when you need implementation detail, then use the dedicated guides for purchased-account management, editing, licensing, export and deployment.