Before you start building, it helps to understand how Vybe is organized. This page covers the key concepts you will encounter throughout the platform.
Organization
An organization is your team’s workspace in Vybe. Everything you build — apps, integrations, connections, and members — belongs to an organization.
Each organization has:
- Its own set of apps and integrations
- A member list with role-based permissions (Owner, Admin, Editor, Member)
- Billing settings and credit balance
- A unique slug used in deployment URLs
You can belong to multiple organizations and switch between them from the sidebar. When you sign up, Vybe creates a personal organization for you automatically.
App
An app is a full-stack Next.js 15 web application. Each app is a complete project with its own:
- Codebase — Pages, components, API routes, and server-side logic
- Database — A dedicated PostgreSQL instance with its own tables and data
- Integrations — Connections to external services configured for this app
- Deployment — A production URL where your team can access the app
You create apps by describing what you need in a chat with the AI agent. The agent generates the entire application — frontend, backend, database schema, and integration wiring — based on your description.
Each app is independent. Changes to one app never affect another. You can safely experiment without worrying about breaking other tools your team relies on.
Thread
A thread is a conversation with the AI agent about a specific app. When you open an app in Vybe, you interact with it through threads.
Each app can have multiple threads. This is useful when you want to:
- Work on different features in parallel
- Keep a clean conversation history for a specific task
- Start fresh without losing previous context
Threads maintain full context about what you have discussed and changed. The AI agent remembers previous messages, code changes, and database modifications within a thread.
AI Agent
The AI agent is the core of Vybe. It is the assistant that builds and modifies your apps based on your instructions. The agent can:
- Create and edit files (pages, components, API routes, styles)
- Run database queries (create tables, insert data, run migrations)
- Install packages from the approved list
- Connect and configure integrations
- Debug errors and fix issues
- Explain how your app works
The agent operates in two modes:
| Mode | Description | Use when |
|---|
| Agent | Can read and modify your app’s code, database, and integrations | You want to build or change something |
| Ask | Read-only access. Can answer questions but cannot make changes | You want to understand something without modifying the app |
The AI agent works within the context of a single app. It has full access to that app’s code, database, and connected integrations, but cannot access other apps in your organization.
Sandbox
The sandbox is a live development environment where your app runs while you are building it. When the AI agent creates or modifies files, the sandbox compiles and runs the updated code automatically.
You can see your app running in real time through the Preview tab. Every change the agent makes — a new page, a styling update, a database query — is reflected in the preview within seconds.
The sandbox provides a full Node.js runtime with access to your app’s database and connected integrations. It behaves exactly like your deployed app, so what you see in preview is what your users will see in production.
Deployment
Deployment is the process of publishing your app so your team can use it. When you deploy, Vybe builds your app and makes it available at a production URL.
Deployed apps are accessible at:
https://<app-slug>-<org-slug>.vybe.build
chargeback-tracker-acme.vybe.build.
Key points about deployment:
- Only authenticated members of your organization can access deployed apps
- Each deployment creates a new version — you can roll back if needed
- Apps run on managed infrastructure with HTTPS and automatic scaling
- Environment variables and secrets are securely injected at deploy time
Integration
An integration is a connection to an external service. Once you connect an integration at the organization level, it becomes available across all apps in your workspace.
Vybe supports several types of integrations:
| Type | Examples |
|---|
| Services | Slack, Salesforce, Jira, Stripe, HubSpot, Google Workspace |
| Databases | PostgreSQL, MySQL, Amazon Redshift |
| Custom APIs | Any REST service with key or token authentication |
| Built-in | People Data Labs, CrustData, OpenAI (no setup required) |
Recipe
A recipe is a pre-configured app starter that combines a specific use case with guided setup steps. Recipes include:
- A description of the app being built
- Required integrations (the recipe prompts you to connect them before starting)
- A tailored prompt that generates a well-structured app
Recipes are useful when you want a head start on common use cases like building a CRM dashboard, a support ticket tracker, or a sales pipeline view.
Template
A template is a reusable app blueprint created from an existing app. When you save an app as a template, it captures the full codebase and database schema so you or your team can spin up copies.
Templates are useful when you want to:
- Create a standardized starting point for similar apps
- Share a proven app structure across your organization
- Let team members customize a base app for their specific needs
Credit
Credits are the unit of billing in Vybe. Each AI interaction — sending a message, generating code, running a query — consumes credits. The number of credits consumed depends on the AI model you use:
- More powerful models (like Claude Opus 4.5) cost more credits per interaction
- Lighter models (like Claude Haiku 4.5) cost fewer credits
- Non-AI actions like editing code manually or deploying do not consume credits
Your credit balance and usage are visible in your workspace settings. See Plans & Credits for details on plans and pricing.
How it all fits together
Here is how the core concepts relate to each other:
Organization
├── Members (Owner, Admin, Editor, Member)
├── Integrations (Slack, Stripe, databases, APIs...)
├── Billing & Credits
│
└── Apps
├── App: Chargeback Tracker
│ ├── Threads (conversations with the AI agent)
│ ├── Codebase (pages, components, API routes)
│ ├── Database (PostgreSQL tables and data)
│ ├── Connected Integrations (Stripe, Slack)
│ └── Deployment → chargeback-tracker-acme.vybe.build
│
└── App: Sales Dashboard
├── Threads
├── Codebase
├── Database
├── Connected Integrations (Salesforce, HubSpot)
└── Deployment → sales-dashboard-acme.vybe.build
