Crewai Enterprise And Deployment

Operator builds a Crew in code, then redeploys to CrewAI Enterprise UI Studio. The Studio reads from a connected git repo.

Deployment binds to a specific git ref (commit SHA preferred over branch). Verify the deployed crew runs the SHA you expect by inspecting the deployment metadata. Pin the ref for prod — branch tracking drifts under concurrent merges.

Operator stores OPENAI_API_KEY and SERPER_API_KEY in CrewAI Enterprise's secrets manager.

Secrets are encrypted at rest and injected into the crew's environment at runtime — never logged in run output. Verify by reading a run log and checking the secret value does not appear. Rotate via the UI Studio + invalidate the old key at the provider in lockstep.

Enterprise dashboards show runs, costs, and traces. Operator wants to export traces to their own OTel collector.

Span schema for downstream exporters is [REQUIRES-VERIFICATION] — confirm the current export shape before pinning consumers. Wire the exporter at deployment config; tag spans with run_id, crew_id, agent role, task id. Don't assume vendor schema is stable across releases.