Storage Backends

AgentVerse stores artifact metadata in PostgreSQL. Artifact package archives (zip files uploaded via publish --zip) are stored in a configurable object store.

Supported Backends

Backend	Key	Best For
Local Filesystem	local	Development, E2E tests
S3 / COS / MinIO / R2	s3	Production — most common
GitHub Releases	github	Open-source projects
Custom HTTP	custom	Internal org storage
BK-Repo (蓝鲸)	bkrepo	Tencent BlueKing ecosystem ⭐ Default

Configuration

The backend is set in config/default.toml under [object_store]:

[object_store]
backend = "bkrepo"   # bkrepo | local | s3 | github | custom

You can also override at runtime with the OBJECT_STORE_BACKEND environment variable.

How It Works

1. User runs agentverse publish --zip skill.zip
2. CLI uploads the zip to POST /api/v1/skills/:ns/:name/upload
3. Server stores the archive in the configured backend
4. Server returns a download URL for the archive
5. URL is stored in the skill's package registry

Depending on the backend, the download URL may be:

• A public CDN URL (public bucket)
• A pre-signed URL with expiry (private S3 bucket)
• A GitHub Release asset URL
• A custom endpoint URL with embedded token

Choosing a Backend

graph TD
    A[Which backend?] --> B{Development?}
    B -->|Yes| C[local]
    B -->|No| D{Open-source?}
    D -->|Yes| E[github]
    D -->|No| F{Have S3/COS/MinIO?}
    F -->|Yes| G[s3]
    F -->|No| H{BlueKing ecosystem?}
    H -->|Yes| I[bkrepo]
    H -->|No| J[custom HTTP]