> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibely.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

> Answers to common questions about building apps, managing projects and your account, security, and how Vibely works.

<Frame>
  <img src="https://cdn.vibely.sh/doc/v1/faq.webp" alt="Answers by section" width="1200" height="675" />
</Frame>

## Getting started

<AccordionGroup>
  <Accordion title="What is Vibely?">
    Vibely is an AI platform that builds web apps and native iOS and Android apps from natural language. You describe what you want, Vibely writes the code, runs it in a cloud sandbox with a live preview, and publishes it when you're ready. See [Welcome to Vibely](/introduction/welcome).
  </Accordion>

  <Accordion title="What is a workspace?">
    A workspace is where you and the people you invite build together. It holds your projects, members, billing, and settings, and every project lives in exactly one workspace.

    * Your plan and credits belong to the workspace, and everyone in it builds from the same pool.
    * You can belong to several workspaces and switch between them from the workspace switcher on the dashboard.
    * Owners and admins can set usage limits and alerts so no one person uses up the shared credits.

    See [Workspace](/features/workspace/overview).
  </Accordion>

  <Accordion title="What can I build with Vibely?">
    Web apps such as landing pages, SaaS products, dashboards, internal tools, and marketplaces, and native mobile apps for iOS and Android built with Expo. Apps can store data and sign users in through your own [Supabase](/integrations/supabase), take payments with [Stripe](/integrations/stripe) or [RevenueCat](/integrations/revenuecat), and call AI models through [Vibely AI](/features/backend/ai).
  </Accordion>

  <Accordion title="Do I need coding experience?">
    No. You build by describing what you want in plain language. If you do write code, every project is a normal codebase you can edit in the [code editor](/features/projects/code-editor) or sync to [GitHub](/integrations/github).
  </Accordion>

  <Accordion title="How do I create a project?">
    Type a description into the prompt box on the [dashboard](/introduction/dashboard), choose **Web** or **Mobile**, and send it. The [Quick start](/introduction/quickstart) walks through a first project end to end.
  </Accordion>

  <Accordion title="Can I start from a template instead of a blank page?">
    Yes. Open **Templates** in the sidebar and start from a working app. On the Business plan, your workspace can also keep its own template library. See [Templates](/features/design/workspace-templates).
  </Accordion>

  <Accordion title="Can I build a mobile app?">
    Yes. Select **Mobile** above the prompt box to build a native iOS and Android app with Expo. You preview it in the browser and on your phone through Expo Go, and submit it to TestFlight and Google Play from the editor. Mobile projects need a Pro plan or higher. See [Mobile apps](/features/mobile-apps/overview).
  </Accordion>
</AccordionGroup>

## Building with Vibely

<AccordionGroup>
  <Accordion title="How do I build efficiently?">
    * Start small: get the core working before adding logins, databases, and integrations.
    * Ask for one change at a time and check the preview after each.
    * Use [Plan mode](/features/agent/plan-mode) for large features, so you agree on the approach before code is written.
    * Put rules you want followed every time in [Knowledge](/features/context/knowledge) instead of repeating them.

    See [Prompting best practices](/prompting/best-practices).
  </Accordion>

  <Accordion title="How should I structure my prompts?">
    Say who the app is for, what data it handles, and how it should feel. Be specific about where a change should happen and what "done" looks like. The [Prompt library](/prompting/library) has ready-made prompts for common features.
  </Accordion>

  <Accordion title="What should I do when I hit an error?">
    When the preview shows an error, an error card appears in the chat. Select **Try to fix** to run a repair turn, which doesn't cost credits. If that doesn't solve it, describe exactly what you see and what you expected. If a change made things worse, restore an earlier version from [Version history](/features/projects/history). See [Debugging](/prompting/debugging).
  </Accordion>

  <Accordion title="Can I connect a backend to store data?">
    Yes. Vibely connects projects to your own [Supabase](/integrations/supabase) account for a Postgres database, authentication, file storage, and edge functions. Pick a Supabase organization or project from **Database** in the **+** menu, or ask Vibely to add one.
  </Accordion>

  <Accordion title="Can I add login to my app?">
    Yes. Once the project is connected to Supabase, ask Vibely to add sign-up and login. See [Authentication](/features/backend/auth) for web apps and [Mobile authentication](/features/mobile-apps/auth) for mobile apps.
  </Accordion>

  <Accordion title="Can I add third-party APIs?">
    Yes. Use a [connector](/integrations/connectors/overview) where one exists, such as Stripe, GitHub, Notion, or Linear, or ask Vibely to call any API directly and store its key as a project secret.
  </Accordion>

  <Accordion title="Can I store sensitive API keys?">
    Yes. Store them as project secrets, which are encrypted and never returned in plain text. When the agent needs a key, it asks you to enter it in the editor rather than in chat. See [Secrets](/features/backend/secrets).
  </Accordion>

  <Accordion title="How do I add payments?">
    Connect [Stripe](/integrations/stripe) for web payments and subscriptions, or [RevenueCat](/integrations/revenuecat) for in-app purchases in mobile apps. See [Payments](/features/grow/payments).
  </Accordion>

  <Accordion title="How can I improve SEO and AI search visibility?">
    Open **SEO & AI search** from the editor header to review how search engines and AI assistants see your app, and ask Vibely to fix what it finds. See [SEO](/features/grow/seo).
  </Accordion>

  <Accordion title="How long does it take to build a project?">
    A first version usually appears within minutes. A real product takes as many turns as it needs: most people build in short loops of one change at a time.
  </Accordion>
</AccordionGroup>

## Features

<AccordionGroup>
  <Accordion title="How do I find project settings?">
    Open the project and go to its settings from the editor. See [Project settings](/features/projects/settings).
  </Accordion>

  <Accordion title="Can I control who can see my project?">
    Yes. Projects are visible to the whole workspace by default. On the Business plan, you can make a project **Restricted**, so only you and the people you invite can open it. See [Collaboration](/features/collaboration/overview).
  </Accordion>

  <Accordion title="Can I rename a project?">
    Yes. Hover the project in the sidebar, open its menu, and select **Rename**.
  </Accordion>

  <Accordion title="How do I duplicate a project?">
    Remix it. Remixing creates an independent copy you can change freely. See [Remix a project](/features/projects/remix).
  </Accordion>

  <Accordion title="Can I delete a project?">
    Yes. Hover the project in the sidebar, open its menu, and select **Delete**. Deletion is permanent.
  </Accordion>

  <Accordion title="What is Plan mode?">
    In Plan mode, Vibely investigates and writes a plan before changing any code. You review the plan, then approve it to build, or ask for changes. Turn it on with the **Plan mode** toggle next to the send button. See [Plan mode](/features/agent/plan-mode).
  </Accordion>

  <Accordion title="Can I see and edit the code?">
    Yes. Open the **Code** tab in the editor to browse and edit files directly. See [Code editor](/features/projects/code-editor).
  </Accordion>

  <Accordion title="Can I edit text or colors by hand?">
    Yes. Turn on **Edits** in the composer and click an element in the preview to change it. See [Visual edits](/features/design/visual-edits).
  </Accordion>

  <Accordion title="Can I collaborate on my projects?">
    Yes. Invite people to your workspace or to a single project, and give them the right role. See [Collaboration](/features/collaboration/overview) and [Comments](/features/collaboration/comments).
  </Accordion>

  <Accordion title="Does Vibely host my published app?">
    Yes. Published web apps are hosted on a `vibelyagent.com` address on every plan. See [Hosting](/features/deploy/hosting).
  </Accordion>

  <Accordion title="How do I publish my project?">
    Select **Publish** in the editor, choose the address and who can see the website, and publish. Later changes go live only when you publish again. See [Publish your app](/features/deploy/publish).
  </Accordion>

  <Accordion title="How do I use my own domain?">
    Connect a domain you already own from the project's domain settings. Custom domains need a Pro plan or higher. See [Custom domain](/features/deploy/custom-domain).
  </Accordion>

  <Accordion title="Can I see analytics for my published app?">
    Yes. Published apps have visitor analytics: visitors, pageviews, sources, devices, and countries. See [Analytics](/features/grow/analytics).
  </Accordion>

  <Accordion title="Can I add images to a prompt?">
    Yes. Use **Upload files or photos** in the **+** menu, paste an image, or drop it into the prompt box. Vibely uses it as a visual reference.
  </Accordion>

  <Accordion title="Can I export all of my project's code?">
    Yes. Download the codebase from the project's Git settings, or sync the project to a GitHub repository. See [Git sync](/integrations/git-sync) and [Code ownership](/features/deploy/ownership).
  </Accordion>

  <Accordion title="How do I see my project history and restore an earlier version?">
    Every change is saved as a version. Open **Version history** from the editor header to browse versions and restore one. See [Version history](/features/projects/history).
  </Accordion>

  <Accordion title="Can I use Vibely from Claude, ChatGPT, or Cursor?">
    Yes. Connect the [Vibely MCP server](/integrations/vibely-mcp-server) and your assistant can create, iterate on, and publish your projects.
  </Accordion>
</AccordionGroup>

## Managing your account

<AccordionGroup>
  <Accordion title="How do I cancel my subscription?">
    Go to **Settings → Plans & credit usage** and select **Cancel plan**. See [Plans](/features/account/plans).
  </Accordion>

  <Accordion title="Can I delete my account?">
    Yes. Go to **Settings → Account**, select **Delete account**, and type `delete my account` to confirm. This permanently deletes your account, workspaces, projects, and data. If you own a workspace that still has other members, delete or transfer it first. See [Delete your account](/features/account/deleting).
  </Accordion>

  <Accordion title="How do I turn on two-factor authentication?">
    Go to **Settings → Account**, click **Set up** on the **Two-factor authentication** card, scan the QR code with an authenticator app, then enter the 6-digit code and click **Verify and turn on**. See [Two-factor authentication](/features/account/settings#two-factor-authentication).
  </Accordion>

  <Accordion title="Why is Vibely asking for my two-factor code before I publish?">
    Your workspace has **Require two-factor authentication** turned on, so publishing and changing build secrets need a session that has verified a code. Enter the code from your authenticator app, then try again. If you haven't set up two-factor authentication yet, do that first in **Settings → Account**. See [Privacy & security](/features/workspace/privacy-security#require-two-factor-authentication).
  </Accordion>

  <Accordion title="How do I invite my team?">
    Go to **Settings → People** and invite members by email. See [People](/features/workspace/people).
  </Accordion>
</AccordionGroup>

## Policies and security

<AccordionGroup>
  <Accordion title="How can I get support?">
    Ask in the project chat first for anything about your app. For everything else, select **Help** in the account menu, email [support@vibely.sh](mailto:support@vibely.sh), or ask the community on [Discord](https://discord.gg/VqrAzMYh8e). The [Support policy](https://vibely.sh/support-policy) explains what to expect on each plan.
  </Accordion>

  <Accordion title="Where can I find the privacy policy and terms?">
    See the [Privacy Policy](https://vibely.sh/privacy-policy), [Terms of Service](https://vibely.sh/terms-of-service), and [Acceptable Use Policy](https://vibely.sh/acceptable-use).
  </Accordion>

  <Accordion title="Does Vibely use my data to train AI models?">
    No. Vibely doesn't use your prompts, code, or project data to train models, on any plan. The optional **Allow data collection for training** setting in **Settings → Privacy & security** is off by default. See [Privacy & security](/features/workspace/privacy-security).
  </Accordion>

  <Accordion title="What is the refund policy?">
    Except where the law requires otherwise, fees are non-refundable, including subscriptions and credit purchases. Cancelling stops the next renewal; you keep access until the end of the period you paid for. The details are in the [Terms of Service](https://vibely.sh/terms-of-service).
  </Accordion>

  <Accordion title="Is Vibely compliant with security standards?">
    Vibely publishes a GDPR [Data Processing Agreement](https://vibely.sh/dpa) that applies without signature. Vibely doesn't hold SOC 2 or ISO 27001 today, and no audit is under way. See the [Security page](https://vibely.sh/security) and [Vibely for Enterprise](/introduction/enterprise).
  </Accordion>

  <Accordion title="How do I keep my app secure?">
    Run a security scan from the project's [Security view](/features/security/project-view) and fix findings from chat before you publish. See [Security best practices](/features/security/best-practices).
  </Accordion>
</AccordionGroup>

## How Vibely works

<AccordionGroup>
  <Accordion title="What tech stack does Vibely use?">
    * **Web projects**: Vite, React, TypeScript, Tailwind CSS, and shadcn/ui.
    * **Mobile projects**: Expo and React Native, with Expo Router.
    * **Backend**: your own Supabase project (Postgres, auth, storage, and edge functions).

    Each project builds and runs in its own cloud sandbox. See [Build engine](/reference/engine/overview).
  </Accordion>

  <Accordion title="How does Vibely remember context?">
    Vibely reads your project's code and chat history on every turn. For rules that should always apply, add them to project or workspace [Knowledge](/features/context/knowledge). For reusable playbooks, add [Skills](/features/context/skills).
  </Accordion>

  <Accordion title="Who owns the code Vibely creates?">
    You do. Under the [Terms of Service](https://vibely.sh/terms-of-service), you keep ownership of your prompts and of the code, designs, and projects Vibely generates for you. See [Code ownership](/features/deploy/ownership).
  </Accordion>
</AccordionGroup>


## Related topics

- [Add payments to your app](/features/grow/payments.md)
- [Optimize your app for SEO and AI search](/features/grow/seo.md)
- [Build from an existing website](/features/design/build-from-url.md)
- [Design guidance](/features/design/design-guidance.md)
- [Design systems](/features/design/design-systems.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.