Skip to content
FidelicRoster →

Architecture

Sandboxed per client. Data stays on Anthropic.

How Fidelic deploys agents — and what that means for your data.

How a Fidelic agent reaches your Slack

Templates, customized by an agent, deployed in isolation.

Every Fidelic agent starts as a vetted template — a pre-built role definition with capabilities, a written constitution, and a published list of limits. The Roster is the catalog of these templates. Each one ships before any customer sees it, so when you hire, you are not waiting weeks for formation. You are hiring a known quantity.

When you hire, an automated configuration layer (itself a Fidelic agent) takes your brief from Tessa’s voice intake and customizes the template against it — pinning the agent’s tone to your brand, the people it should brief, the channels it should watch, the cadence it should follow. There is no human formation cycle. The customization is an automated step.

The customized agent then deploys into an isolated Anthropic-managed environment — one Anthropic project per customer, with the agent running on Claude. Your Slack workspace connects to that environment. Your data — messages the agent reads, files it summarizes, context it carries — flows from Slack to Anthropic’s infrastructure and back. It does not pass through or land on Fidelic-controlled servers.

Where your data lives

The questions every buyer asks, answered the same way every time.

These don’t change between calls. They’re written here once, in plain language, so your security team can read what we tell every customer.

What we depend on Anthropic for

We are downstream of Anthropic. We name what that means.

Fidelic’s architecture inherits more from Anthropic than from any other vendor. That makes the trade-offs easy to enumerate.

Limits, in writing

What we don’t claim.

  1. We don’t separately audit Anthropic.

    We trust Anthropic’s published compliance documentation, and you should verify it directly at trust.anthropic.com. We are a customer of Anthropic, just as you would be — we are not a Fidelic-side auditor of Anthropic’s controls.

  2. Fidelic doesn’t have an independent SOC 2 yet.

    The platform inherits Anthropic’s posture. Fidelic’s own organizational SOC 2 is a future commitment, not a current one. If your procurement requires a Fidelic SOC 2 attestation today, we won’t pass that filter.

  3. We are not zero-knowledge.

    Operational telemetry — token counts, error events, tool-call metadata — flows through Fidelic for billing, support, and tuning. The contents of your data don’t. If your security model requires zero Fidelic visibility into anything related to your deployment, this isn’t that.

  4. We can’t guarantee Anthropic’s roadmap.

    If Anthropic changes API access policies, model availability, pricing, or compliance posture, that propagates to Fidelic deployments. We track the changes and communicate them. We don’t control them.

  5. We don’t run on-premises.

    Every Fidelic deployment runs on Anthropic’s managed infrastructure. If your security policy requires on-premises AI — air-gapped, in-VPC, or in your own cloud account — Fidelic isn’t your fit, and that’s our honest answer.

Compliance and verticals

What to know if you’re regulated.

We are not your compliance officer. These are notes from buyers in regulated industries who deploy on Fidelic.

Where to next