How to Deploy CrewAI to Production

When you shift CrewAI agent crews from notebooks to production, their behavior changes. They need memory that lasts across runs, storage for outputs, and team-shared access. Without these, state resets after each task, limiting crews to one-offs. Production agents tackle ongoing jobs, such as customer support chats or data pipelines. Fastio workspaces support this: agents store files, search via RAG once Intelligence is enabled, and monitor activity feeds. Teams can scale CrewAI this way. Check Fastio Workspaces, Fastio Collaboration, and Fastio AI. Example: A research crew handles daily market data, saves to Fastio. Agents require API keys for MCP.

from crewai_memory import PostgresMemory memory = PostgresMemory(url="postgresql://user:pass@host/db")

• How to Deploy Hermes Agent in Production With DockerHermes Agent runs as a persistent background service inside Docker, exposing an OpenAI-compatible API on port 8642 and...
• How to Deploy OpenClaw with Docker: A Production GuideDeploy OpenClaw with Docker to make sure your AI agents run the same way in every environment, from your laptop to...
• LangGraph vs CrewAI: Which Multi-Agent Framework to Choose in 2026LangGraph and CrewAI are the two most-searched multi-agent frameworks heading into 2026. This comparison goes beyond...
• How to Integrate Fastio API with CrewAI WorkflowsSet up Fastio API with CrewAI workflows to create a shared workspace for agents. They upload outputs, preserve version...
• OpenAI Agents SDK vs CrewAI: Choosing the Right Agent FrameworkOpenAI Agents SDK and CrewAI solve multi-agent orchestration in fundamentally different ways. This comparison breaks...
• Best Tools for CrewAI Agents: Top Picks for 2026CrewAI agents need good tools to be useful. The framework handles coordination, but external integrations let agents...

More on this subject: Multi-Agent Systems (54 guides)

Follow this step-by-step checklist for CrewAI production. 1. Install with pip install 'crewai[tools]'. Pin versions like crewai==1.9.3 in requirements.txt. Use UV for CI/CD speed.

Services: Redis for memory, Postgres for history, LLM like OpenAI/Anthropic, Serper for search. Try Upstash or Supabase managed options. 3.

Dockerfile: dockerfile FROM python:3.11-slim WORKDIR /app COPY requirements.txt. RUN pip install -r requirements.txt COPY. CMD ["uvicorn", "main:app", "--host", "0.0.0.0", "--port", "8000"] Add health checks. 4. docker-compose.yml: yaml services: app: build:. ports: ["8000:8000"] depends_on: [redis, postgres] redis: image: redis:7-alpine postgres: image: postgres:16 environment: POSTGRES_DB: crewai 5.

Env Vars: LLM keys, DB URLs, memory settings. 6.

Observability: LangSmith callbacks. 7.

Local Test: docker compose up. 8.

Deploy: Render, Railway, Fly.io. 9. 10. CI/CD: GitHub Actions with ruff lint, pytest, bandit scans. 11.

Health: /health endpoint for agent/DB status.

Single-container prototypes work fine, but production needs auto-scaling, managed DBs, and reliability. Compare options:

Railway suits most CrewAI apps with built-in scaling, Postgres, Redis. Add via railway add.

For Kubernetes, use this Deployment + HPA:

apiVersion: apps/v1
kind: Deployment
spec:
  replicas: 3
  template:
    spec:
      containers:
      - name: crewai
        resources:
          requests:
            cpu: "100m"
            memory: "256Mi"
        envFrom:
          - secretRef:
              name: crewai-secrets
---
apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
spec:
  scaleTargetRef:
    kind: Deployment
    name: crewai
  metrics:
  - type: Resource
    resource:
      name: cpu
      target:
        type: Utilization
        averageUtilization: 70

Serverless: Lambda for <15min tasks, SQS queues, DynamoDB state.

Celery + Redis for task queues: celery -A tasks worker -l info -c 4.

LLM handling: tenacity backoff, circuit breakers.

Fastio takes file I/O load off agents via MCP uploads.

Deploy CrewAI Agents Today

Persistent storage, a consolidated MCP toolset, and RAG search for CrewAI agents in production. Built for agentic deployment workflows.

Start 14-Day Trial

CrewAI lacks native file persistence. Fastio workspaces handle it. Agents create orgs/workspaces via API and upload via MCP tools over HTTP/SSE, no local storage needed. Once Intelligence is enabled for the workspace, it indexes files for RAG. Agents ask "Summarize last report" and get cited answers. Fastio offers a 14-day Business Trial requiring a credit card, with plans starting at Starter ($29/mo). Ownership transfer passes control to humans, agents keep admin. Example: Agent sets up client data room, transfers to PM. Human accepts by email.

Fastio logs track uploads, views, and changes. The WebSocket events feed alerts on changes and triggers crews. Workflow: CSV upload -> event -> research crew -> report back. Pair with LangSmith for traces. Granular permissions and file version history prevent multi-agent conflicts.

Memory loss? Check Redis/Postgres connections and health. LLM limits? Tenacity retries + Celery queues. File conflicts? Rely on Fastio version history and permissions. Scaling hangs? DB pool exhaustion, add pgbouncer. Start with logs: crewai --verbose, dashboards, LangSmith. 1%.