ZekaForge's AI assistant runs on Claude. You can reach Claude two ways — the Anthropic API directly, or Amazon Bedrock — and ZekaForge supports both behind one adapter. The models are the same family; the difference is operational.
Data residency and compliance
With Bedrock, requests stay inside your AWS account and chosen region, which simplifies data-residency and compliance stories for enterprise buyers. The Anthropic API is a separate vendor relationship with its own data-processing terms.
Latency and regions
Bedrock lets you pick a region close to your workloads. The Anthropic API is straightforward to start with and often fastest to adopt for a small team.
Cost and quotas
Both are usage-priced per token. Bedrock consolidates spend into your AWS bill (useful when you have committed spend or credits); the Anthropic API bills separately. ZekaForge tracks per-tenant token usage either way so quotas are enforced consistently.
Credentials
- Anthropic API: an API key stored in environment variables or Secrets Manager.
- Bedrock: no long-lived key — the app uses an IAM role with least-privilege
bedrock:InvokeModelpermissions.
How ZekaForge abstracts it
A single interface exposes the same features — explain, prioritize, summarize — across providers, plus a demo driver that returns labeled sample analysis when nothing is configured. Switching providers is a configuration change, not a rewrite.
A reasonable default
If you already run on AWS, start with Bedrock to keep data and billing in one place. If you want the fastest path to a prototype, start with the Anthropic API and switch later — the adapter makes that painless.