A warranty vault and QR serialization engine where counterfeit and duplicate claims are mathematically impossible

Consumer hardware and electronics brands bleed margin through warranty fraud and manual support friction.

The standard registration experience is broken on both sides. For buyers, preserving a thermal paper receipt for two years in a drawer is unrealistic — when a device fails, the receipt is faded or lost. For brands, asking customers to upload invoice photos creates an expensive manual review queue where human support agents spend hours squinting at receipts to verify store names, purchase dates, and serial numbers.

Worse, legacy systems trust client-side claims or use sequential serial numbers. A malicious buyer who buys one legitimate speaker can photocopy the invoice and register several replacement claims. Fraudsters guess sequential numbers on retail shelves and claim warranties before genuine buyers even open the retail box. And during high-traffic flash sales, concurrent web requests often exploit race conditions to register the exact same serial number across two different accounts.

A multi-tenant warranty and serialization platform engineered from the ground up to make counterfeit and duplicate registrations physically impossible.

At the core is an unforgeable QR serialization protocol. Each unit receives a cryptographically randomized serial token (KPR-CURA-SPK-3001) etched onto the product packaging and hardware chassis. When a customer scans the QR code with their phone camera, the system performs an atomic conditional claim in PostgreSQL under a row-level lock. Even if two buyers attempt to claim the identical serial number at the exact same millisecond, the database serializes the transactions — the first claim commits, and the second is immediately rejected with a deterministic conflict error.

Multi-tenant security is enforced at the database kernel using PostgreSQL Row-Level Security (RLS) with three strictly isolated roles:

• keepr_migrator: Owns database DDL and runs migrations; never used by web traffic.
• keepr_app_role: The runtime API role with zero DDL privileges, restricted to scoped tenant queries.
• keepr_definer_owner: Executes audited SECURITY DEFINER functions so anonymous public QR scans can verify product authenticity without exposing brand tenant records.

The backend is built on Fastify, BullMQ, and Redis, with Next.js powering both the mobile customer vault and the brand operator dashboard. BullMQ workers process background SLA countdowns, warranty expiry events, and rate-limited webhook dispatches to external ERPs without blocking the Node.js event loop. Brands can configure protection plans, issue batch recalls, and manage warranty claims through an integrated Kanban helpdesk.

The platform is running in production-grade staging with complete test coverage: 28 backend integration tests and 82 browser E2E test suites verifying every role transition, claim condition, and RLS boundary.

The entire 4-container production stack (API, Web client, PostgreSQL 16, and Redis 7) is hardened with read-only root filesystems and automated zero-downtime GitHub Actions deployments, running with an ultra-lean memory footprint of under 110 MB RAM.

Available for Brand Deployment: Keepr is available as a dedicated, fully managed platform for consumer electronics and D2C brands. Rather than spending six months building internal warranty tooling, brands can deploy a dedicated, white-labeled instance in under 48 hours.

You can test the live interactive demo right now at keepr.codeworth.codes using seeded test accounts (admin@curaaudio.com / Password123!). If you want Keepr deployed for your brand, contact Swayam directly on WhatsApp to set up an onboarding pilot.