Production URL
Your app is available at:| Component | Source | Example |
|---|---|---|
| App slug | Derived from your app name | ”Sales Dashboard” becomes sales-dashboard |
| Org slug | Your organization’s identifier | ”Acme Corp” becomes acme-corp |
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 undersrc/app maps to a URL path.
| File path | URL |
|---|---|
src/app/page.tsx | / |
src/app/customers/page.tsx | /customers |
src/app/settings/page.tsx | /settings |
src/app/reports/monthly/page.tsx | /reports/monthly |
“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 path | URL | Method |
|---|---|---|
src/app/api/data/route.ts | /api/data | GET, POST, etc. |
src/app/api/customers/route.ts | /api/customers | GET, POST, etc. |
src/app/api/export/route.ts | /api/export | GET, POST, etc. |
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 path | URL pattern | Example URL |
|---|---|---|
src/app/customers/[id]/page.tsx | /customers/:id | /customers/42 |
src/app/orders/[orderId]/page.tsx | /orders/:orderId | /orders/abc-123 |
“Add a customer detail page that shows the full profile when I click on a customer in the table.”
Navigation
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
“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
- Learn which environment variables are available in your deployed app: Environment Variables
- Understand how deployment works end to end: Deploying Your App