FAQ

Vibewax is designed for building marketing websites, landing pages, portfolios, blogs, web apps (contact forms, booking pages, record-keeping systems), simple 3D apps and games, visuals, and prototypes or MVPs. It excels at professionally designed, fast-loading sites.

Vibewax is not the right tool for complex enterprise applications, native iOS or Android mobile apps, desktop software, or projects requiring PHP, Python backends, WordPress, or Supabase. It works exclusively with Next.js (React) and its built-in database.

Yes, Vibewax works fully in any language. Simply give the agent instructions in your preferred language (Czech, French, German, Spanish, etc.) and it will generate the project content in that language. If you need multilingual pages, describe clearly which sections should appear in which language.

Yes. Vibewax can set up authentication using OTP (one-time password sent by email) or a standard email and password login system. Just describe what you need and the agent will implement it.

Yes. Visual edits lets you click directly on text, images, and other elements in the preview and change them without sending a message to the agent. Those changes are written into your project when you save and use no credits. The exception is Ask AI on text or an image, which does use credits and shows the price before you run it.

Vibewax works great in a mobile browser, so you can create and manage your projects right from your phone. The one exception is Visual edits, which is available only on larger-screen devices.

Click the Publish button in the top-right corner of the editor. After publishing, your site is live at a free Vibewax subdomain. To connect a custom domain, go to Settings → Domains.

This is a known issue where the build completes but the UI does not update. Contact support with your project link and they will manually reset the publish state. Your site is most likely already live even if the dashboard still shows building.

The preview URL and the published URL (your Vibewax subdomain or custom domain) are separate environments. You need to click Publish to push your changes to the live site. If the live site still does not update after publishing, try duplicating the chat and republishing from the duplicate. This often resolves stale deployment issues.

Yes. Go to Settings in your project and use the export option to download a ZIP of your source code.

Every published site carries a machine-readable ai-generated tag, but that is not a visible notice to your readers. Whether you need to disclose anything further about your content or your own AI features depends on applicable law and the specific use case. Using AI responsibly walks through the common cases.

No. The notice you see in Vibewax applies to Vibewax. If your project has a chatbot or any other AI feature, telling your end users about it is part of your application. Ask the agent to add a notice above the chat input or at the start of the conversation.

In your project, go to Settings → Domains, type your domain name, and click Connect. Then follow the status shown there. Some white-label setups configure DNS automatically or activate the domain through a partner proxy. If the platform shows DNS records, add those exact values at your registrar and return to click Refresh.

Add records only when Settings → Domains asks you to. Manual setups typically need two records:

• An A record for the root domain pointing to Vibewax’s IP address
• A CNAME record for www pointing to Vibewax’s hostname

The exact values are shown in Settings → Domains when you add your domain.

Check Settings → Domains first. If it shows a missing apex record, add the exact A record displayed there and remove conflicting A or AAAA records for the root domain. If your white-label provider manages DNS automatically or uses a partner proxy, refresh the status and contact your brand’s support team instead of changing records blindly.

If the page says that DNS is being configured automatically, wait a few minutes and click Refresh. For manual setup, confirm that the records at your registrar exactly match what the platform shows and remove conflicting records. DNS propagation can take up to 24 hours. For partner-proxy setups, contact your brand’s support team if the domain does not activate.

Vibewax does not provide email hosting. For email on your custom domain (e.g. info@yoursite.com), sign up with a third-party provider such as Google Workspace, Zoho, or Microsoft 365, and configure their MX records with your registrar. Once you have an email address, the Vibewax agent can set up contact forms to send notifications to it.

Yes. Vibewax has a built-in email API powered by Resend. To send from your own domain address, you need your own Resend account and API key. Ask the agent to set up email functionality and provide your desired sender and recipient address.

The default limit is a maximum of 10 emails per minute per application. Vibewax can only send emails, not receive them. It is not suitable for newsletters or bulk marketing emails.

First, check your spam or junk folder. If emails are truly not arriving, contact support with the link to your project and the email address involved. The team can investigate email delivery on the backend.

If the agent shows no progress for more than 10 to 15 minutes, reload the page. If the preview is frozen, try Rebuild Preview or Restart App in its toolbar. If the last change broke your project, use Version history or Restore this version. If the problem persists, contact support with the chat link and approximate time. Credits consumed during a confirmed stuck session will be reviewed.

When reporting an error, be as specific as possible. Describe what you were doing before the error, what you see now, what is not working, and what the correct behavior should be. The more detail you provide, the better the agent can fix it on the first try.

Vibewax has approximately 20 steps per user request. If your prompt is too complex, the agent may not complete everything. Break large requests into smaller sequential steps: send one specific change per message, verify it works, then move on.

Vibewax saves project versions so you can restore earlier code. For your own copies, use GitHub for code if your plan supports it, and Export in the Database tab for table data. The ZIP does not include files uploaded to your app. A duplicate copies the current project, not an earlier database state.

Yes. Click the clock icon in the top bar to open Version history, pick a version to preview it, and click Restore. You can also use the Restore this version button under any agent response. Either way, the project code goes back to the state it was in at that point. See Version history. This restores code only, not database data or files uploaded to your app. Publish again to update your live site.

Yes. Vibewax runs on several models from different companies, and you can pick which one the agent uses. GLM 5.3 Flash is the default. It is fast and cheap on credits, and works well for most everyday changes. See AI models for the full list and what each one suits.

You can change the model in two places. To change it for all your chats, open Settings, go to the Preferences tab, and pick a model under AI. To pick a model for one specific project, open that chat, go to the Settings tab, and pick a model under AI Model. The setting in a project always takes precedence over the setting in your account.

Stay on the default unless you have a reason to change. Move up to a model built for complex work when you are adding something like user accounts, payments, or more complex logic. Drop to a faster, cheaper one for text edits and small tweaks. See AI models for the current options.

Each company builds its models differently, and the differences show up more in style than in what the model can do. Which one suits you often comes down to the project and to personal preference, so it is worth trying a few.

Yes. Credit use depends on the selected model’s rates and the tokens it processes and generates. The size of the change and the length of the conversation also play a part.

Every model is marked EU, US, or Global. Global routing can process requests in different regions, including outside the EU. If your project handles personal data and you need that data to stay in the EU, pick a model marked EU.

Yes. Your choice applies to your next message. Everything the agent has already built stays as it is, and it keeps the full history of your project, so you can switch models at any point without losing anything.

Projects you started a while ago may still be set to a model that has since been retired. Those projects keep working. They now run on the newer version of the same model, so you get the improvements without doing anything. New chats always use the current lineup.

Error 524 is a timeout, meaning the server did not respond in time. Try refreshing the page after a minute or two. If it persists, contact support with your chat link.

The sandbox server crashed. It should restart automatically within one to two minutes. If it does not, contact support with your chat link. The team can restart the sandbox and refund any credits consumed during the outage.

This is often caused by your browser’s automatic page translation interfering with the Vibewax editor. Disable browser translation for the platform domain and try again. If the error appears on your published site, report it to the agent with a clear description or contact support.

Single images must not exceed 8000×8000 pixels. If uploading more than 20 images in one request, each must be under 2000×2000 pixels. Files should be under 5 MB. If you encounter an SVG upload error, contact support.

Open the chat menu and select Duplicate. A normal duplicate copies the current project without its conversation history and gets a separate database. Current table data is copied where supported; older projects with legacy App Files may start with an empty database and no uploaded files. Publish the copy and reconnect its custom domain if needed. Use Version history to recover an earlier code version.

No. Each duplicate gets its own separate database.

Yes. Click Share next to the Publish button and set the visibility to Anyone with the link. Share the link. Anyone who opens it can view the project and duplicate it into their own Vibewax account.

Yes. Any project can be duplicated and shared with your client. They can then continue developing and managing the site in their own Vibewax account, independently from you.

No. Every Vibewax project gets one automatically. You don’t need to set one up with a provider, enter credentials, or connect anything. Describe what you want to store, such as contact form submissions or blog posts, and the agent creates the tables and wires them into your project.

Every project has its own isolated database with real-time updates and automatic scaling, hosted in the EU. See Databases.

The Database tab lists your tables and shows the rows in each one. You can filter and sort them, edit values right there, add rows, or delete them. Creating tables and changing which fields they have happens in your project’s code, so ask the agent for those, for example: “Add a phone field to the Leads table.”

Yes. In the Database tab, click Add testing mode and Vibewax creates a Testing database, a separate copy of your data that you can work in without changing what your users see. You can switch between your Live and Testing databases whenever you want, and publish from either one. Publishing from Testing runs a compatibility check first so your published app keeps working with its existing data.

Export in the Database tab downloads a ZIP snapshot of your table data, and Import restores one. Files your project stores, such as uploaded images, are not part of that file. Keep a snapshot before bigger changes, since deleting rows and importing a snapshot both replace data permanently.

Vibewax builds search-engine-friendly sites. Server-side rendering, clean HTML, and meta tags are all handled by Vibewax for you. Once you publish your project, the SEO audit scores your site and tells you what to improve. You can also edit meta tags, page titles, and descriptions in Settings → SEO.

The audit in the SEO tab checks your published site, so it stays locked until you publish. If you want a score before that, ask the agent in chat to run an SEO audit and it checks a preview of your current edits instead.

The audit reflects your last published version. If you’ve changed something since then, publish your project again and the audit results will refresh. You can also ask the agent to audit your unpublished changes on a preview.

AI readiness measures how well AI crawlers, such as those from ChatGPT, Claude, or Perplexity, can reach your site and understand it. It checks that your content is on the page itself rather than loaded with JavaScript, that AI crawlers aren’t blocked, and that an llms.txt file is available to guide them. Vibewax renders your pages on the server automatically.

Work through the list of issues, errors first, then warnings. Either use the Fix all with AI button and hand the agent every issue at once, or work through them one by one. Then publish your changes and the score updates on the next audit.

Google indexing takes a while, often days to weeks. To speed it up, submit your site URL to Google Search Console at search.google.com/search-console. You can also share your URL on social media, since Google crawls links it finds elsewhere on the web.

Technically yes, using your published Vibewax URL in an iframe. However, content inside iframes is poorly indexed by search engines, which has a negative impact on your SEO. A better approach is to use Vibewax as a standalone site with its own custom domain.

Your account is your personal identity — your email, sign-in, and personal preferences like theme and language. A workspace is where the actual work happens, with its own projects and credits.

Settings under Personal follow your account everywhere. Your theme, language, AI model preference, and notifications stay the same in every workspace. Settings under Workspace are tied to each workspace, so domains, API keys, and connections are different in each one.

Contact support and provide the new email address. They will update it on the backend. Note: you cannot use an email address that is already registered to another Vibewax account.

Check your spam or junk folder first. If the email is not arriving at all, contact support. They can verify your account status and help with authentication.

Contact support and request account deletion. They will delete your account and all associated data. Note: this action is irreversible. All projects, credits, and data will be permanently removed.

Contact Vibewax support with your project link and a description of the issue.

On the affected agent response, choose Report issue and, if the option is available for your workspace, select Request a credit review. The automated review usually takes about a minute and can restore credits for clear agent or platform failures. If the option is unavailable or the result needs another look, contact support with the chat link and report details.