VeUP
← All case studies
Agentic AI Consulting Services · Agentic Support (RAG + Live Tool-Use)
ClusterPOS wordmark

ClusterPOS empowers its support team with an AI agent on Amazon Bedrock

RAGEmbeddings & vector searchAgentic workflowsModel routingInfrastructure-as-code foundationInfrastructure observabilityDay-2 runbooks & team enablementCentralized workforce identityPrivate connectivity & network isolationStanding cost-optimization mechanismData residencyObservability-gap assessmentManaged billing & resellSecrets management & credential elimination
0 → production
first GenAI system — a self-hosted agent platform on Bedrock
4 engagements
returned three times after handover, then managed services
Sub-800ms
knowledge-base retrieval — 1–2s end to end, beating the SOW SLA
ClusterPOS point-of-sale product screenshot
Amazon BedrockNova ProAWS FargateRDS + pgvectorCloudWatch

Production OpenWebUI Retrieval-Augmented Generation chatbot on Amazon Bedrock for a European SaaS retail point-of-sale platform.

The customer

ClusterPOS is a European SaaS retail point-of-sale platform serving small-to-medium retail businesses. Their support workflow ran through a Zoho-hosted knowledge base — a static documentation tree with no conversational, grounded assistance — which meant linear support-headcount growth as the customer base expanded.

The challenge

ClusterPOS needed to deflect repeat support questions, accelerate time-to-resolution, and stay competitive against retail-POS rivals increasingly shipping AI-assisted in-product help. The team had no prior Generative AI capability in production and needed an AWS partner to take them from zero to a production chatbot within a sub-three-week build window.

The solution

VeUP designed and delivered a production OpenWebUI chatbot grounded on the customer's Zoho knowledge base, with Amazon Bedrock as the inference plane and Amazon Nova Pro as the production primary foundation model. The Bedrock integration was built model-toggleable from the start, so ClusterPOS can bring new models into production without redeploying. Live POS data is reached through OpenWebUI tool/function-calling, letting end-users ask grounded questions over both static documentation and live operational data.

The production deployment runs in the customer's AWS Canada (Central) region (ca-central-1) across a Multi-AZ VPC, with Application Load Balancer + ACM TLS at ingress, ECS Fargate hosting the OpenWebUI and VeUP-forked Bedrock Access Gateway, and Amazon RDS for PostgreSQL with pgvector for application state plus the RAG index. The chatbot cut over to production in November 2025; a POS integration extension followed in May 2026.

Architecture

The ClusterPOS support agent, end to end — from the original static-KB support workflow through to the production Multi-AZ VPC on Bedrock Nova Pro, with the RAG and live-POS tool surfaces, security, and observability planes.

Cluster Systems ClusterPOS — target state on AWS. Multi-AZ VPC in ca-central-1 with public-subnet Application Load Balancer plus ACM TLS, private app-tier ECS Fargate task running OpenWebUI and a VeUP-forked Bedrock Access Gateway, private data-tier Amazon RDS PostgreSQL with pgvector plus Amazon EFS and AWS Backup, Amazon Bedrock (Nova Pro, Nova Lite, Claude Sonnet, Titan embeddings), AWS IAM, Secrets Manager, KMS, and CloudWatch, external Zoho KB and ClusterPOS POS API tool surfaces, and Google Workspace SSO.
The production estate — a Multi-AZ VPC in ca-central-1, with the chatbot on Fargate, its knowledge in RDS and pgvector, and Bedrock doing the reasoning.

Where it started

Assessed baseline · new implementationSoftware & Internet — retail point-of-sale SaaS · Europe · AWS infrastructure in ca-central-1
Starting point
Support ran on a static knowledge base

A Zoho-hosted documentation tree — no conversational assistance for staff or end users; support agents self-served by browsing docs.

Starting point
POS answers meant manual lookups

Staff queried the live ClusterPOS system directly for transaction, inventory, and store-status questions — no tool-using agent surface over live data.

Constraint
Self-host / data-residency requirement

Ruled out third-party SaaS chatbot vendors outright, and drove a custom build on AWS instead of an off-the-shelf support bot.

Driver
Support headcount tracked customer growth

Linear support-headcount growth with no deflection lever in place to bend the curve.

Gap
No GenAI capability in-house

No prior GenAI or agent workload existed — the agent framework, RAG, tool use, and IAM scoping all had to be sourced externally.

A new implementation — there was no prior chatbot or agent architecture to migrate. This is the starting context as assessed at engagement start.

Production outcomes

KPIResult
RAG retrieval latencySub-800 ms across a 600-document staging corpus, with end-to-end answers in one to two seconds — well inside the committed service levels (p50 ≤ 5s, p95 ≤ 10s).
Continued engagementAfter handover, Cluster Systems came back to VeUP three more times — for RDS MySQL 8 with DDoS and WAF protection, an IAM security review, and an NLB-to-ALB migration with WAF — then signed on for ongoing managed services.
AWS services in production
Amazon Bedrock (Nova Pro primary)AWS FargateAmazon RDS for PostgreSQL + pgvectorAmazon EFSApplication Load BalancerAWS Certificate ManagerAWS Secrets ManagerAWS IAMAWS KMSAmazon CloudWatchAWS Cost Explorer
External integrations
Zoho KB ingestionGoogle Workspace SSO (OIDC/SAML)ClusterPOS POS API