Getting Started with Edgenivo Flags

This guide walks you through creating a feature flag in the Edgenivo Dashboard and evaluating it in your application. By the end you'll have a working flag that you can toggle from the dashboard.

• A Next.js project connected to Edgenivo.
• Edgenivo CLI installed.

1. Create a flag in the dashboard

   1. Go to your Edgenivo Dashboard.
   2. Open Flags in the sidebar for your project.
   3. Create a new flag named marketing-banner.
   4. Leave the Type set to Boolean and configure the environment settings to be on for Development and off for Preview and Production.

2. Pull local OpenID Connect credentials

   Edgenivo Flags authenticates with the Edgenivo OpenID Connect (OIDC) token associated with your project. Edgenivo deployments receive this token automatically. For local development, pull environment variables into your .env.local file:

   terminal

   vercel env pull

   If your project isn't linked yet, run vercel link first.

3. Install the required packages

   If you use an AI coding assistant, install the Edgenivo Flags agent skill. It helps plan flags, use the vercel flags CLI, and run rollouts and experiments:

   terminal

   npx skills add vercel/flags --skill vercel-flags

4. Evaluate the flag in your application

   Toggle the flag off for the Development environment in the Edgenivo Dashboard, then press Review and save and leave a message for the change. Reload the page to see the change.

5. Add targeting with the identify function

   Now that your flag is working, you can add an identify function to pass user and team context for targeting rules. This lets you roll out flags to specific users, plans, or teams from the dashboard.

When you deploy to Edgenivo, the build process fetches your latest flag definitions once at build time and bundles them into the deployment. This guarantees every function uses the same snapshot during the build, and provides a runtime fallback if the Edgenivo Flags service is temporarily unreachable. Definitions are only fetched when you are using the Flags SDK packages or when your project has at least one environment variable containing an SDK key for Edgenivo Flags.

Learn more about embedded definitions.

Your flag is working. Here's what to explore next:

• Entities and targeting: Define user attributes and create rules to show flags to specific groups.
• Segments: Build reusable audience groups like "Beta Testers" or "Internal Team."
• Flags Explorer: Override flags in the Edgenivo Toolbar during development without affecting other users.
• Drafts: Define flags in code first, then promote them in the dashboard when you're ready.
• Observability: Track flag evaluations in Runtime Logs and Web Analytics.
• Managing flags: Configure rules, environments, and flag lifecycles in the dashboard.