Cargo CDK

The runtime under your agents, declared in code.

Agents, context, tools, data models, plays, territories, apps, and the connectors under them, as TypeScript.Plan the diff, deploy declaratively, roll back anytime. Written by you, or by your coding agent.

Start building for free

Define, plan, deploy.

One definition for the whole workspace: agents, context, tools, data models, plays, territories, apps, connectors. Preview every change offline, deploy declaratively, roll back instantly.

Read the CDK docsEvery builder, the deploy flow, state and drift.

Install the CLIcargo-ai cdk init, plan, and deploy in one prompt.

1import {

2defineConnector,

3defineModel,

4defineAgent

5} from "@cargo-ai/cdk";

7export const hubspot = defineConnector("hubspot", {

8integration: "hubspot",

9});

11export const contacts = defineModel("contacts", { dataset: hubspot });

13export const sdr = defineAgent("sdr", {

14models: [{ ref: contacts, readOnly: true }],

15});

Quickstart

Up and running in three commands.

Install the CLI, scaffold a project, and deploy your first resources. No YAML, no clicking through a console.

Install the CLI

$npm i -g @cargo-ai/cli

Scaffold a project

$cargo-ai cdk init my-workspace

Deploy

$cargo-ai cdk deploy

One definition

Your whole workspace, in code.

Every Cargo resource has a define builder. Wire them together and the dependency graph is just your variable graph.

Own it, don't rent it

What only code unlocks.

Rent your GTM as a stack of point tools, or own it as code. Versioned, reproducible, composable, and yours to keep.

VersionedYour entire GTM in git. Diff every change, review it in a pull request, and roll back a bad deploy with one command.
ReproducibleSpin up a whole GTM from one definition, in a single deploy: staging to prod, a new region, a fresh client workspace.
ComposableTyped primitives (models, plays, tools, agents) that you wire together in code. Not cells in a spreadsheet.

Questions engineers ask

Everything else lives in the docs.

No. Deploys are additive, so resources you create in the UI stay put. Mix visual and code however you like.

Yes. cargo-ai cdk import binds live resources into state, so you can adopt the CDK without starting over.

secret() reads values at deploy time and keeps them out of your state file and the content hash.

cargo-ai cdk refresh reports what drifted; deploy --refresh folds those changes back in or re-applies your code.

Yes. cargo-ai cdk types generates types from your real integration schemas, checked before you deploy.

cargo-ai cdk rollback restores the pre-deploy snapshot in one command.

Trusted by 10,000+ GTM Engineers working at

Give your agents a runtime

Bring the agents you have.Start free, deploy in one command.

Start building for free