Getting Started with Veloxa Build

Veloxa Build is VeloxaHost's AI website and app builder. You describe what you want in plain language, the AI builds it in a live preview, and you refine it by chatting or by clicking the page. This guide takes you from signing in to a first version you are happy with.

What you need

  • A VeloxaHost account. Veloxa Build uses the same login as the console. If you don't have one, you can create it from the sign-in page.
  • A web browser. There is nothing to install, and no code to write.

The owner of an organization (with a verified email) can build on the Free plan. Pro is the Veloxa Build add-on: an owner or admin of your organization turns it on in the console under Settings → Add-ons, and it then covers everyone in the organization. Plan limits and prices are on the pricing page.

1. Sign in

Go to build.veloxahost.com. If you are already signed in to the VeloxaHost console in the same browser, you are signed in to the builder automatically. Otherwise, use the sign-in button: you sign in on the console's own page (with Google, GitHub or your password and MFA, as usual) and come straight back.

Log out in the builder ends the builder session only. The sign-in screen then offers to sign you out of VeloxaHost too.

2. Describe what you want

Type a description in the message box and send it. Say what kind of site or app it is, which sections or pages it needs, and how it should feel. For example:

Build a website for my bakery, Rise & Crumb. Sections: a hero with our name,
today's breads and pastries with prices, a custom cakes page with a gallery,
a pre-order request form, our opening hours and address. Soft cream and brown
colours, friendly rounded type, photos front and centre.

Ready-made prompts for restaurants, bakeries, salons, portfolios, SaaS landing pages and agencies are on the starter prompts page. Their "Start with this prompt" links open the builder with the text already in the message box, ready for you to edit before you send it.

If your request is too vague to build well, the AI may ask a couple of short questions first, each with options. Pick an answer, type your own, or skip, and it carries on.

Attach your own files

Drag files onto the message box, or use its attach button, to send them with your message: a logo, photos, a menu as a PDF, a CSV list of products. Each file is saved in your project's assets/ folder and the AI uses it where you ask. It can look at an image or read a PDF or text file when it needs the content.

AttachmentLimit
Files per message50
Images30 MB each
PDFs, text and data files10 MB each
Other files (audio, video, fonts, archives)25 MB each

3. Watch it build

While the AI works, a short checklist in the chat shows what it is doing, and the result appears in the live preview next to the conversation. After every change the builder reloads the preview and checks that the page actually runs; if it reports an error, the AI works on a fix before it finishes. Fixes use AI usage like any other message.

When it is done, the builder suggests a few next steps. Click one to send it, or ignore them and type your own.

4. Refine it

By chatting

Send another message describing the change: "make the header darker", "add a testimonials section", "replace the plum tart with a pear tart at 6.50". Short, specific messages work best.

By clicking

Turn on click-to-edit in the preview toolbar, then click the element you want to change: a heading, a button, an image. It is attached to your next message, so the AI knows exactly which element you mean. Describe the change and send.

Projects built before click-to-edit existed may say it is not available yet. Send any change in the chat and the page is rebuilt with support for it.

5. Go back with version history

After every AI message that changes your files, a version of the project is saved automatically. Open Version history in the preview toolbar (on a phone, in the toolbar's "…" menu) to see them and restore one. Restoring is reversible: you can switch back to any other version afterwards. The most recent 30 versions are kept per project.

Managing projects

  • Duplicate a project from its menu in the project list to use it as a starting point for another.
  • Delete a project to remove its files, versions and conversation, and to take down its draft and published site. Download it first if you might want it back.

Next steps