Platform

Deployment

Deploy your agents to Connic cloud using Git-based automatic deployments or CLI deployments.

Overview

Two ways to deploy your agents

Connic supports two deployment methods depending on your workflow:

Git Integration

Connect a Git repository to your project. Pushing to configured branches automatically triggers deployments.

• Automatic on push
• Branch-to-environment mapping
• Currently supports GitHub
• GitLab, Bitbucket coming soon

CLI Deployments

Deploy using the CLI - locally or in CI/CD pipelines. Perfect for unsupported Git providers or custom workflows.

• Works with any Git provider
• Use in CI/CD pipelines
• Manual control

Git Integration

Connect your Git repository for automatic deployments on push. Currently supports GitHub, with GitLab and Bitbucket support coming soon.

Connect Your Repository

Go to Project Settings → Git Repository and connect your Git provider.

You'll authorize Connic to access your repositories, then select which repository to connect to this project.

Configure Environment Branches

Go to Project Settings → Environments and configure which branch deploys to each environment.

For example:

• Production → main
• Staging → develop

Push to Deploy

Push changes to your configured branch. Connic automatically detects the push via webhooks and creates a new deployment.

bash

# Push to trigger deployment
git add .
git commit -m "Update agents"
git push origin main

CLI Deployments

Use the CLI to deploy from your local machine or CI/CD pipeline. This is the recommended approach for:

Git providers not yet integrated (GitLab, Bitbucket, self-hosted)
CI/CD pipelines where you want full control
Projects not using Git at all

Install the SDK

bash

pip install connic-composer-sdk

Authenticate

Create an API key in Project Settings and authenticate:

bash

connic login

This creates a .connic file:

json

{
  "api_key": "cnc_xxxxxxxxxxxx",
  "project_id": "your-project-uuid"
}

For CI/CD, use environment variables instead: CONNIC_API_KEY and CONNIC_PROJECT_ID

Get Your Environment ID

Go to Project Settings → Environments and copy the environment ID you want to deploy to.

Deploy

bash

# Deploy to default environment
connic deploy

# Deploy to a specific environment
connic deploy --env <environment-id>

The CLI packages your agents/, tools/, middleware/, schemas/, and requirements.txt and uploads them.

CI/CD Integration

Use the CLI in your CI/CD pipeline to deploy automatically on push - even with Git providers that aren't directly integrated yet.

yaml

# Example: GitLab CI/CD (.gitlab-ci.yml)
deploy:
  stage: deploy
  script:
    - pip install connic-composer-sdk
    - connic deploy --env $CONNIC_ENV_ID
  variables:
    CONNIC_API_KEY: $CONNIC_API_KEY
    CONNIC_PROJECT_ID: $CONNIC_PROJECT_ID

Set CONNIC_API_KEY, CONNIC_PROJECT_ID, and CONNIC_ENV_ID as CI/CD secrets.

What Happens During Deployment

Code is packaged and uploaded to Connic

Container is built with your dependencies

Agents are deployed and become available

Traffic is routed to the new deployment

Monitoring Deployments

View deployment status, logs, and history in the Deployments tab:

See all deployments with status and duration
Click a deployment to view build logs
The currently serving deployment is marked "Active"

Rollback a Deployment

If a deployment introduces an issue, you can quickly roll back to a previous stable version:

Open Deployments and select a prior successful deployment
Activate it to promote that revision as the current production version
Optionally revert the commit in Git to keep history in sync

bash

# Roll back by reverting a bad change
git revert <bad-commit-sha>
git push origin main

Ready to deploy!

Use Git integration for supported providers, or the CLI for everything else including CI/CD pipelines.

Environments

Manage environments and branch mapping

Observability

Monitor runs, traces, and token usage

Local Testing

Test agents locally with hot-reload

Variables

Configure secrets and settings per environment