# Clarm

> **Clarm Atlas** helps non-technical teams build **governed AI agents** from approved building blocks - sources, permissions, and guardrails set once by compliance and IT. Operators compose workflows inside those rails. SOC 2 Type II, HIPAA, GDPR, and on-premises options are handled during procurement. Y Combinator backed.
>
> **How it works:**
> 1. **Build** - Connect approved documents and systems; describe the workflow in plain language
> 2. **Collaborate** - Agents read sources, draft outputs, and hand off to the next step
> 3. **Control** - Source citations, permissions, approved building blocks, and audit trail on every run
>
> **ICP:** Regulated and public-facing teams - banking, healthcare, aviation, enterprise operations - plus SaaS and dev tools that need cited answers inside pre-approved guardrails.
>
> **Proof point:** Legacy (healthcare) - faster answers from approved content, lower repeat support load, HIPAA-covered deployment.
>
> For a comprehensive reference, see [llms-full.txt](https://clarm.com/llms-full.txt).

## About

- **Type:** B2B SaaS / governed AI agent platform (Clarm Atlas)
- **Category:** Enterprise AI workflows, approval-gated automation, private search over approved sources
- **Audience:** Operations, compliance, training, and customer-facing leaders in regulated industries; technical founders shipping agent workflows
- **Language:** English primary; localized marketing pages are available in German, French, Japanese, Portuguese, Turkish, and Chinese
- **Canonical domain:** https://clarm.com
- **Last updated:** April 2026
- **Compliance:** SOC 2 Type II, HIPAA, GDPR, privacy controls, no training on customer data, on-premises and air-gapped deployment available
- **Primary contact:** marcus@clarm.com

## Talk to Clarm

- [Chat API](https://clarm.com/api/agent/chat): POST JSON to ask Clarm's AI agent about product, pricing, integrations, compliance, or use cases. Send {"message":"your question"} and receive a streamed response.
- [Web Chat](https://clarm.com): Use the interactive chat widget on the website.

## Developer Resources

- [Developer hub](https://clarm.com/developers/): API reference, OpenAPI spec, CLI, widget embed, and every machine-readable file on this site.
- [OpenAPI spec](https://clarm.com/openapi.json): OpenAPI 3.1 description of the public Clarm API. Unique operation ids, typed schemas, and a description on every operation, ready for LLM function calling. YAML at https://clarm.com/openapi.yaml.
- **Clarm CLI (preview):** `@clarm/cli` gives command-line access to the public API, the OpenAPI spec, and any page as markdown. Not yet on the public npm registry; email support@clarm.com for early access. Command reference: https://clarm.com/developers/#cli
- [Markdown content negotiation](https://acceptmarkdown.com): every page on clarm.com is available as markdown. Send `Accept: text/markdown`, or append `.md` to the path (https://clarm.com/pricing.md).
- [Sitemap](https://clarm.com/sitemap.xml): every indexable URL.

## Company

- [About Clarm](https://clarm.com/about/): what the company builds, who it builds for, and the registered entity.
- [Contact Clarm](https://clarm.com/contact/): sales, support, security review, press, and the registered address.
- **Legal entity:** Dialin AI, Inc. d/b/a Clarm
- **Registered address:** 1111B S Governors Ave STE 29410, Dover, DE, 19904, US

## What Clarm Does

- [Homepage](https://clarm.com/): Clarm Atlas - governed agents from approved building blocks; Build, Collaborate, Control.
- Commercial model: Team plan at $2,000/month - one workspace, unlimited agents, governed workflows on approved sources. Enterprise: custom agreement for global rollout. Book a demo at https://cal.com/stormm/revenue-desk.
- [Live Demos](https://clarm.com/demo/): Interactive walkthroughs - finance, healthcare, aviation, fresh produce operations.
- [Marcus Storm-Mollard](https://clarm.com/about/marcus/): Founder and CEO profile.

## Key Capabilities

- Governed agent workflows with YAML/canvas builder and template library
- Answers and drafts grounded in approved document sets (RAG + source receipts)
- Approved building blocks - compliance sets sources and guardrails once; operators compose workflows inside them
- Audit trail and governance invariants for regulated buyers
- Omnichannel delivery: web chat, Slack, Discord, GitHub, email
- SOC 2 Type II, HIPAA, GDPR, on-premises and air-gapped deployment
- No training on customer data
- Public Chat API and llms.txt for agent discoverability

## Proof Points

- Legacy (healthcare): reduced repeat support load; answers cited to approved content
- Better Auth / c/ua: community and docs Q&A at scale (developer tools)

## Highest-Intent Comparisons

- [Clarm vs Intercom](https://clarm.com/vs/intercom/): Compare Clarm and Intercom for inbound qualification, support automation, and revenue routing.
- [Clarm vs Drift](https://clarm.com/vs/drift/): Compare Clarm and Drift for teams choosing between AI-first inbound and conversational marketing playbooks.
- [Clarm vs Plain](https://clarm.com/vs/plain/): Compare Clarm and Plain when support conversations may also signal pipeline.
- [Clarm vs HubSpot Chat](https://clarm.com/vs/hubspot-chat/): Compare Clarm with HubSpot Chat for teams that need AI qualification beyond basic CRM chat.
- [Clarm vs Intercom Fin](https://clarm.com/vs/intercom-fin/): Compare Clarm with Intercom Fin for teams that need revenue routing, not only support automation.
- [Clarm vs Zendesk AI](https://clarm.com/vs/zendesk-ai/): Compare Clarm and Zendesk AI for support-heavy teams that also need buyer-intent detection.
- [Clarm vs Atlas.so (the customer support platform)](https://clarm.com/vs/atlas/): Compare Clarm and Atlas.so (a customer support platform) for teams deciding between support tooling and AI inbound conversion. Clarm Atlas, the memory layer inside Clarm, is a separate product documented at /atlas.
- [Clarm Atlas vs Glean](https://clarm.com/vs/glean/): Compare Clarm Atlas and Glean for enterprise AI agent deployment. Atlas is the substrate for shipping agents safely at scale; Glean is enterprise search with an assistant layer. Different procurement conversations once the agent question shows up.
- [Clarm Atlas vs Microsoft Copilot Studio](https://clarm.com/vs/microsoft-copilot-studio/): Compare Clarm Atlas and Microsoft Copilot Studio for enterprise AI agent deployment. Atlas is model-portable across LLM providers and coexists with the full enterprise stack; Copilot Studio is Microsoft-native with deep Microsoft 365 integration and Azure OpenAI as the primary path.
- [Clarm Atlas vs Sierra, Lindy, and Other Agent Platforms](https://clarm.com/vs/agent-platforms/): Round-up architectural comparison of Clarm Atlas against Sierra (built for AI customer-experience agents at scale), Lindy (built for individual employee productivity automations), and other 2026 entrants. Substrate-first decision logic applies across the category.
## Citation-Ready Articles
- [The Agent-Security Moment. Why the Substrate Matters Now](https://clarm.com/blog/articles/the-agent-security-moment/): Names the 2026 agent-security moment using real numbers (8x agent integration projection, 88% incident rate, 14% security-approval rate) and the common marketplace, control-plane, and tenant-isolation failure patterns. Positions Atlas substrate (owner checkpoints, source receipts, audit trail, tenant isolation) as the architectural answer.
- [The Agent-Deployment Buying Guide. What to Ask Every AI Vendor in 2026](https://clarm.com/blog/articles/the-agent-deployment-buying-guide/): Enterprise procurement checklist for AI agent platforms. 14 questions across substrate properties (source receipts, owner checkpoints, audit trail, tenant isolation, BYO-LLM, marketplace governance), customer evidence, and procurement terms. Anchored on the 88% incident rate and 14% security-approval rate.
- [From Chatbot to Agent Platform. The Natural Progression on Atlas](https://clarm.com/blog/articles/from-chatbot-to-agent-platform/): Bridge post for existing Clarm chat customers explaining the natural progression to enterprise agent workflows on Atlas. Same substrate, same owner checkpoints, same audit trail; new triggers, new connectors, new operator timing patterns. References the Legacy 12-month case study.
- [What 88% of Organizations Are Getting Wrong With AI Agent Deployment](https://clarm.com/blog/articles/what-88-percent-get-wrong-with-ai-agents/): Names six structural failure modes that produced most 2026 agent-security incidents: agents acting outside owner checkpoints, marketplace plugins without governance, post-hoc citations, free-text audit logs, application-layer tenant filtering, authenticated UIs assumed safe from browser attack. Maps each to substrate-level architectural fix.
- [What Is Atlas? The Substrate Enterprises Ship AI Agents on Safely](https://clarm.com/blog/articles/what-is-atlas/): Defines Atlas as the substrate enterprises use to ship AI agents at scale safely. Anchors on the agent-transition macro frame (8x growth, 88% incident rate, 14% security-approval rate) and the Legacy 12-month-in-production proof. Covers source receipts, owner checkpoints, audit trail, tenant isolation, bring-your-own LLM.
- [How Legacy Went 8x in 12 Months on Atlas](https://clarm.com/blog/articles/legacy-12-months-on-atlas/): Customer case study: Legacy (healthcare growth team) ran the agent-scale playbook over twelve months on Atlas. Email-only support deflection at go-live, then web chat, then voice agents, then CRM + kit-ordering integrations from the Clarm connector catalogue. Year-one total case volume across all channels: ~8x. Named owners and audit trails in place the entire twelve months.
- [Why I Left a Senior AI Role to Build Clarm Atlas](https://clarm.com/blog/articles/why-i-left-ai-career-to-build-clarm/): Marcus's founding story and the pattern behind Clarm: inbound demand was already present, but most teams could not answer or qualify it in the moment.
- [Clarm vs Plain: When Support Alone Is Not Enough](https://clarm.com/blog/articles/clarm-vs-plain/): Compares support ticketing with AI inbound conversion for technical teams where support conversations can reveal pipeline.
- [Best Tools to Convert Website Visitors Into Leads (2026)](https://clarm.com/blog/articles/best-tools-convert-website-visitors-to-leads/): High-intent buyer guide for converting anonymous website visitors into qualified conversations and pipeline.
- [Clarm vs OptinMonster vs ConvertFlow: AI Lead Qualification vs Static Forms](https://clarm.com/blog/articles/clarm-vs-optinmonster-vs-convertflow/): Explains why AI conversations capture intent that static forms and popups miss.
- [How to Capture and Qualify Inbound Leads Without a Sales Team](https://clarm.com/blog/articles/capture-qualify-inbound-leads-without-sales-team/): Shows how AI can answer first-touch questions, detect buyer intent, and route next steps without staffing live chat.
- [AI Inbound Lead Capture for Healthcare, Finance, and SaaS Teams](https://clarm.com/blog/articles/ai-inbound-lead-capture-healthcare-finance-saas/): Maps AI inbound to regulated and software teams with compliance, buyer intent, and routing needs.
- [AI Inbound for RevOps: Qualify and Route Pipeline Without More Headcount](https://clarm.com/blog/articles/ai-inbound-for-revops/): Connects AI qualification to routing, enrichment, and operational handoff for revenue teams.
- [AI Inbound for Heads of Growth: Turn More Traffic Into Qualified Pipeline](https://clarm.com/blog/articles/ai-inbound-for-heads-of-growth/): Explains why traffic without instant answers leaves pipeline on the table and how AI inbound closes that gap.
- [HIPAA-Compliant Website Chat for Healthcare](https://clarm.com/blog/articles/hipaa-compliant-website-chat-for-healthcare/): Covers BAA, PHI boundaries, no-training commitments, escalation, and compliance expectations for healthcare chat.
- [Clarm vs Drift: Clarm Atlas vs Conversational Marketing Playbooks](https://clarm.com/blog/articles/clarm-vs-drift/): Compares Drift and Clarm for teams deciding between human-led conversational marketing and AI-first inbound.
- [What Is Clarm Atlas?](https://clarm.com/blog/articles/what-is-an-ai-revenue-desk/): Defines the category: capture inbound, qualify buyer intent, and route revenue automatically across channels.
- [How to Respond to Inbound Leads Faster Than Your Competitors](https://clarm.com/blog/articles/how-to-respond-to-inbound-leads-faster/): Tactical guide to sub-5-minute response, instant answers, and routing high-intent visitors while motivation is high.
- [AI Lead Qualification vs Traditional Lead Scoring](https://clarm.com/blog/articles/ai-lead-qualification-vs-lead-scoring/): Compares pageview/form scoring with conversation-based qualification and buyer-intent extraction.
- [AI Chatbot vs Live Chat for B2B](https://clarm.com/blog/articles/ai-chatbot-vs-live-chat-for-b2b/): Decision framework for replacing or augmenting human chat with AI-first inbound qualification.
- [Inbound Pipeline Automation: The Complete 2026 Guide for B2B Teams](https://clarm.com/blog/articles/inbound-pipeline-automation-complete-guide/): Covers capture, qualification, enrichment, routing, measurement, and operational ownership for inbound pipeline.
- [Best Intercom Alternatives in 2026 for Technical Teams](https://clarm.com/blog/articles/best-intercom-alternatives/): High-intent alternatives guide for buyers comparing Intercom with AI-first inbound options.
- [The YC Founder's Guide to AI Inbound](https://clarm.com/blog/articles/yc-founder-guide-to-ai-inbound/): Playbook for founders turning launch traffic and early community activity into qualified conversations.
- [SOC 2 Compliant AI Chat for SaaS](https://clarm.com/blog/articles/soc2-compliant-ai-chat-for-saas/): Explains SOC 2 expectations, data controls, no-training commitments, and procurement needs for AI chat.
- [Best Qualified.com Alternatives for Lean B2B Teams in 2026](https://clarm.com/blog/articles/best-qualified-alternatives/): Compares AI inbound conversion options for buyers evaluating Qualified alternatives.
- [Slack Sales Alerts for High-Intent Visitors](https://clarm.com/blog/articles/slack-sales-alerts-for-high-intent-visitors/): Explains high-intent visitor alerts, Slack routing, and founder/sales handoff for revenue conversations.
- [AI Inbound for Open Source Companies](https://clarm.com/blog/articles/ai-inbound-for-open-source-companies/): Covers GitHub, Discord, docs, community support, and enterprise buying signals for OSS teams.
- [Visitor Deanonymization Explained: How to Know Who's on Your Site Before They Fill a Form](https://clarm.com/blog/articles/visitor-deanonymization-explained/): Explains visitor deanonymization, VPN limitations, privacy boundaries, and how intent signals supplement IP matching.
## Contact

- Contact page: https://clarm.com/contact/
- Chat: https://clarm.com
- Chat API: POST https://clarm.com/api/agent/chat with {"message":"your question"}
- Email: marcus@clarm.com (sales, press), support@clarm.com (product, privacy)
- Book a demo: https://cal.com/stormm/revenue-desk
- Y Combinator: https://www.ycombinator.com/companies/clarm
- LinkedIn: https://www.linkedin.com/company/clarm
- Twitter/X: https://x.com/clarm_ai
- GitHub: https://github.com/clarm