Understanding the vibe coding glossary is not about memorizing definitions. It is about removing the friction that slows you down when you are building. Every time you encounter a term you do not understand — in documentation, in an AI-generated code comment, in a tutorial — you lose momentum. You stop building and start searching. That context switch is the real cost of not knowing the vocabulary.
This glossary exists to give vibe coders a single reference for every technical term they will encounter. Whether you are using Cursor for the first time, deploying your first app to Vercel, or trying to understand why your AI assistant keeps suggesting a "middleware layer," the answer is here.
The definitions are written for the vibe coding audience specifically: people who are building software with AI assistance, who may not have a computer science degree, and who need practical understanding rather than academic precision. Each term includes what it is, why it matters to you as a vibe coder, and links to relevant tools or guides on alumi.space where applicable.
For a quick-reference version without the extended explanations, see the main glossary page.
Terms A–Z
Agent
An AI agent is software that can take a goal, plan a series of steps, execute those steps, and adjust based on results — all with minimal human intervention. Unlike a simple AI assistant that responds to one prompt at a time, an agent can read files, run commands, create code, test results, and iterate autonomously. Examples include Cursor Composer, Replit Agent, and Claude Code.
This matters because agents represent the next leap in vibe coding productivity. Instead of prompting step-by-step, you describe what you want and the agent builds it. See our full explainer: What is an AI Agent?
API
An Application Programming Interface is a set of rules that lets different software systems communicate with each other. When your app fetches weather data, processes a payment through Stripe, or sends an email via Resend, it is using an API. APIs define what requests you can make and what data you get back.
This matters because almost every feature in a modern app relies on APIs. Your AI coding tool will generate API calls constantly. Understanding what an API is helps you debug when things go wrong and choose the right services for your stack.
API Key
An API key is a unique string of characters that identifies your application when making API requests. It acts as a password for your app to access a service. API keys should never be exposed in client-side code or committed to public GitHub repositories. Store them in environment variables instead.
This matters because leaked API keys are one of the most common security mistakes in vibe-coded projects. If someone gets your Stripe API key, they can charge cards on your account. If they get your OpenAI key, they can run up your bill. Treat API keys like passwords.
App Builder
An app builder is a platform that lets you create complete applications by describing what you want in natural language. Tools like Lovable, Bolt.new, and v0 generate full-stack code, provide hosting, and handle deployment. They differ from AI coding assistants (like Cursor) in that you do not need to work in a code editor at all.
This matters because app builders are the most accessible entry point to vibe coding. If you have never written code, an app builder is where you start.
Authentication
Authentication is the process of verifying that a user is who they claim to be. This typically involves logging in with an email and password, a social account (Google, GitHub), or a magic link. Authentication answers the question "Who are you?" Services like Clerk, Supabase Auth, and Auth0 handle this for you.
This matters because every app with user accounts needs authentication. Building it yourself is risky. Using a service is faster and more secure. See our comparison: Clerk vs Supabase Auth vs Auth0.
Authorization
Authorization determines what an authenticated user is allowed to do. While authentication asks "Who are you?", authorization asks "What are you allowed to access?" For example, a regular user can view their own data, but only an admin can delete other users' accounts. Role-based access control (RBAC) is the most common authorization pattern.
This matters because forgetting authorization is a common security flaw. Your app might correctly verify who a user is but still let them access data or actions they should not have permission to use.
Backend
The backend is the server-side part of an application that users never see directly. It handles data storage, business logic, authentication, and API requests. The backend runs on a server (or serverless function) and communicates with the frontend through APIs. Common backend technologies include Node.js, Python, and Go.
This matters because many vibe-coded apps need a backend for user accounts, data storage, and API integrations. Tools like Supabase and Railway provide backend services without requiring you to manage servers.
CDN
A Content Delivery Network is a global network of servers that caches and delivers your app's static files (HTML, CSS, JavaScript, images) from locations geographically close to your users. Instead of loading from a single server in Virginia, your app loads from whichever CDN node is nearest to the visitor. All major hosting platforms (Vercel, Netlify, Cloudflare) include a CDN.
This matters because CDNs make your app faster for users everywhere in the world and reduce the load on your origin server. If you are using any modern hosting platform, you already have a CDN.
CI/CD
Continuous Integration / Continuous Deployment is the practice of automatically testing and deploying your code whenever you push changes to a Git repository. When you push to GitHub, a CI/CD pipeline can run your tests, build your app, and deploy it to production without any manual steps. Vercel, Netlify, and GitHub Actions all provide CI/CD.
This matters because CI/CD eliminates the tedious manual deployment process. With proper CI/CD, shipping an update is as simple as pushing code to GitHub.
CLI
A Command Line Interface is a text-based way to interact with software by typing commands. Instead of clicking buttons in a graphical interface, you type commands like npm install or git push in a terminal window. Many developer tools are CLI-first, meaning the command line is the primary way to use them.
This matters because vibe coding often involves the terminal, even if you primarily work in a graphical editor. Knowing basic CLI commands helps you follow tutorials, troubleshoot deployment issues, and use tools that only have a CLI interface.
Component
A component is a reusable, self-contained piece of user interface. In React, a button, a navigation bar, a form, and a card are all components. Components accept data (called "props") and render UI based on that data. Building apps with components is like building with LEGO: small pieces combine into complex structures.
This matters because AI coding tools generate components constantly. Understanding the concept helps you communicate with your AI assistant ("Create a PricingCard component that accepts a plan name, price, and feature list").
Context Window
The context window is the maximum amount of text an LLM can consider at one time. It is measured in tokens and varies by model — from 8K tokens to over 1 million. Everything in the context window (your prompt, the conversation history, any code files provided) counts toward this limit. When the context window fills up, the AI starts "forgetting" earlier information.
This matters because context window limits affect how much of your codebase an AI tool can understand at once. A larger context window means the AI can reason about more files simultaneously, producing more coherent changes across your project.
CORS
Cross-Origin Resource Sharing is a browser security mechanism that controls which websites can make requests to your API. If your frontend is on app.example.com and your API is on api.example.com, the browser blocks the request by default. CORS headers tell the browser which origins are allowed to access your API.
This matters because CORS errors are one of the most common issues vibe coders encounter. Your app works locally but fails when deployed because the browser blocks cross-origin requests. Understanding CORS helps you fix these errors quickly instead of spending hours confused.
Cron Job
A cron job is a scheduled task that runs automatically at specified intervals. Named after the Unix cron utility, cron jobs handle recurring work: sending daily email digests, cleaning up expired sessions, generating weekly reports, or syncing data with external services. Services like Trigger.dev and Inngest make cron jobs easy for vibe coders.
This matters because many app features require background work that runs on a schedule. Without cron jobs, you would have to trigger these tasks manually or hope a user's visit triggers them.
Database
A database is a system for storing, organizing, and retrieving data. When your app saves user profiles, stores blog posts, or records transactions, it writes to a database. The most common type for vibe-coded apps is a relational database like PostgreSQL, which organizes data into tables with rows and columns. Supabase, PlanetScale, and Neon all provide managed databases.
This matters because almost every app beyond a static website needs a database. Choosing the right database service affects your app's performance, cost, and how easily you can query your data.
Deploy
Deploying is the process of making your application available on the internet. It involves uploading your code to a server, building it into a runnable format, and configuring it to respond to web requests. Modern platforms like Vercel and Netlify automate deployment: you push code to GitHub, and the platform handles the rest.
This matters because deployment is the step that turns your local project into a live product. See our guide: Ship It.
DNS
The Domain Name System translates human-readable domain names (like alumi.space) into IP addresses (like 104.26.10.78) that computers use to find each other on the internet. When you buy a domain and point it to your hosting provider, you are configuring DNS records. Cloudflare, Namecheap, and your domain registrar all provide DNS management.
This matters because setting up a custom domain requires configuring DNS. The process is straightforward but unfamiliar to most first-time builders. A misconfigured DNS record means your domain shows an error page instead of your app.
Edge Function
An edge function is a small piece of server-side code that runs at CDN locations worldwide, close to the user making the request. Unlike traditional serverless functions that run in a single region, edge functions execute at the nearest network edge, resulting in lower latency. Vercel Edge Functions, Cloudflare Workers, and Supabase Edge Functions are popular options.
This matters because edge functions let you add server-side logic (authentication checks, A/B testing, redirects) without the latency of a centralized server. They are especially useful for globally distributed apps.
Environment Variable
An environment variable is a configuration value stored outside your code that changes depending on where your app is running. Database connection strings, API keys, and feature flags are typically stored as environment variables. Locally, they live in a .env file. In production, your hosting platform provides a secure way to set them.
This matters because environment variables keep secrets out of your code. If you hardcode an API key in your source code and push it to GitHub, anyone can see it. Environment variables solve this problem.
Fine-Tuning
Fine-tuning is the process of training an existing LLM on additional, specialized data to improve its performance on specific tasks. Instead of training a model from scratch (which costs millions of dollars), fine-tuning adjusts an existing model's behavior using a smaller dataset. For example, you might fine-tune a model on your company's coding standards so it generates code in your preferred style.
This matters because fine-tuning is how AI coding tools are adapted for specific use cases. Most vibe coders will not fine-tune models themselves, but understanding the concept helps you evaluate tools that claim to be "fine-tuned for coding."
Framework
A framework is a pre-built structure that provides conventions, tools, and patterns for building applications. Instead of starting from a blank file, you start with a framework that handles routing, project structure, build configuration, and common patterns. Next.js, Remix, SvelteKit, and Nuxt are popular frameworks for web applications.
This matters because AI coding tools work best with popular frameworks. When you tell Cursor to "build a dashboard," it will likely generate Next.js or React code because these frameworks have the most training data. Choosing a well-supported framework makes your AI tools more effective.
Frontend
The frontend is the part of an application that users see and interact with in their browser. It includes the HTML structure, CSS styling, and JavaScript behavior of your user interface. The frontend communicates with the backend through APIs to fetch and display data. React, Vue, and Svelte are popular frontend libraries.
This matters because most vibe-coded projects are frontend-heavy. AI tools excel at generating frontend code: layouts, forms, interactive elements, and visual components.
Git / GitHub
Git is a version control system that tracks changes to your code over time. GitHub is a platform that hosts Git repositories online and adds collaboration features (pull requests, issues, actions). Git lets you save snapshots of your code (commits), create parallel versions (branches), and undo changes. Every professional development workflow uses Git.
This matters because Git is your safety net when working with AI tools. Before letting an agent modify your codebase, commit your current state. If the agent produces unwanted changes, you can revert to the previous commit. Git is non-negotiable for vibe coding.
Headless CMS
A headless Content Management System stores and manages content (blog posts, product descriptions, pages) but does not include a frontend to display it. Instead, it provides an API that your app fetches content from. Tools like Sanity, Contentful, and Strapi are headless CMSs. The "headless" part means the content and presentation are separate.
This matters because a headless CMS lets non-technical team members update content without touching code. If your app has a blog, documentation, or any content that changes frequently, a headless CMS is the right tool.
Hosting
Hosting is the service that runs your application and makes it accessible on the internet. Your code needs to run on a computer (server) that is always online and connected to the internet. Hosting providers like Vercel, Netlify, Cloudflare Pages, and Railway provide these servers along with tools for deployment, monitoring, and scaling.
This matters because without hosting, your app only runs on your computer. Choosing the right hosting platform affects your app's performance, cost, and reliability. See our guide: Best Free Hosting for Vibe Coders.
IDE
An Integrated Development Environment is a software application that provides tools for writing, testing, and debugging code in one place. VS Code, Cursor, and Windsurf are IDEs. A modern IDE includes a code editor, file browser, terminal, debugger, and extensions. AI-native IDEs like Cursor add AI assistance directly into the editing experience.
This matters because your IDE is where you spend most of your time as a vibe coder. Choosing an IDE with strong AI integration dramatically affects your productivity.
JSX
JSX is a syntax extension for JavaScript that lets you write HTML-like code inside JavaScript files. It is used by React and Next.js. Instead of separating HTML and JavaScript into different files, JSX combines them: <button onClick={handleClick}>Submit</button>. JSX is not valid JavaScript on its own — it is compiled into regular JavaScript function calls during the build step.
This matters because JSX is everywhere in vibe-coded projects. Your AI tools will generate JSX constantly. Recognizing it helps you read and modify the code your AI assistant produces.
LLM
A Large Language Model is an AI system trained on vast amounts of text data that can generate, understand, and reason about human language and code. GPT-4, Claude, Gemini, and Llama are all LLMs. They power every AI coding tool, app builder, and chatbot in the vibe coding ecosystem. LLMs predict the most likely next text based on patterns learned during training.
This matters because LLMs are the engine behind everything in vibe coding. Understanding their capabilities and limitations (they predict plausible text, they do not truly "understand" code) helps you use them more effectively and catch their mistakes.
Local AI
Local AI refers to running LLM models on your own computer instead of using cloud-based APIs. Tools like Ollama, LM Studio, and Jan let you download open-source models (Llama, Mistral, CodeLlama) and run them locally. Local AI offers privacy (your code never leaves your machine), works offline, and has no per-token costs.
This matters because local AI eliminates API costs and privacy concerns. The trade-off is that local models are generally less capable than cloud-based models like GPT-4 or Claude, and they require a powerful computer (16+ GB RAM, ideally a dedicated GPU).
MAU
Monthly Active Users is a metric that counts the number of unique users who interact with your app at least once during a calendar month. Many services, especially authentication providers, use MAU as their pricing unit. One user logging in 100 times counts as 1 MAU.
This matters because MAU-based pricing determines when you will start paying for services. See our comparison: Clerk vs Supabase Auth vs Auth0 for how MAU pricing works in practice.
MCP
Model Context Protocol is an open standard (developed by Anthropic) that allows AI models to connect to external data sources and tools through a standardized interface. MCP enables AI assistants to access databases, APIs, file systems, and other services in a consistent way. Think of it as a universal adapter that lets AI tools plug into your existing infrastructure.
This matters because MCP is expanding what AI coding tools can do. Instead of just generating code, an AI assistant with MCP can query your database, read your documentation, or interact with your project management tool directly.
Merchant of Record
A Merchant of Record (MoR) is a company that handles the legal and financial responsibility of processing payments on your behalf. Services like Lemon Squeezy and Paddle act as your MoR, handling sales tax calculation, VAT compliance, invoicing, and refunds. Without an MoR, you are responsible for tax compliance in every jurisdiction where you have customers.
This matters because selling software globally creates complex tax obligations. An MoR handles all of this for a percentage of each sale, saving you from becoming a tax compliance expert. It is the simplest path to selling software internationally.
Middleware
Middleware is code that runs between a request arriving at your server and the response being sent back. It intercepts requests to perform tasks like checking authentication, logging, rate limiting, or modifying headers. In Next.js, middleware runs at the edge before your page loads, making it useful for auth checks and redirects.
This matters because middleware is where you enforce security rules, handle redirects, and add cross-cutting functionality. Your AI coding tool will often suggest middleware when you ask about protecting routes or adding authentication.
MRR
Monthly Recurring Revenue is the predictable income your SaaS generates each month from active subscriptions. If you have 10 customers paying $29/month, your MRR is $290. MRR is the single most important metric for subscription-based businesses and is used to measure growth, forecast revenue, and determine company value.
This matters because MRR is the scoreboard for SaaS businesses. It tells you whether your product is growing, stagnating, or shrinking. Many vibe coders build SaaS products, and understanding MRR helps you set goals and measure progress.
MVP
A Minimum Viable Product is the simplest version of your product that delivers enough value to attract early users and validate your idea. An MVP is not a prototype or a demo — it is a real product that real people can use, just with a deliberately limited feature set. The point is to test your hypothesis with the least investment of time and money.
This matters because vibe coding makes MVPs faster and cheaper to build than ever before. See our cost guide: How Much Does Vibe Coding Cost?
Next.js
Next.js is a React-based framework for building full-stack web applications. It adds server-side rendering, routing, API routes, and optimized build tooling on top of React. Created by Vercel, Next.js is the most popular framework in the vibe coding ecosystem because AI tools have extensive training data for it and Vercel provides seamless deployment.
This matters because if you ask an AI to build a web app, there is a strong chance it will generate a Next.js project. Understanding Next.js basics (pages, layouts, API routes) helps you work with AI-generated code more effectively.
No-Code
No-code refers to platforms that let you build applications through visual interfaces (drag-and-drop, form builders, workflow editors) without writing any code. Bubble, Webflow, and Airtable are no-code tools. No-code differs from vibe coding in that vibe coding produces real, exportable code, while most no-code platforms lock you into their proprietary systems.
This matters because no-code and vibe coding are often confused. The key difference: vibe-coded apps produce standard code you can host anywhere and modify freely. No-code apps typically cannot be exported or self-hosted.
ORM
An Object-Relational Mapping is a library that lets you interact with your database using your programming language instead of writing raw SQL queries. Prisma and Drizzle are popular ORMs in the JavaScript/TypeScript ecosystem. Instead of writing SELECT * FROM users WHERE id = 1, you write db.user.findUnique({ where: { id: 1 } }).
This matters because AI tools often generate code using ORMs. If your AI suggests Prisma or Drizzle, it is creating a database interaction layer that is easier to read and maintain than raw SQL. Understanding what an ORM does helps you evaluate whether the AI's database code is correct.
PostgreSQL
PostgreSQL (often called Postgres) is a powerful, open-source relational database. It is the default database for most vibe-coded applications because it is free, well-documented, and supported by every major hosting platform. Supabase, Neon, and Railway all use PostgreSQL under the hood. It stores data in tables with rows and columns and supports complex queries, JSON data, and full-text search.
This matters because PostgreSQL is the database you will encounter most often. When your AI tool generates database code or suggests a database service, it is almost certainly talking about PostgreSQL.
Prompt
A prompt is the text input you provide to an LLM to get a response. In vibe coding, prompts range from simple ("fix this bug") to complex ("build a dashboard with user authentication, a data table with sorting and filtering, and a chart showing monthly revenue"). The quality of your prompt directly affects the quality of the AI's output. See our guide: Write Better Prompts.
This matters because prompting is the core skill of vibe coding. Better prompts produce better code with fewer iterations. Learning to write clear, specific, context-rich prompts is the highest-leverage skill a vibe coder can develop.
RAG
Retrieval-Augmented Generation is a technique that enhances an LLM's responses by fetching relevant information from external sources before generating an answer. Instead of relying solely on training data, a RAG system searches a knowledge base (documentation, databases, files) and includes the results in the prompt. This makes responses more accurate and up-to-date.
This matters because RAG is how AI coding tools "know" about your codebase. When Cursor reads your project files to generate contextually appropriate code, it is using a form of RAG. Understanding RAG helps you appreciate why providing context to your AI tools produces better results.
React
React is a JavaScript library for building user interfaces, created by Meta (Facebook). It introduced the concept of components as the building blocks of UI and uses a virtual DOM to efficiently update the browser. React is the most popular frontend library in the world and the foundation for Next.js. Nearly every AI coding tool has extensive React training data.
This matters because React is the default language of vibe coding. When AI tools generate frontend code, it is almost always React or React-based (Next.js). Understanding React's component model helps you read, modify, and debug AI-generated code.
REST API
A REST (Representational State Transfer) API is a web API that follows a specific set of conventions. It uses HTTP methods (GET to read, POST to create, PUT to update, DELETE to remove) and organizes resources by URL paths (/api/users, /api/posts/123). REST is the most common API style for web applications.
This matters because your vibe-coded app's backend likely exposes a REST API, and your frontend consumes it. Understanding REST helps you debug API issues ("Why am I getting a 404?") and communicate with your AI tool about API design.
RLS
Row Level Security is a PostgreSQL feature that restricts which rows a user can access in a database table. Instead of checking permissions in your application code, RLS enforces access rules at the database level. Supabase relies heavily on RLS to secure data. For example, an RLS policy can ensure users can only read their own rows, even if your application code has a bug.
This matters because RLS is Supabase's primary security mechanism. If you use Supabase, understanding RLS is essential. Misconfigured RLS policies can expose private data or block legitimate access. Your AI tool can generate RLS policies, but always review them carefully.
SaaS
Software as a Service is a business model where users pay a recurring subscription to access software over the internet. Instead of buying software once and installing it, customers pay monthly or annually for access. Gmail, Slack, Notion, and most modern software products are SaaS. SaaS revenue is measured in MRR.
This matters because SaaS is the most common business model for vibe-coded products. The combination of AI coding tools and modern infrastructure makes it possible for a single person to build and run a SaaS business that would have required a team of five just a few years ago.
SDK
A Software Development Kit is a collection of tools, libraries, and documentation that makes it easier to build with a specific platform or service. When Stripe provides a JavaScript SDK, it includes pre-built functions for creating charges, managing subscriptions, and handling webhooks. SDKs save you from writing raw API requests and handle edge cases the platform has already solved.
This matters because SDKs are how you integrate third-party services into your app. Your AI coding tool will import and use SDKs when you ask it to add payments, auth, email, or other features. A good SDK makes integration a few lines of code instead of hundreds.
Serverless
Serverless computing is a model where you write functions that run on-demand without managing servers. You do not provision, configure, or maintain any infrastructure. The platform (AWS Lambda, Vercel Functions, Cloudflare Workers) handles scaling automatically: your function runs when called and you pay only for execution time. "Serverless" does not mean there are no servers — it means you do not manage them.
This matters because serverless is how most vibe-coded apps run their backend logic. API routes in Next.js on Vercel are serverless functions. Understanding serverless helps you grasp why your functions have cold starts, timeout limits, and memory constraints.
SSR
Server-Side Rendering is the process of generating HTML on the server for each request, then sending the complete HTML to the browser. This differs from client-side rendering (where the browser receives a blank page and JavaScript builds the content). SSR improves initial load time and is better for SEO because search engines can read the fully rendered HTML. Next.js supports SSR natively.
This matters because SSR affects your app's performance and search engine visibility. If your vibe-coded app needs to rank on Google, SSR (or static generation) is important. Your AI tool will sometimes suggest SSR for pages that need SEO.
SSL/TLS
Secure Sockets Layer / Transport Layer Security is the encryption protocol that secures data transmitted between a user's browser and your server. When your URL starts with https:// instead of http://, SSL/TLS is active. It prevents eavesdropping, tampering, and impersonation. In 2026, SSL/TLS certificates are free (via Let's Encrypt) and automatically configured by all major hosting platforms.
This matters because HTTPS is mandatory for modern web apps. Browsers mark HTTP sites as "Not Secure," and many APIs refuse to communicate over insecure connections. Fortunately, your hosting platform handles this automatically, so you rarely need to think about it.
Supabase
Supabase is an open-source backend-as-a-service platform that provides a PostgreSQL database, authentication, file storage, edge functions, and real-time subscriptions in a single package. Often described as "the open-source Firebase alternative," Supabase is the most popular backend choice in the vibe coding ecosystem because of its generous free tier and tight integration with modern frameworks.
This matters because Supabase is likely the first backend service you will use as a vibe coder. It gives you everything you need to build a full-stack app without managing infrastructure.
Tailwind CSS
Tailwind CSS is a utility-first CSS framework that lets you style elements by applying pre-defined classes directly in your HTML or JSX. Instead of writing custom CSS (color: blue; font-size: 1.5rem;), you add classes (text-blue-500 text-2xl). Tailwind is the dominant styling approach in the vibe coding ecosystem because AI tools generate Tailwind code extremely well.
This matters because Tailwind is what your AI coding tool will use for styling by default. Understanding Tailwind's class naming convention (p-4 for padding, bg-white for background, rounded-lg for border radius) helps you read and tweak AI-generated styles.
Token
In the context of LLMs, a token is a unit of text that the model processes. A token is roughly 3-4 characters or about 0.75 words. The sentence "Hello, how are you?" is about 6 tokens. Token counts determine both the context window limit (how much text the model can consider) and API pricing (you pay per token processed). Input tokens (your prompt) and output tokens (the AI's response) are often priced differently.
This matters because tokens directly affect your costs and the quality of AI responses. Understanding token limits helps you write more efficient prompts and estimate API costs for AI-powered features in your app.
TypeScript
TypeScript is a superset of JavaScript that adds static type checking. It lets you define what type of data a variable, function parameter, or return value should be (string, number, User[]). TypeScript catches errors at build time rather than at runtime, making code more reliable. AI coding tools generate TypeScript by default in most modern projects.
This matters because TypeScript is the standard language for vibe-coded applications. Your AI assistant generates TypeScript, and the type system helps it produce more accurate code. When you see .ts or .tsx files, you are looking at TypeScript.
Vibe Coding
Vibe coding is the practice of building software by describing what you want to an AI tool and collaborating with it to produce working code. The term was coined by Andrej Karpathy in February 2025. Rather than writing code manually, vibe coders use natural language prompts, AI coding assistants, and app builders to create applications. The "vibe" refers to the intuitive, conversational nature of the process. Learn more: What is Vibe Coding?
This matters because it is the foundation of everything on this site. Vibe coding is democratizing software creation, letting people without traditional programming backgrounds build real, functional applications.
Webhook
A webhook is a way for one service to send real-time data to another when an event occurs. Instead of your app polling an API repeatedly ("Did anything happen yet?"), the service pushes data to your app when something happens. For example, Stripe sends a webhook to your server when a payment succeeds, and your app updates the user's subscription status in response.
This matters because webhooks connect your app to external services. Payment confirmations, email delivery notifications, GitHub push events, and auth status changes all come through webhooks. Understanding webhooks helps you build responsive, event-driven features.
WebSocket
A WebSocket is a communication protocol that enables persistent, two-way communication between a browser and a server. Unlike HTTP (where the browser sends a request and waits for a response), WebSocket connections stay open, allowing the server to push updates to the browser instantly. Chat apps, live dashboards, collaborative editors, and real-time notifications use WebSockets. Supabase Realtime uses WebSockets.
This matters because WebSockets enable real-time features. If your app needs live updates (new messages appearing without page refresh, live collaboration, real-time data feeds), WebSockets are the underlying technology that makes it possible.
This glossary is a living document. As new tools, concepts, and patterns emerge in the vibe coding ecosystem, we add them here. For the quick-reference version, see the main glossary page. If you think a term is missing, let us know.