cohenta
Get started
HomePricing

Product

How it worksCapabilitiesAsset typesProduct surfaces

Studios

CreativeVisualVideoResearch

Platform

DistributionIntegrationsQuality & TrustSolutionsSecurityThe engine

Company

AboutEnterpriseBlogNewsContactFAQ
Sign in · soonGet started

For enterprise

Runs in your cloud. Answers in Teams.

Team Deployment puts the engine in an account you control — and @Cohenta in Teams, as an app your organization owns.

Talk to usRequest a walkthrough
Your keys stay yoursApproval policiesZero custodyPriority support
for enterprisedeployment boundary
YOUR CLOUDRunnerthe engineYour vaultreferences onlyCampaign stateyour disk · your DBSlackMicrosoft Teams@Cohenta answers hereCohenta cloudlicense checkssigned updatesno campaign traffic
Team Deployment — what runs whererunner · vault · state

The trust story

Nothing of yours on our side.

Cohenta never receives or stores your keys, credentials, assets, or campaign state.

The Runner in your subscription

Templates for Azure, AWS, and GCP land the engine inside your network rules and your residency. Cohenta operates none of it.

Teams under your Entra registration

The app is registered in your directory, with scopes your admins read, consent to — and can revoke. No standing access to your tenant.

Keys resolved in your vault

References, not values. The Runner resolves keys at call time from Azure Key Vault, AWS Secrets Manager, or GCP Secret Manager — never into a log or a call to Cohenta.

One brand configuration, every seat

Voice, palette, and banned terms compile once. Every campaign — whoever starts it — is authored and reviewed inside the same rules.

Approvals with names in them

Who reviews and who publishes is policy, per brand or per channel. A run pauses at its gate — durably — until a named approver presses the button.

Signed updates, on your schedule

The Runner installs builds signed by Cohenta, when you choose. Our cloud sees license pings and optional telemetry — campaign data, never.

Getting started

From template to first campaign.

Configuration, not a services engagement — and we stay on the call, first apply to first approval.

Stand up the RunnerAzure · AWS · GCP — templates providedBring @Cohenta into Teamsyour Entra registration · admin consentSet policy and brandnamed approvers · brand rules · per channelpaper · in parallelProcurementterms · privacy · DPAfirst approved run
Rollout — three stations and a gatetemplate · entra · policy

Standard terms and the privacy policy are published today — send both ahead. Licenses and downloads land in the accounts portal at launch.

For agencies

One partner, many deployments.

One deployment per client — their account, their keys, their rules. Your team operates; their names approve. No client credential sits with you, or with us.

Talk about a partner setup

Pricing, plainly

One tier on a public ladder.

Priced in the open, next to the free skills and the Pro Runner. Monthly or annual. No quote call.

See pricing

Buyer questions

Asked before signing.

What does a security review cover?
Your own controls, mostly — the account, the vault, and the network the Runner sits in are all yours to show. Our side contributes signed builds and a license check, so that part of the questionnaire is short.
Where does campaign data live?
With you — assets and campaign state sit on your disk, database, or object storage. Messages routed through Teams or Slack are processed by Microsoft or Slack, like the rest of your tenant traffic.
Who can approve and publish?
The people your policies list. Approval is a button press in Teams or Slack — never inferred from conversation — and publishing takes its own explicit confirmation after review.
Do we need Microsoft Teams?
No — Slack, Claude Code, the CLI, and the API work the same against a deployed engine. Teams, the claude.ai connector, and remote MCP are what this tier adds.
Can one deployment serve several brands or clients?
Yes — brand config and approval policies are scoped per brand inside one deployment. Agencies usually add a deployment per client when isolation is the point.
What about a DPA and custom terms?
The paper on this site applies from day one. Send your DPA or addendum over — we hold none of your keys, credentials, or campaign data, so both tend to be short conversations.

Next step

Ready when your cloud is.

A scoping call on architecture, policy, and paper — or watch a Team Deployment run a campaign, gate to gate.

Talk to usRequest a walkthrough