ClusterPOS empowers its support team with an AI agent on Amazon Bedrock
ClusterPOS runs a multi-tenant retail point-of-sale SaaS for restaurant and retail operators. VeUP’s engagement added a grounded-AI assistant to that product the way a SaaS company has to: designed for multi-tenancy on Amazon ECS Fargate and Amazon Bedrock, delivered against hard acceptance criteria — latency SLOs, a zero-critical-alarm gate, and a proven backup-restore — and operated as a durable part of the platform, not a bolted-on demo.
The challenge
For an ISV, adding AI to a live multi-tenant product is a different problem from standing up a chatbot. The assistant had to run inside ClusterPOS’s SaaS operating model: predictable unit economics on shared infrastructure, tenant data kept clean, credentials and integrations (the Zoho knowledge base, and later live POS data) managed safely, and the whole feature held to the same reliability bar as checkout — because a POS vendor’s customers do not distinguish “the AI is down” from “the product is down.” ClusterPOS needed the feature shipped to production with acceptance criteria it could hold its own platform to.
The solution
VeUP designed and delivered the assistant as SaaS infrastructure. The serving layer runs on Amazon ECS Fargate behind an Application Load Balancer with AWS Certificate Manager TLS — no instances to manage, capacity scaled to demand, CPU reservations measured and right-sized after launch. Amazon Bedrock (Amazon Nova Pro) provides the model layer with no keys or GPU fleet to operate; Amazon RDS for PostgreSQL and Amazon EFS carry application state; AWS Secrets Manager isolates integration credentials; AWS KMS encrypts at rest. The build was held to explicit acceptance criteria and proven at a formal gate: latency percentile targets under nominal load, zero critical CloudWatch alarms, grounded answers citing their sources from the seeded knowledge base, and a backup-restore test into staging passed via AWS Backup. The engagement continued past launch into solution-architecture support as the assistant’s scope grew.
Production outcomes
| KPI | Result |
|---|---|
| Latency SLOs | End-to-end latency at nominal load met the committed targets: p50 ≤ 5 seconds and p95 ≤ 10 seconds — SaaS-grade acceptance criteria for an AI feature. |
| Reliability gate | Zero critical CloudWatch alarms through the acceptance window; backup-restore into staging verified as a delivery milestone. |
| Unit economics | Fargate runtime cost tracked from launch; initial CPU reservations found over-provisioned and right-sized down — a measured cost-optimization pass rather than a set-and-forget deployment. |
| Lessons & continuation | Treating an AI feature as SaaS engineering — acceptance criteria, restore tests, SLOs, and post-launch right-sizing — is what makes it durable; the platform has since grown a live POS data integration on the same foundations, with ongoing VeUP solution-architecture support. |