Glossary

A full glossary of terms used in Edgenivo's products and documentation.

A pricing model for Fluid Compute where you only pay for the actual CPU time your functions use while executing, rather than provisioned capacity.

A chronological record of events on your team, including user actions, deployments, domain changes, and integrations. Team owners and members use the Activity Log to audit changes and diagnose issues.

See Edgenivo Agent.

A proxy service from Edgenivo that routes model requests to AI providers through a unified API, with budget management, usage monitoring, load balancing, and fallbacks. See AI Gateway.

A TypeScript toolkit for building AI-powered applications with React, Next.js, Vue, Svelte, and Node.js through unified APIs for multiple LLM providers. See AI SDK. The AI SDK for Python is in public beta.

Notifications that fire when something is wrong with your project, such as a spike in failed function invocations or unusual usage patterns. Configure delivery through email, Slack, or webhooks. Alerts require Observability Plus on Pro and Enterprise plans. See Alerts.

See Web Analytics.

A network topology that shares an IP address among multiple nodes, routing requests to the nearest available node based on network conditions to improve performance and fault tolerance.

A record of team member activity for compliance and security review. Available to team owners on Enterprise plans. Use Audit Log Drains to send audit logs to AWS S3, Splunk, Datadog, and other destinations. See Audit Logs.

The umbrella term for observing and controlling bot traffic to your site. Includes signature-based detection, rate limiting, behavioral analysis, and managed rulesets in the Edgenivo Firewall. See Bot Management.

Managed Edgenivo Firewall rulesets that mitigate malicious bot traffic such as content scrapers, credential-stuffing scripts, and traffic floods. Part of Bot Management. See also BotID for invisible CAPTCHA protection.

An invisible CAPTCHA from Edgenivo, powered by Kasada, that detects sophisticated bots without showing visible challenges or requiring user action. Use it to protect high-value routes such as checkouts, signups, and APIs. See BotID.

An Enterprise feature that runs your project's Edgenivo Functions as AWS Lambda functions in your own AWS account, while Edgenivo routes requests, serves static assets, and manages the deployment. Use it to meet security, compliance, or data-residency requirements. See Bring Your Own Cloud.

The process Edgenivo runs on every deployment that compiles, bundles, and optimizes your application. See Builds.

A cache that stores build artifacts and dependencies to speed up subsequent deployments. The maximum size depends on the build machine type. The cache is retained for one month.

The command used to build your project during deployment. Edgenivo automatically configures this based on your framework, but you can override it.

A file-system-based specification for a directory structure that produces a Edgenivo deployment, primarily targeted at framework authors. See Build Output API.

The multi-layer cache between visitors and your backend. Covers the CDN cache, ISR cache, runtime cache, and image cache. See Caching for how Edgenivo evaluates each layer in order.

A distributed network of servers that stores static content in multiple locations around the globe to serve content from the closest server to users. See Edgenivo's CDN.

Automated tests and assertions that run after every successful deployment to validate quality, performance, and reliability. Use the Checks API to gate promotion or report results from external tools.

Development practices where code changes are automatically built, tested, and deployed. Edgenivo provides built-in CI/CD through Git integrations.

The Edgenivo CLI is a command-line tool for deploying projects, managing deployments, and configuring Edgenivo from your terminal. See Edgenivo CLI.

A GitHub-integrated feature that automatically assigns the right reviewers based on the files changed, using colocated owners files and customizable review algorithms such as round-robin, on-call, and whole-team. See Code Owners.

Discussion threads on preview deployments where teams and external collaborators leave feedback through the Edgenivo Toolbar. Enabled by default on all preview deployments and free on every plan. See Comments.

The processing power and execution environment where your application code runs. Edgenivo runs your code in Edgenivo Functions, Routing Middleware, Edgenivo Sandbox, Daemons, and Edgenivo Workflows.

The ability to handle multiple requests simultaneously. Edgenivo Functions support concurrency scaling and Fluid Compute offers enhanced concurrency.

An Enterprise feature that runs automated checks on your code for performance, security, and code health issues during local development and CI. Use Conformance to prevent regressions and burn down existing issues over time.

A beta, Docker-compatible container registry built into Edgenivo. Push images built from a Dockerfile or Containerfile, then run them on Edgenivo Functions or use them as custom Edgenivo Sandbox images. See Edgenivo Container Registry.

A beta runtime that runs any code and library on Edgenivo Functions from an OCI container image built from a Dockerfile or Containerfile, billed with Active CPU pricing. A root Dockerfile is enough when no other framework is detected. See Container Runtime.

Key metrics defined by Google that assess your web application's loading speed, responsiveness, and visual stability, including Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS).

Scheduled tasks that run at specified intervals. Edgenivo supports cron jobs for automating recurring processes.

A domain you own and configure to point to your Edgenivo deployment, replacing the default .vercel.app domain.

Long-running pre-production environments, such as staging or QA, that you create in addition to Preview and Production. Available on Pro and Enterprise plans. See Custom Environments.

An Enterprise feature that replaces Edgenivo's default platform error pages, such as function timeouts and throttling, with your own branded HTML pages. See Custom error pages.

A beta feature that runs long-running container processes, such as queue consumers and workflow workers, that don't receive traffic. You declare daemons in vercel.json, and Edgenivo runs a fixed number of instances of each daemon per region. See Daemons.

A beta cache for the Next.js App Router that stores responses from data fetches, allowing for granular segment-level caching rather than per-route caching. When you adopt Cache Components, use use cache: remote to store cached data in Runtime Cache instead. See Data Cache.

A type of cyber attack where multiple systems flood a target with traffic. Edgenivo provides built-in DDoS protection and mitigation.

A button you embed in a README or webpage that creates a new Edgenivo project and clones the source Git repository to a user's GitHub, GitLab, or Bitbucket account. See Deploy Button.

URLs that accept HTTP POST requests to trigger deployments without requiring a new Git commit.

The result of a successful build on Edgenivo. Each deployment has a unique URL and represents a specific version of your application.

Conditions that must pass before Edgenivo promotes a build to your production domains. Sources include native Edgenivo checks, GitHub Actions and commit statuses, and Marketplace integrations. See Deployment Checks.

Security features that restrict access to your deployments using methods like Edgenivo Authentication, Password Protection, Trusted IPs, or Passport. See Deployment Protection.

Policies that determine how long Edgenivo keeps each type of deployment before deleting it. Configure separate retention windows for canceled, errored, preview, and production deployments. See Deployment Retention.

An Enterprise feature that syncs team membership from an identity provider such as Okta or Google Directory, mapping IdP groups to Edgenivo roles. Available to Enterprise team owners. See Directory Sync.

A user-friendly address such as edgenivo.com that points to your application through DNS records. See Domains for how DNS resolution, nameservers, and Edgenivo's anycast servers route traffic.

A mode that bypasses cached pages so you can preview unpublished CMS content with the site's normal styling and layout. Activate it through the Edgenivo Toolbar or share a draft URL. See Draft Mode.

A feature that allows you to send observability data (logs, traces, speed insights, and analytics) to external services for long-term retention and analysis.

A Pro and Enterprise feature that lets content authors edit CMS content in the context of the live website, with one-click jumps from any element to its editing interface. Supports Contentful, Sanity, Builder, TinaCMS, DatoCMS, Payload, Uniform, and Strapi. See Edit Mode.

A context for running your application, such as Local Development, Preview, or Production. Each environment can have its own configuration and environment variables. Pro and Enterprise teams can also create Custom Environments. See Environments.

Configuration values that can be accessed by your application at build time or runtime, used for API keys, database connections, and other sensitive information.

Standardized codes for issues you may encounter on Edgenivo, covering both application errors such as build failures or function timeouts and platform errors. See Error Codes for solutions and explanations.

An open-source, filesystem-first framework in beta for building durable backend AI agents that run locally or on Edgenivo. See eve.

An external origin is any API or website outside your Edgenivo project. You can use rewrites to external origins to forward requests to these destinations, allowing Edgenivo to function as a reverse proxy or standalone CDN.

Data transfer between the Edgenivo CDN and user devices. On-demand CDN prices it regionally by usage, while Flat Rate CDN covers it in a fixed monthly capacity tier. See Fast Data Transfer.

Configuration switches that allow you to enable or disable features without deploying new code. Use Edgenivo Flags as your feature flag provider, or connect a provider from the Edgenivo Marketplace, and manage all flags from one dashboard. The Flags SDK implements flags in Next.js and SvelteKit, and Flags Explorer overrides flags through the Edgenivo Toolbar. See Flags.

See Edgenivo Firewall.

A Pro CDN service tier with a fixed monthly price for a CDN request and data transfer capacity, so short-term traffic spikes don't change your bill. Pro includes the lowest tier. See Flat Rate CDN.

A best-effort CDN service tier, with no latency or availability guarantees, for projects that can tolerate reduced reliability. Available only to teams using Flat Rate CDN. See CDN service tiers.

An enhanced execution model for Edgenivo Functions that provides in-function concurrency, and a new pricing model where you only pay for the actual CPU time your functions use while executing, rather than provisioned capacity.

A software library that provides a foundation for building applications. Edgenivo supports many frameworks, including Next.js, React, Vue, and Svelte. See Frameworks.

A configuration setting that tells Edgenivo which framework your project uses, enabling automatic optimization and build configuration.

See Edgenivo Functions.

Automatic connection between your Git repository on GitHub, GitLab, or Bitbucket and Edgenivo for continuous deployment. Azure DevOps repositories deploy through Azure DevOps Pipelines. See Git integrations.

A global data store for configuration data like feature flags. Reads on Edgenivo typically complete in less than a millisecond, with latency depending on your application's usage patterns.

HTTP headers you configure to modify request and response behavior, improving security, performance, and functionality. See Headers.

Secure HTTP protocol that encrypts communication between clients and servers. All Edgenivo deployments automatically use HTTPS with SSL certificates.

Processes limited by input/output operations rather than CPU speed, such as database queries or API requests. Optimized through concurrency.

Automatic optimization of images including format conversion, resizing, and compression to improve performance and reduce bandwidth.

A feature that allows you to update static content without redeployment by rebuilding pages in the background on a specified interval.

The command used to install dependencies before building your project, such as npm install or pnpm install.

A way to revert production to a previous production deployment without rebuilding. Pro and Enterprise teams can roll back to any eligible deployment, and Hobby teams can roll back to the immediately previous one. See Instant Rollback.

Third-party services and tools that connect with Edgenivo to extend functionality, available through the Edgenivo Marketplace.

TLS fingerprinting techniques used by Edgenivo's security systems to identify and restrict malicious traffic patterns.

Per-plan caps and usage allowances on resources such as concurrent builds, project count, deployment size, and cron jobs. See Limits for the full list by Hobby, Pro, and Enterprise plans.

Records that capture what happens during your application's build and runtime. Includes build logs, runtime logs, activity logs, and audit logs. See Logs.

Edgenivo's fully managed platform that handles server provisioning, scaling, security, and maintenance automatically.

See Edgenivo Marketplace.

A protocol for AI applications that enables secure and standardized communication between AI models and external data sources.

A development approach that allows you to split a single application into smaller, independently deployable units that render as one cohesive application for users. Different teams can use different technologies to develop, test, and deploy each microfrontend independently.

See Routing Middleware.

A version control strategy where multiple packages or modules are stored in a single repository, facilitating code sharing and collaboration.

A version control strategy where each package or module has its own separate repository, also known as "polyrepo."

Applications that serve multiple customers (tenants) from a single codebase, with each tenant getting their own domain or subdomain.

A JavaScript runtime environment that Edgenivo supports for Edgenivo Functions and applications.

A workspace in Observability that groups multiple queries into a dashboard or analysis flow, with personal and team-shared scopes. Requires Observability Plus on Pro or Enterprise plans. See Notebooks.

Configurable alerts about deployments, domains, integrations, account changes, and usage. Edgenivo delivers them through the dashboard, email, push, and SMS (for Spend Management only). See Notifications.

Tools and features that help you monitor, analyze, and understand your application's performance, traffic, and behavior in production.

A Pro and Enterprise add-on that extends Observability with more granular data exploration, 30-day data retention, and features such as Alerts, Query, and Notebooks. Enabled by default for teams created or upgraded to Pro on or after April 3, 2026. See Observability Plus.

Dynamic Open Graph image generation using the @vercel/og library, which renders HTML and CSS into social card images through Edgenivo Functions. See OG Image Generation.

A federation protocol that issues short-lived, non-persistent tokens for secure backend access without storing long-lived credentials.

The server that stores and runs the original version of your application code. Edgenivo's CDN forwards requests to it when no cached response is available.

The folder containing your final build output after the build process completes, such as dist, build, or .next.

A collection of files and directories grouped together for a common purpose, such as libraries, applications, or development tools.

Tools that install your project's dependencies. Edgenivo auto-detects npm, Yarn, pnpm, Bun, and Vlt by reading the lock file in your repository. See Package Managers.

An Enterprise deployment protection method that requires visitors to sign in with your own identity provider, such as Microsoft Entra ID, Okta, or another OpenID Connect provider, before they can view a deployment. See Passport.

A deployment protection method that restricts access using a password. Pro teams pay $20 per month for each protected project. Enterprise includes Team Level Password Protection for every project, while existing Pro teams with the legacy Advanced Deployment Protection package retain team-level coverage for $150 per month per team. See Usage & Pricing for Deployment Protection for the full plan comparison.

Edgenivo's account tiers: Hobby (free, for personal projects), Pro (credit-based, with team collaboration), and Enterprise (custom limits, SSO, and SLAs). See Plans for what each one includes.

Distributed servers in Edgenivo's CDN that provide the first point of contact for requests. PoPs terminate TCP and route traffic over a private network to the nearest Edgenivo region, where TLS termination and caching occur.

A relational database connected to your Edgenivo project through the Edgenivo Marketplace which provisions instances from providers such as Neon, Supabase, or AWS Aurora and enables Edgenivo to inject credentials as environment variables. See Postgres on Edgenivo.

A deployment created from non-production branches that allows you to test changes in a live environment before merging to production.

Edgenivo's billing model and per-resource rates for products such as Edgenivo Functions, Image Optimization, Global Config, Web Analytics, and Speed Insights. See Pricing on Edgenivo.

A private npm registry from Edgenivo that distributes packages under the @vercel-private scope, requiring authentication through a Edgenivo account. See Private Registry.

A private connection from your Edgenivo deployments to AWS-hosted backend services through AWS PrivateLink endpoint services, so traffic doesn't cross the public internet. See AWS PrivateLink.

The live version of your application that serves end users, typically deployed from your main branch.

An application that you have deployed to Edgenivo, which can have multiple deployments and is connected to a Git repository.

The set of overrides for build, routing, function, cron, and image-optimization defaults. Define them in vercel.json, vercel.ts, or the dashboard. See Project Configuration.

An Enterprise feature that restricts deployments of an organization's Git repositories to authorized Edgenivo teams, preventing accidental deployments to personal accounts. Up to five scopes per team. See Protected Git Scopes.

An Observability tool for exploring traffic, errors, latency, and similar metrics across your projects. Save queries to Notebooks for reuse and team collaboration. See Query.

See Edgenivo Queues.

A system for managing what each team member can do on Edgenivo through assigned roles such as owner, member, billing, and developer. See Role-based access control.

A performance metric in Speed Insights that uses real user data to measure your application's actual performance in production.

HTTP responses that tell clients to make a new request to a different URL, useful for enforcing HTTPS or directing traffic.

An in-memory key-value store connected to your Edgenivo project through the Edgenivo Marketplace, provisioned from providers such as Upstash. See Redis on Edgenivo.

Geographic locations where Edgenivo can run your functions and store data. Edgenivo has 19 compute-capable regions globally.

The stages a Edgenivo product passes through before becoming generally available: Alpha (under development), Beta (pre-GA without an SLA), Private Beta (under NDA), Limited Beta (publicly announced with gated access), Public Beta (available without special invitation), and General Availability (GA). See Release Phases.

A cache that shares build outputs and task artifacts across your Edgenivo team, CI, and Edgenivo builds, so unchanged tasks don't run twice. Turborepo uses it natively, and the Remote Cache SDK supports other build tools such as Nx and Rush. See Remote Caching.

A location where files and source code are stored and managed in version control systems like Git, maintaining history of all changes.

A programmatic interface for managing your Edgenivo account, projects, and deployments through HTTP requests or the Edgenivo SDK. See REST API Reference.

URL transformations that change what the server fetches internally without changing the URL visible to the client.

A deployment strategy that rolls out a new build to a configurable fraction of traffic before promoting it to 100%. You can pair it with Skew Protection and Instant Rollback. Available on Pro and Enterprise plans. See Rolling Releases.

How Edgenivo's CDN evaluates rules on every request before checking the cache or invoking your code. Order: firewall, bulk redirects, project-level routes, deployment-level routes. Define rules in your framework, in vercel.json or vercel.ts, or from the dashboard. See Routing.

Code that executes before a request is processed, running on Fluid Compute to modify responses, implement authentication, or perform redirects.

The execution environment for your functions. Edgenivo Functions support Node.js, Bun, Python, Rust, Go, Ruby, Wasm, and the beta Container runtime. See Runtimes.

A regional, ephemeral cache for storing and retrieving data across Edgenivo Functions, Routing Middleware, and builds within a Edgenivo region, with invalidation through TTLs and tags. See Runtime Cache.

Logs generated by your functions during execution, useful for debugging and monitoring application behavior.

An authentication protocol that allows teams to log into Edgenivo using their organization's identity provider. Available on Enterprise plans and as a Pro add-on.

See Edgenivo Sandbox.

An Enterprise add-on that creates private connections between Edgenivo Functions or Edgenivo Sandbox and backend infrastructure using dedicated static IP addresses, VPC peering, and isolated networks. See Secure Compute.

A cloud computing model where code runs without managing servers, automatically scaling based on demand and charging only for actual usage.

A beta feature that lets you deploy multiple backends and frontends within a single Edgenivo project, such as a Next.js frontend and a FastAPI backend in the same repository sharing routing, environment variables, and a domain. See Services.

A single running microVM instance inside a Edgenivo Sandbox. Persistent sandboxes can have many sessions over time: each time a sandbox resumes from its last snapshot, a new session begins. See Persistent Sandboxes.

A feature that prevents version mismatches between client and server during a deployment by pinning framework-managed requests to a specific deployment ID. On by default for projects created after November 19, 2024. Available on Pro and Enterprise plans. See Skew Protection.

A TLS extension where the client sends the destination hostname in plain text at the start of the handshake, before encryption begins. The Sandbox firewall uses the SNI to identify and filter HTTPS traffic by domain. Connections without an SNI cannot be matched to a domain rule.

Performance monitoring that provides detailed insights into your website's Core Web Vitals and loading performance metrics.

A Pro and Enterprise feature that notifies you, triggers a webhook, or pauses production deployments when team spend reaches a threshold within a billing cycle. Enterprise teams need the Flexible Commitment plan. Configurable by team owners and billing roles. See Spend Management.

Shared static egress IP addresses that let Pro and Enterprise projects reach backend services that require IP allowlisting. Static IPs apply to outbound traffic only. For dedicated networks and VPC peering, use Secure Compute. See Static IPs.

Edgenivo's suite of storage products including Edgenivo Blob for large files, Global Config for low-latency configuration data, and the Edgenivo Marketplace for databases such as Postgres and Redis.

A technique for sending data progressively from functions to improve perceived performance and responsiveness.

See Edgenivo Toolbar.

The collection and analysis of how a request flows through your application and Edgenivo's infrastructure, captured as spans. Continuously collect sampled traces from production and preview traffic with always-on tracing, trace your own session with Session Tracing in the Edgenivo Toolbar, export them with trace drains, or add spans with @vercel/otel for OpenTelemetry. See Tracing.

A deployment protection method that restricts access to deployments based on IP address allowlists, available on Enterprise plans.

A high-performance build system for monorepos that provides fast incremental builds and remote caching capabilities.

An additional login verification step using either an authenticator app for time-based one-time passwords or a passkey through a WebAuthn-compatible device. You can configure recovery codes to regain access if you lose your second factor. See Two-factor authentication.

An AI agent from Edgenivo that builds full-stack apps and agents from natural language prompts and deploys them to Edgenivo. See the v0 docs.

An AI assistant built into Edgenivo that uses context from your projects, deployments, logs, and repositories. Chat with it from the dashboard or Slack, use Investigations to analyze alerts, failed deployments, runtime errors, and cost or performance issues, and use Code Review for pull request feedback. In public beta for Pro and Enterprise teams. See Edgenivo Agent.

A deployment protection method that restricts access to team members and authorized users with Edgenivo accounts.

Scalable object storage service for static assets like images, videos, and files, optimized for global content delivery.

A service that gives your agents and apps short-lived access to third-party APIs such as Slack, GitHub, Microsoft, and Snowflake. You set up a connection once at the team level, and allowed projects request tokens at runtime, so provider secrets never live in your environment variables. See Edgenivo Connect.

A multi-layered security system that protects applications from threats, including platform-wide DDoS protection and customizable WAF rules.

Tools for building platforms where agents and users deploy apps, either as isolated projects for generated apps or as one multi-tenant deployment that serves many customers through custom domains and subdomains. See Edgenivo for Platforms.

Serverless compute that allows you to run server-side code without managing servers. Functions automatically scale based on demand and offer enhanced concurrency through Fluid Compute for AI workloads and I/O-bound tasks.

A catalog of third-party services that integrate directly with your Edgenivo projects, including databases, observability tools, AI providers, and CMSs. Marketplace integrations inject credentials as environment variables and bill through your Edgenivo account. See Integrations.

A durable event-streaming system for serverless applications. Producers publish messages to topics, and consumer groups process them in parallel with automatic retries and replay. Powers Edgenivo Workflows. See Edgenivo Queues (beta).

A compute primitive for safely running untrusted or user-generated code in isolated Linux microVMs, designed for AI agents, code generation, and developer experimentation. Sandboxes are persistent by default: the filesystem is snapshotted when a session stops, and the sandbox configuration is preserved across sessions, so both are restored on the next resume.

A browser overlay for iterating on deployments, with Comments, Feature Flags, Draft Mode, Edit Mode, layout shift inspection, and accessibility audits. Enabled by default on previews. See Edgenivo Toolbar.

A managed platform for building durable applications and AI agents in JavaScript, TypeScript, and Python. The code can pause, resume, and maintain state across Edgenivo Functions and Edgenivo Queues, with managed persistence handling state and event logs. See Edgenivo Workflows.

A predictive performance metric that anticipates the impact of changes on application performance before deployment.

A customizable security layer that allows you to define rules to protect against attacks, scrapers, and unwanted traffic.

Privacy-friendly analytics that provide insights into website visitors, page views, and user behavior without using cookies.

HTTP POST endpoints that fire when an event happens in your Edgenivo team, such as a deployment finishing or a domain changing. Use them to trigger external workflows or integration logic. Available on Pro and Enterprise plans. See Webhooks.

See Edgenivo Workflows.

In JavaScript, an entity in a repository that can be either a single package or a collection of packages, often at the repository root.