• Projects 32
  • Rating 5.0
  • Rating 8 010

Budget: 4000 USD Deadline: 14 days

Building a multi-tenant AI support platform where every conversation routes through an LLM, gets logged, and feeds back into quality metrics — the architecture decision that matters most here is whether the AI layer is synchronous (fine for low volume) or async with a task queue like Celery + Redis, which I'd go with to handle burst load without blocking FastAPI responses.

Concrete plan: FastAPI app with async endpoints, PostgreSQL for structured data (conversations, agents, tickets) plus pgvector for semantic search over your knowledge base. OpenAI API calls go through a worker queue with retry logic and idempotency keys so a failed webhook never double-charges or drops a message. Docker Compose locally, ECS or Fargate on AWS in prod, with secrets in Parameter Store.

One risk a junior misses: OpenAI rate limits under concurrent load. I'd add a token-bucket rate limiter per tenant and graceful fallback to a canned response so the platform stays responsive even when the API throttles.

What's the expected concurrent user volume, and do you need voice synthesis integrated from day one or is that a phase-two feature?

  • Projects 3
  • Rating -
  • Rating 981

Budget: 5000 USD Deadline: 30 days

Hi,
I’m interested in long-term collaboration on your AI customer support platform.
Proposed start:
• Stack: Python + FastAPI + PostgreSQL + OpenAI + Docker (+ AWS for deploy)
• Phase 1 (MVP, 10–14 days): REST API, ticket/conversation storage, AI chatbot endpoint, auth basics, Docker, OpenAPI docs
• Then ongoing development: integrations, AWS, improvements, monitoring
Rate: $30–35/hour
or Phase 1 fixed: $1,200–1,500 (agreed scope)
Before coding, I’d clarify:
1. FastAPI or Django preferred?

Proposals concealed

The list does not show proposals concealed by the client or freelancer with a Plus profile, as well as proposals violating rules