Publishing connectors

• Other organizations can deploy it
• It appears in the Connector Hub
• It becomes eligible for hosted mode (C1 runs it for customers)
• The community can contribute improvements

​

Publishing flow

​

Version lifecycle

​

Publishing paths

​

Contributing to existing connectors

• Fork the repository
• Add your changes
• Submit a pull request
• Maintainers review and merge
• New version published with your changes

• Fork the repository
• Publish under your organization
• Maintain independently

​

New connectors

• Work with C1 to host in their GitHub org
• Benefits from existing CI/CD and publishing infrastructure

• Host in your own GitHub organization
• Publish to registry under your org name
• Full control, full responsibility

• Don’t publish to the public registry
• Deploy in daemon mode on your infrastructure
• Suitable for proprietary internal systems

​

Supported platforms

​

Signing keys

​

Contributing a connector

​

Before you start

1. Check for existing connectors: Search the Connector Hub for your target system. If one exists, consider contributing improvements rather than building from scratch.
2. Review the SDK: Familiarize yourself with the baton-sdk and the building connectors guide.
3. Understand the target system’s API: You’ll need API credentials with sufficient permissions to list users, groups, roles, and other access-related resources.

​

Implementation requirements

​

Pull request process

​

For existing connectors

# Fork the repository
gh repo fork ConductorOne/baton-yourservice
cd baton-yourservice

# Create a feature branch
git checkout -b feature/add-role-support

# Make your changes, then run local validation
make build
make lint
make test
./dist/*/baton-yourservice --help

# Submit a pull request

​

For new connectors

1. Use the standard project structure
2. Ensure CI/CD is configured with standard GitHub workflows
3. Contact C1 if you want official hosting:
   • Open an issue on baton-sdk
   • Include: target system name, API documentation link, your use case
4. Or publish independently under your organization

​

Review criteria

​

Security reporting

• DO NOT file a public issue
• DO send a private report to security@c1.ai

​

Quick reference

​

Registry API methods