Product Introduction
Quick Start
- Agent Development
- Importing a Git Repository
- Starting From a Template
- Direct Upload
- Start with AI
Framework Guide
- Agent
- Frontends
  - Vite
  - React
  - Vue
  - Hugo
  - Other Frameworks
- Backends
- Full-stack
  - Next.js
  - Nuxt
  - Astro
  - React Router
  - SvelteKit
  - TanStack Start
  - Vike
- Custom 404 Page
Project Guide
- Project Management
- edgeone.json
- Configuring Cache
- Building Output Configuration
- Error Codes
Build Guide
Deployment Guide
- Overview
- Create Deploys
- Manage Deploys
- Deploy Button
- Using Github Actions
- Using Gitlab CI/CD
- Using CNB Plugin
- Using IDE PlugIn
- Using CodeBuddy IDE
Domain Management
- Overview
- Custom Domain
- HTTPS Configuration
  - Overview
  - Apply for Free Certificate
  - Using Managed SSL Certificate
- Configure DNS CNAME Record
Observability
- Overview
- Metric Analysis
- Log Analysis
Functions
- Overview
- Edge Functions
- Cloud Functions
  - Overview
  - Node.js
  - Python
  - Go
Agents
- Overview
- Quick Start
- Conversation Storage
- Observability
- Sandbox Tool
  - Overview
  - Using the Agent Framework
  - Sandbox Atomic API
  - Network Search Tool
- Agent Authentication
Models
- Overview
- Models and Vendors
  - Overview
  - Using Vendor Keys
    - OpenAI
    - Anthropic
    - Google AI Studio
    - DeepSeek
    - MiniMax
    - Hunyuan
    - Zhipu
    - MoonShot AI
- FAQs
Storage
- Overview
- KV
- Blob
Middleware
AI-Native Development
- Skills
- MCP
Copilot
- Overview
- Quick Start
API Token
EdgeOne CLI
Message Notification
Integration Guide
- AI
  - Dialogue Large Models Integration
  - Large Models for Images Integration
- Database
  - Supabase Integration
  - Pages KV Integration
- Ecommerce
  - Shopify Integration
  - WooCommerce Integration
- Payment
  - Stripe Integration
  - Integrating Paddle
- CMS
  - WordPress Integration
  - Contentful Integration
  - Sanity Integration
  - Payload Integration
- Authentication
  - Supabase Integration
  - Clerk Integration
Best Practices
- Adding an AI Chat Assistant to a Website
- AI Dialogue Deployment: Deploy Project with One Sentence Using Skill
- Using General Large Model to Quickly Build AI Application
- Use the DeepSeek model to quickly build a conversational AI site
- Building an Ecommerce Platform with Shopify
- Building a SaaS Site Using Supabase and Stripe
- Building a Company Brand Site Quickly
- How to Quickly Build a Blog Site
Migration Guides
- Migrating from Vercel to EdgeOne Pages
- Migrating from Cloudflare Pages to EdgeOne Pages
- Migrating from Netlify to EdgeOne Pages
Troubleshooting
FAQs
Limits
Pricing
Contact Us
Release Notes

Using CNB Plugin

By following the guidelines in this section, you can quickly integrate a cloud-native build process in CNB to automatically build and deploy to EdgeOne Makers.
Configuring a Private Key
Obtain EDGEONE_API_TOKEN from Makers. For details, see API Token.
Use the CNB key repository for storage, then refer to it in the pipeline. The envs.yml content is as follows:
EDGEONE_API_TOKEN: oJTlMUq9**********NYzKFIw=
The complete .cnb.yml is configured as follows:
# trigger: push to master branch
main:
  push:
    # Import environment variables from private repository:
    # See: https://docs.cnb.cool/en/build/env.html#importing-environment-variables
    - imports: https://cnb.cool/***/-/blob/main/envs.yml
      stages:
        # Build Current Project
        - name: Build Current Project
          image: node:20
          script: node -v && npm install && npm run build
        # Deploy Build Output to EdgeOne Makers
        # The ./dist directory is generated in the previous build step
        # See: https://www.npmjs.com/package/edgeone
        - name: Deploy to EdgeOne Makers
          image: node:20
          script: npx edgeone makers deploy <outputDirectory> -n <projectName> -t $EDGEONE_API_TOKEN
Note:
npx edgeone makers deploy Parameter Description:
<outputDirectory>: The folder where the project build product resides (required).
-n, --name: Project name that needs to be deployed. A new project will be created automatically if the project does not exist (required).
-e, --env: Target environment for deployment, available values: production or preview (default production).
Example: npx edgeone makers deploy ./dist -n project-name -t $EDGEONE_API_TOKEN.
Cloud Native Build (CNB)
When code is pushed to the main branch, it triggers the following build process:
1. Import required environment variables.
2. Build project using Node.js 20 environment.
3. Deploy the build output to Makers.
EdgeOne Makers Deployment
After the build is complete, the project is automatically deployed to Makers through the following process:
1. Build stage generates ./dist directory.
2. Deploy using the EdgeOne CLI tool edgeone makers deploy.
More examples
Reference Documentation

Configuring a Private Key
Cloud Native Build (CNB)
EdgeOne Makers Deployment