Create a complete online store just by registering on Vareons

The core idea on Vareons is that an online store is not assembled in disconnected phases — the account and the store are created at the moment of registration. The merchant opens /register and enters their name, business name, Website Name, the subdomain they want (for example "mystore", which becomes mystore.vareonos.com), phone, email and password. As soon as registration completes, the store exists on the internet with no separate installation or hosting step.

This is possible because Vareons models the user as the tenant: the store id equals the user account id (tenantId = User._id), and the entire site content is stored on the same document. So when the account is created, the server seeds a complete, renderable store: homepage component settings (a hero, a products grid, category tiles, and more products), header and footer components, the site layout with brand colours and bilingual SEO meta tags, and ready static pages such as product, checkout and contact. The merchant needs neither an external template nor extra integrations to start.

The subdomain is part of registration itself, so the store runs at {name}.vareonos.com, and the platform also owns an additional domain, vareons.store, that operates alongside the primary one. A custom domain the merchant owns can be connected later from dashboard settings. A default trial plan is also applied with registration (by default Basic for three days, adjustable by the platform admin), so the store stays available while it is being set up.

Afterwards the merchant goes through the onboarding flow (/onboarding) to turn the default store into one that reflects the business: choose the business type, then the template, then brand identity (colours and logo), then the store currency, then the product card theme, and finally the summary. These steps do not create the store again — they customise the very data that was born with registration.

The dashboard, meanwhile, is wired to the store structurally rather than separated from it. The storefront and the dashboard read and write the same tenant document: what the merchant edits in products, categories, prices, discounts, shipping and storefront visibility appears on the public store, and what a customer creates as an order on the store appears immediately in the dashboard orders page. Every record — products, orders, customers, reviews — is scoped by tenantId, so merchants' data never mixes.

In practice this means the first product you add from the dashboard appears in the homepage grid and on the products page, and the first order from the store shows up in orders with the customer, payment and shipping details. From there you can edit any component on any page in the live website editor, change the entire store theme from dashboard settings with a single apply action, or connect a custom domain. None of these paths require writing code or running anything on the merchant's machine.

In short: registration is not merely creating an account — it is creating a self-contained store that is ready to operate. The store takes visitors, shows products, completes orders, ships, accepts payments, and is managed entirely from the dashboard, from the first minute.