Ships it: a census of 143 listings

Only for Ada's own sandboxed Code tools: promoting a change set puts the Python live in production conversations and a promote can be reverted, but a human approves and nothing deploys to your infrastructure.

Source retrieved 2026-09-09

The firm takes engagements through to live operation rather than stopping at a prototype, deploying production agents with logging, approvals and rollback paths.

Source retrieved 2026-09-29

There is no deploy feature; a GitHub Actions integration can trigger workflow_dispatch and the allowlisted shell can run git, so shipping is a pipeline you wire yourself.

Source retrieved 2026-09-09

Publishing is deliberately outside the default loop; commits, PRs and deploys must be exposed as separately gated tools.

It gives coding agents actions against deployment platforms, so a deploy can be triggered through Loadout, but Loadout itself produces no diff and the vendor documents no release pipeline of its own.

Source retrieved 2026-10-03

Built agents and workflows are deployed by the builder itself: publishing is a mandatory, version-controlled step in the Admin UI with rollback, so work does not stop at a draft.

Source retrieved 2026-09-24

The agent executes local shell commands under your permission rules, so it can run deploy scripts you authorise, but no release, CD or environment-promotion feature is documented anywhere in the CLI docs.

Source retrieved 2026-09-10

Deployment is inside the engagement rather than left to the client, and the handover step names the deployment environment and rollback explicitly.

Source retrieved 2026-10-03

Agents drive a change through CI to merge; the vendor does not claim the agent deploys or releases.

Source retrieved 2026-09-02

A team can execute the code it writes in a shell or Docker container, but nothing in the docs claims it opens pull requests or deploys to an environment.

Source retrieved 2026-09-19

Delivery runs past the diff into production: they publish a CI/CD-based deployment process, and the agent engagement has its own launch and post-launch tuning stage.

Source retrieved 2026-09-11

It ships agent versions to live phone traffic with canary, promotion and rollback; it does not deploy application code.

Bolt deploys the finished project itself to a live bolt.host address, with custom domains and Netlify as alternatives on paid plans.

Source retrieved 2026-09-11

One CLI command ships an ADK agent to a production bot on Botpress Cloud; it does not open a pull request or deploy to infrastructure you own.

Source retrieved 2026-09-02

Browser automations are deployed as hosted Functions, published and invoked from the CLI or API.

The CLI deploys the agent code you wrote to Cartesia's cloud; the product itself produces no diffs to ship.

Bash gives it git and script execution, so a deploy command is reachable, but the SDK documents no deployment surface of its own.

Source retrieved 2026-09-02

The claimed workflow ends at a commit, branch and pull request; deployment is only whatever shell command Claude is allowed to run.

Source retrieved 2026-09-02

It goes past the diff by running your own commands and by committing or opening a PR from the Kanban board, but Cline ships no deployment service of its own.

Source retrieved 2026-09-12

Accepted work lands in Git as a commit on the PR branch or a stacked pull request, pushed with your own credentials; nothing in the docs deploys or releases the change.

Source retrieved 2026-09-15

Locally it stops at edits plus commands you allow; pull requests are opened from Codex cloud or the GitHub Action.

Source retrieved 2026-09-02

It ships what it builds only into its own runtime: a tested integration is published as a governed tool the assistant can call in live chat and voice, with no deployment to customer infrastructure.

Source retrieved 2026-09-12

Cresta deploys the agents it builds through governed rollouts, A/B comparison against a baseline and one-click rollback; it does not ship application code to your own environments.

Source retrieved 2026-09-02

It ships the automation itself rather than landing code changes in your repository: crewai deploy create pushes a crew or flow to AMP.

It stops at the branch and pull request; deployment stays with your own CI, though a CLI run in CI can be given git and gh access.

Source retrieved 2026-09-02

Stops at the pull request in your repository; your team merges and ships through its existing pipeline.

Source retrieved 2026-09-02

One-click deploys exist but only through the legacy Cascade agent, only to Netlify, in beta, and capped at 1 deploy/day on Free and 10 on Pro; agents otherwise stop at a pull request.

Source retrieved 2026-09-03

The CLI pushes agent configuration to the platform and into CI/CD; what it deploys is agents, not application code.

High autonomy permits pushes, deployments and migrations; the Release stage that tracks ship gates is Private Preview.

Source retrieved 2026-09-02

One documented deploy path: the /deploy slash command in VS Code agent mode, which needs Cloud Run enabled and the Cloud Run MCP server installed as a Gemini extension. Not supported in JetBrains IDEs.

Source retrieved 2026-09-02

Deployment is claimed as the last step of the agent's own loop, so it goes past producing a diff; Claw can additionally host a site on its cloud computer.

Source retrieved 2026-09-15

Deployment is part of the framework: one command pushes an agent to Google Cloud, and the same agent can be containerised and run on infrastructure you control instead.

Source retrieved 2026-09-15

goose has no managed deployment pipeline of its own; it ships work by executing your shell and git commands, and the vendor positions CI/CD build and deployment workflows as tasks you script around the CLI.

Source retrieved 2026-09-16

Gumloop builds and deploys custom MCP servers straight from a GitHub repository on every push to main, but that ships the connector code, not the buyer's own applications.

Source retrieved 2026-09-09

The agent edits files and executes shell commands, but no deployment or release capability is described.

It goes past the artefact: generated websites and web apps publish to a public Julius link on every plan, but the vendor states custom domains and production backends need outside hosting.

Source retrieved 2026-09-17

It reaches further than a diff, committing, pushing branches and opening pull requests through the GitHub Action, but no deployment or release step is documented anywhere on the site.

Source retrieved 2026-09-18

Cloud Agents commit and push to a session branch and raise pull requests; the vendor names deployments only in a comparison claim, and documents no deploy pipeline.

Source retrieved 2026-09-02

LangSmith Deployment runs agents in production with one-click deploy from Studio and a control-plane API; the free Developer plan shows Deployment as N/A, so shipping starts at Plus.

Source retrieved 2026-09-18

Commits, pushes and opens pull requests; it cannot approve PRs and no deployment step is claimed.

Source retrieved 2026-09-02

Lindy ships what it builds to its own hosted lindy.link URL and rebuilds on the same address, so work reaches an audience without a deploy step, but it does not deploy into your own infrastructure.

Source retrieved 2026-09-19

What ships is the agent workflow itself: single-click deploy straight from a GitHub repo, listed on all four plans.

Deploys what it builds on managed infrastructure with a custom domain, so it goes past the diff; the API exposes the same publish step and deploys require a confirmation.

Source retrieved 2026-09-19

The beta agent-framework-tools package gives an agent local or Docker shell execution, so it can run any command you approve; no deploy, release or pull-request step is documented.

Publishing and deploying agents is unlimited on both paid tiers; deployment targets include hosted web apps, website embeds, webhooks, scheduled runs and, on Business, custom domains.

Source retrieved 2026-09-02

It deploys the AI agents built in Agent Studio, including promotion between instances; it ships no application code.

It can run shell commands including git operations when you ask, but by design it stops short of committing or pushing on its own, and no deployment surface is documented.

Source retrieved 2026-09-20

What it ships is the automation itself: publishing puts a workflow or agent version into production and schedules or channels then run it. It does not deploy application code.

Source retrieved 2026-09-02

Delivery runs past the diff into production: they take the platform live and then monitor and harden it inside the client's operation.

Source retrieved 2026-09-26

A Gateway publication broker creates commits, pushed branches and pull requests from a session; nothing in the docs claims it deploys.

Source retrieved 2026-09-02

It stops at a branch and pull request in your GitHub Actions runner; no deployment step is documented anywhere on the site.

Source retrieved 2026-09-21

It ends at a pull request rather than a deploy: the documented automation loop opens a PR and leaves the merge and release to you.

Source retrieved 2026-09-21

Through the API the agent pushes a branch and opens or updates a pull request; no deployment step or target is documented.

Source retrieved 2026-09-02

Agent versions ship through Draft, Sandbox, Pre-release and Live with rollback, drivable from the CLI or Agents API, but promotion to Live is always a manual step.

Source retrieved 2026-09-02

There is no deployment feature; the Coder shell tool runs unrestricted commands that outlive the run, so an agent can execute deploy commands you allow, and the docs warn to sandbox untrusted work.

Source retrieved 2026-09-21

Agent does not stop at a diff: publishing puts a running instance on Replit's cloud, with custom domains and monitoring included.

Source retrieved 2026-09-22

Delivery goes past the build to deployment of the accepted scope, with monitoring and access documented at launch.

Source retrieved 2026-09-04

It deploys metadata to the org itself, and through the Salesforce DX MCP Server's DevOps Center tools it commits and opens pull requests; deploy and delete stay approval-gated by default.

Source retrieved 2026-09-03

It does publish live: agents write straight into the connected CMS, and for sites built in code the fix arrives as a GitHub pull request that you merge yourself, so on that surface it stops at the diff.

Source retrieved 2026-10-03

It ships agent versions rather than code: publishing to ChatGPT can run through CI/CD, but nothing deploys application software.

Source retrieved 2026-09-26

Deploys what it builds: workflows ship as versioned REST endpoints, with deploy/undeploy/rollback callable from CI. What ships is workflows, not code.

Source retrieved 2026-09-03

Delivery does not stop at handing over artefacts: they put builds into production on client or VPS infrastructure and keep monitoring and iterating after go-live.

Source retrieved 2026-09-12

It does not stop at a design: the agent is published and deployed as an Orchestrator process, the CLI provisions a serverless machine and robot user for it, and Orchestrator then schedules and monitors the runs.

Source retrieved 2026-09-03

Delivers a live preview plus deployable source files; nothing on vecbase.com claims it deploys to your own hosting or merges to your repo.

Source retrieved 2026-09-03

Agents commit, push branches and open pull requests through the GitHub integration, but no page describes the agent performing a deployment.

Source retrieved 2026-09-03

Pushing, releasing and deploying are permitted but classified as external-risk actions that always stop for an explicit human approval prompt.

Source retrieved 2026-09-21

There is no deployment feature; the agent stops at a reviewable diff, though its terminal tool can execute any shell command you permit, which is how a deploy script would run.

Source retrieved 2026-09-29

It commits, pushes the task branch and opens a pull request with a pre-filled description, and can auto-push, but no page claims it deploys to an environment.

Source retrieved 2026-09-09

There is no deployment feature; the agent stops at edits on disk and whatever your own shell commands do, since git and deploy scripts run through the generic bash tool.

Source retrieved 2026-09-28

Delivery runs past the diff into production: they build CI/CD pipelines that deploy to staging and production, and deploy agents into the client environment with monitoring.

Source retrieved 2026-09-25