Skip to main content
Connic

Move beyond self-hosting
to more capable agents

Test changes before release, compare variants with real requests, and require human approval for sensitive actions. Moving to Connic gives your team these capabilities on a platform that also handles execution, scaling, and monitoring.

Start for freeTalk to Sales
Read the migration guide
agents/invoice-processor.yaml
# Define the whole agent in one YAML file
name: invoice-processor
model: connic/gpt-5.6-sol
reasoning_effort: auto
system_prompt: |
You are an expert accountant.
Extract every field from the invoice
and verify the totals add up.
tools:
  - documents.parse
  - documents.extract_entities
  - database.store_invoice

Connic handles hosting, scaling, and observability

With self-hosting, your team operates the infrastructure, adjusts capacity, and maintains monitoring. Connic handles these tasks for the agents, reducing maintenance and on-call work.

Hosting

Skip all this

  • Kubernetes manifests
  • Docker builds
  • CI/CD pipelines
  • Cluster upgrades

git push is the deploy. No containers to babysit, no pipelines to debug, no cluster upgrades on the calendar.

Scaling

Skip all this

  • HPA configuration
  • Resource tuning
  • Capacity planning
  • Idle resource costs

Managed runtime scales with demand. Billing covers runs and minutes instead of idle clusters waiting for traffic.

Observability

Skip all this

  • ELK / Loki setup
  • Prometheus metrics
  • Grafana dashboards
  • Alert configuration

Full execution traces are on by default. Every LLM call, tool call, and timing shows up in the dashboard without a separate observability stack.

Reuse your existing code

Python tools, prompts, and business logic form the foundation for migration. Configure agents in YAML while Connic handles deployment and operations.

What remains
  • Python tools

    Same functions, same logic. Drop them in tools/

  • Agent logic

    Prompts and orchestration translate to YAML and middleware

  • Git workflow

    Branches, PRs, and code review stay unchanged

  • External integrations

    APIs, databases, and services stay reachable from custom tools

What disappears
  • Kubernetes configs

    Manifests, Helm charts, kubectl runbooks

  • Docker setup

    Dockerfiles, image builds, registry plumbing

  • CI/CD pipelines

    GitHub Actions, Jenkins, deploy scripts

  • Monitoring stack

    Prometheus, Grafana, custom alert rules

Follow the quickstart to cut over the first agent.

Self-hosted vs Connic

What teams manage today and what Connic takes over

Self-hosted vs Connic
FeatureSelf-HostedConnic
DeploymentDocker/K8s + CI/CDgit push
RollbacksManualOne-click
ObservabilityDIY (Prometheus, Grafana)Built-in
Retrieval (RAG)DIY (vector DB)Built-in
ConnectorsCustom per systemFirst-party catalog
A/B testingNot includedIncluded
Automated evaluation (Judges)Not includedIncluded
Human-in-the-loop approvalsNot includedIncluded
Budget alerts & limitsNot includedIncluded
Team permissions (RBAC)DIYBuilt-in
Secrets managementVault / env filesBuilt-in
Auto-recoveryDIYBuilt-in

Support for your migration

Personal assistance, suitable infrastructure, and materials for legal and security reviews support your move to Connic.

Dedicated infrastructure

Enterprise plans come with dedicated compute, custom SLAs, and an account manager who guides the team through the migration end to end.

Support for compliance review

Enterprise provides a DPA, EU AI Act readiness support, and documentation covering SOC 2 Type II, ISO 27001, and HIPAA. These give your team a basis for reviewing the provider change internally. Audit logs are included in every plan.

Migrate at a controlled pace

For a staged cutover, Bridge keeps services in the VPC while agents run on Connic. Workloads can move one at a time on the team's timeline.

Keep exploring

Composer SDK

Define agents in YAML.

Bridges

Reach private services, no inbound ports.

Observability

Trace every step, every token.

Connectors

Wire agents to real systems.

Environments

Per-env config and secrets.

Testing

Assertions and judges, in CI.

Frequently Asked Questions

Start with one agent and use connic migrate for conversion. The migration report identifies items that need manual adjustment. After review and testing, move that agent to Connic while the remaining agents continue on the existing infrastructure.

Tools, prompts, and business logic form the foundation for the agent in Connic. Framework-specific configuration and workflows move into YAML, tools, and middleware. connic migrate helps with the transition; the result is then reviewed and tested.

Through Connic Bridge. A Bridge Agent inside the private network establishes an outbound connection to Connic. Agents running on Connic can then use internal databases and APIs without exposing them publicly.

Compare the full set of capabilities: Connic handles hosting and scaling and adds testing, observability, A/B tests, quality evaluations, human approvals, and cost controls. Connections, retrieval, sessions, and a database are available on the same platform. With self-hosting, building, operating, or buying these capabilities adds to server and maintenance costs. The pricing page lists plans and their included capabilities.

Your tools and business logic are written in Python and can be reused. The YAML agent configuration and functions such as StopProcessing or AbortTool are designed for Connic. If you switch platforms, these parts need to be adapted to the new environment.