I've been evaluating a few of the new AI agent platforms (CrewAI, LangGraph, etc.) for a potential CI/CD automation project. While the demos are impressive, I've hit a massive, unspoken wall: procurement and vendor management.
Suddenly, my clean infrastructure-as-code setup is threatened by a sprawl of new SaaS dependencies. Each platform wants its own API key, has its own pricing model (per-token, per-agent, per-hour), and its own data processing agreement. It feels like we're regressing to the pre-cloud era of managing dozens of individual vendor contracts, just to run a few scripts.
What does this mean for our current stacks? Consider the complexity it adds to simple security and cost controls.
* **Secret Management:** Instead of a few well-defined secrets for major cloud providers, I'm now looking at provisioning and rotating API keys for multiple AI agent services. My `vault` or `secrets manager` configuration is getting bloated.
```yaml
# Was: aws, gcp, maybe one LLM provider
# Now becoming:
secrets:
- openai-api-key
- anthropic-api-key
- crewai-api-key
- langsmith-api-key
- n8n-license-key
```
* **Cost Tracking:** Cloud cost tools are built for compute, storage, and network egress. They aren't designed to track and attribute millions of micro-transactions for "agent runs" or "workflow steps" across 3-4 different platforms. Forecasting becomes a guessing game.
* **Compliance & Lock-in:** Each new platform is a new data processor. Getting each one through legal/security review for enterprise use is a project in itself. And since these agents are built on proprietary orchestration layers, portability is low.
The promise was automation, but the overhead of managing these new vendors might cancel out the benefits. I'm starting to think a simpler approach—using a single, well-supported LLM API and writing our own orchestration logic in Python—might keep our infrastructure cleaner, even if it's more initial work.
Are others feeling this pain, or am I overcomplicating it? How are you integrating these tools without creating a vendor management nightmare?