Connectors Overview
DgiDgi provides a comprehensive connector ecosystem that connects your AI-powered development environment with the tools and services you need. Our connectors follow a BYOI (Bring Your Own Infrastructure) architecture where your actual data lives in your chosen providers, and DgiDgi orchestrates everything.
BYOI Architecture
DgiDgi is an orchestration layer, not a data storage layer. Your code, databases, and deployments live in your infrastructure:
What DgiDgi Stores vs What You Own
| Data Type | Where It Lives | What DgiDgi Stores |
|---|---|---|
| Source Code | Your GitHub/GitLab/Bitbucket | Repo URL, branch names, commit metadata |
| Databases | Your Supabase/PlanetScale/Neon | Connection string (encrypted), schema cache |
| Deployments | Your Fly.io/Vercel/Railway | Deployment ID, status, URLs |
| Secrets | Your vault or DgiDgi (encrypted) | Encrypted references |
| Chat Media | DgiDgi R2 buckets | Full files (platform functionality) |
| Run Artifacts | DgiDgi R2 buckets | Generated outputs, logs |
Connector Architecture
DgiDgi uses a two-tier connector architecture that provides flexibility:
Tenant Level
- Configured by organization owners
- Connects services with organization credentials
- Can override platform OAuth credentials (BYOA - Bring Your Own App)
- Manages organization-wide connector access
Project Level
- Configured by project members
- Enables specific tenant connectors for a project
- Project-specific configuration overrides
- Controls which connectors are available in the editor/agent
Credential Modes
Every connector has a credential mode that determines how authentication works:
| Mode | Description | Example Providers |
|---|---|---|
| Hybrid | Platform provides default, tenant can override | GitHub, OpenAI, Vercel |
| Tenant-Managed | Tenant must provide their own credentials | Auth0, Clerk, Render |
Credential Resolution Order
Why BYOI Matters
| Benefit | Description |
|---|---|
| Cost Isolation | Use your own OpenAI/Anthropic keys for direct billing |
| Compliance | Use organization-approved OAuth apps |
| Data Residency | Data stays in your chosen regions |
| Full Ownership | Export and leave anytime with your data |
| Custom Scopes | Request specific permissions for your apps |
Connector Categories
| Category | Description | Examples |
|---|---|---|
| AI | LLM providers and AI services | OpenAI, Anthropic, Groq, Gemini |
| CLI/AI | AI-powered CLI tools | Claude Code, GitHub Copilot CLI, Aider |
| Source Control | Version control systems | GitHub, GitLab, Bitbucket, Azure DevOps |
| Database | Database and data services | PostgreSQL, MongoDB, Supabase, Neon |
| Deployment | Hosting and deployment platforms | Vercel, Netlify, Fly.io, Cloudflare |
| Auth | Authentication providers | Clerk, Auth0, Supabase Auth, Firebase |
| Storage | File and object storage | S3, Cloudflare R2, Google Cloud Storage |
| Payments | Payment processing | Stripe, Paddle, LemonSqueezy |
| Email services | Resend, SendGrid, Postmark | |
| Analytics | Analytics and monitoring | PostHog, Mixpanel, Sentry |
| Messaging | Communication platforms | Slack, Discord, Telegram |
| Productivity | Productivity tools | Notion, Linear, Jira |
| Search | Search engines | Algolia, Typesense, Meilisearch |
| Web3 | Blockchain and crypto | Alchemy, Infura, OpenSea |
| Runtime | Container and serverless | Kubernetes, Docker, AWS Lambda |
| Secrets | Secret management | HashiCorp Vault, 1Password, Doppler |
| CI/CD | Continuous integration | GitHub Actions, CircleCI, ArgoCD |
| Observability | Logging and tracing | OpenTelemetry, Grafana, Jaeger |
| Security | Security scanning | Snyk, SonarQube |
| Data | Data pipelines | Snowflake, Airbyte |
| API Management | API gateways | Kong |
| Mobile | Mobile development | Expo |
| Marketing | Marketing platforms | Google Ads, Facebook, HubSpot |
Authentication Types
DgiDgi connectors support multiple authentication methods:
| Auth Type | Description | Use Case |
|---|---|---|
| API Key | Simple key-based authentication | Most cloud services |
| OAuth 2.0 | Secure token-based with refresh | GitHub, Google, Slack |
| Basic Auth | Username/password | Legacy systems |
| Bearer Token | Pre-authenticated token | Service accounts |
| IAM Role | Cloud IAM authentication | AWS, GCP, Azure |
| Connection String | Database connection URLs | PostgreSQL, MongoDB |
| None | No authentication required | Local services (Ollama) |
Credential Security
All credentials are encrypted and securely stored:
Connector Status
| Status | Description | Color |
|---|---|---|
| Connected | Working and verified | Green |
| Pending | Awaiting configuration | Yellow |
| Pending Approval | Requires admin approval | Orange |
| Error | Configuration or connection issue | Red |
| Failed | Authentication failed | Red |
| Expired | Token expired, needs refresh | Gray |
| Disabled | Manually disabled | Gray |
Getting Started
For Organization Owners
- Navigate to Settings > Connectors in the DgiDgi dashboard
- Browse the provider catalog by category
- Click Connect on the connector you want to add
- Choose authentication method:
- OAuth: Click "Sign in with [Provider]" for automatic setup
- API Key: Enter credentials manually
- Verify the connection and save
For Project Members
- Open your project and go to Settings > Connectors
- Click Set Up Connectors
- Select from your organization's connected connectors
- Configure project-specific settings if needed
- The connector is now available in the editor and agent
Using Your Own Credentials (BYOI)
To use your own OAuth app or API keys:
- Go to Settings > Connectors
- Click on the connected provider
- Click Override Credentials
- Enter your own:
- OAuth App: Client ID, Client Secret, Callback URL
- API Key: Your API key from the provider
- Save and re-authenticate
API Reference
Tenant Connectors API
# List connected connectors
GET /api/v1/tenant/connectors
# Connect a new connector
POST /api/v1/tenant/connectors
{
"providerId": "github",
"providerName": "GitHub",
"category": "source_control",
"authType": "oauth",
"credentials": {}
}
# Update connector
PATCH /api/v1/tenant/connectors/:id
# Verify connector
POST /api/v1/tenant/connectors/:id/verify
# Delete connector
DELETE /api/v1/tenant/connectors/:id
Project Connectors API
# List project connectors
GET /api/v1/projects/:projectId/connectors
# Enable connector for project
POST /api/v1/projects/:projectId/connectors
{
"tenantConnectorId": "conn_123",
"config": {}
}
# Update project connector config
PATCH /api/v1/projects/:projectId/connectors/:id
# Remove from project
DELETE /api/v1/projects/:projectId/connectors/:id
Related Documentation
- Connector Catalog - Complete list of all connectors
- AI Providers - Detailed LLM provider information
- CLI Tools - Command-line AI tools
- SDK Documentation - Using connectors in code
- Security Overview - Security and compliance