Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vybe.build/llms.txt

Use this file to discover all available pages before exploring further.

Every deployed Vybe app gets a production URL based on your app name and organization. Your app can have multiple pages, API routes, and dynamic segments — all powered by the Next.js App Router.

​
Production URL

Your app is available at: 
https://<app-slug>-<org-slug>.vybe.build
ComponentSourceExample
App slugDerived from your app name”Sales Dashboard” becomes sales-dashboard
Org slugYour organization’s identifier”Acme Corp” becomes acme-corp
For example, an app called “Sales Dashboard” in the “Acme Corp” organization is deployed to: 
https://sales-dashboard-acme-corp.vybe.build

​
Multi-page routing

Your Vybe app can have as many pages as you need. The AI creates new pages using the Next.js App Router file convention, where each folder under src/app maps to a URL path.
File pathURL
src/app/page.tsx/
src/app/customers/page.tsx/customers
src/app/settings/page.tsx/settings
src/app/reports/monthly/page.tsx/reports/monthly
When you ask the AI to add a new page, it creates the file in the correct location and adds navigation links so your users can find it.
“Add a customers page with a searchable table showing all customers from our database.”

​
API routes

Your app can include server-side API routes that handle data fetching, form submissions, and other backend logic. API routes follow the same file-based routing pattern:
File pathURLMethod
src/app/api/data/route.ts/api/dataGET, POST, etc.
src/app/api/customers/route.ts/api/customersGET, POST, etc.
src/app/api/export/route.ts/api/exportGET, POST, etc.
API routes run on the server and have access to your database, integrations, and environment variables.

​
Dynamic routes

For pages that display a specific record — like a customer detail page or an order view — your app can use dynamic route segments:
File pathURL patternExample URL
src/app/customers/[id]/page.tsx/customers/:id/customers/42
src/app/orders/[orderId]/page.tsx/orders/:orderId/orders/abc-123
Dynamic routes let you build detail views, edit forms, and record-specific pages without creating a separate file for each record.
“Add a customer detail page that shows the full profile when I click on a customer in the table.”
When the AI creates new pages, it also wires up navigation so your users can move between them. Depending on your app’s layout, this may include:
  • A sidebar with links to each page
  • A top navigation bar
  • Breadcrumbs for nested pages
  • In-page links and buttons
You can ask the AI to change the navigation style at any time.
“Switch the sidebar navigation to a top nav bar with dropdown menus.”

​
Authentication and access control

All routes in your deployed app — pages and API routes — are protected by Vybe authentication. Only members of your organization who have been granted access to the app can view it. There is no public access by default. When someone visits your app URL without being authenticated, they are redirected to log in. This applies to every route in your app, including API endpoints.
If you need to share your app with someone outside your organization, you will need to invite them as a member first. See App Access for details on managing who can access your app.

​
What is next