Brass Armadillo · Web POS
Your Access database. Modern web. Same workflow.
A purpose-built POS and back-office for Brass Armadillo, replacing the Access front-end with a multi-station web app on cloud-standard infrastructure — without changing how your team rings a sale.
Six stores · One system · Same data layer (Azure SQL → managed Postgres on cutover)
What we're building
281 features mapped from your Access front-end, your sales screen, your reports, and six competitor POS systems — distilled into three concrete shifts.
01
Replace the Access UI
Same workflow your cashiers know — dealer ID lookup, multi-line sales grid, manual discount column, payment methods, suspended sales. Web-based, multi-station ready, no per-station install.
02
Keep your data
Your existing Azure SQL data is the source of truth. We mirror your tables one-to-one, then move to managed Postgres on YittBox infrastructure on Dan's signoff — clean migration, no data loss, no lock-in.
03
Add what's been missing
GoAntiquing JSON pull, real-time projection vs actual, audit-grade reconciliation, mobile-friendly manager views. The reports your team has been doing by hand, automated.
Your sales screen, on the web
We're not reinventing the workflow. Dan's annotations on your current screen are the spec — the web version preserves every column, every tab, every payment method.
Working POC
Multi-station web sales screen
Same grid, same payment methods, same workflow — running in any browser at any station, all writing to the same database in real time.
Open the live demo →Phoenix store · 6 stores wired
Why we built it this way
Dan raised four concerns on May 13. Here's how the architecture answers each one.
- Concurrent stations — can it handle 5-6 stations submitting at once?
- Yes — and many more. Six stores × six stations is ~36 concurrent cashiers chain-wide. Modern Postgres handles thousands of writes/sec with row-level locking. We'll run a load test on a stripped POC endpoint to put a real number on it before the contract closes.
- Architecture — local install or browser-based? AWS or Azure?
- Browser-based, AWS-hosted. No per-station install, no Citrix gymnastics. Standard Next.js + Postgres + RDS on AWS, behind Traefik with TLS. Stations are just Chrome on a Windows box.
- Data backup — what about restorability?
- RDS automated backups + point-in-time recovery, cross-region snapshot copy, retention policy on your timeline. Backups are tested with a quarterly restore drill, not assumed to work.
- Credit card processing — works with our existing processor?
- Yes. Your processor already handles auth and PCI. We integrate via the connectivity spec they provide. No merchant-account churn, no PCI scope expansion on your side.
Built by YittBox
Same team behind Yittzy, the multi-store e-commerce platform, Yittrix CRM, and a fleet of internal tools running for clients across the Midwest. Brass is shop #44 372 in the YittBox project ledger.
Standards stack
- · Next.js · TypeScript · React
- · Postgres on AWS RDS
- · Traefik · Docker · GitHub Actions
- · NextAuth (SSO-ready)
The numbers
- 281 features mapped from your Access DB
- 23 functional areas
- 6 competitor POS systems reviewed
- 6 stores wired into the schema