Feature availability

Reviewed against the repository on 13 September 2026. Your deployed version may differ. This page records rollout gates; Features explains controls and behaviour. A landing-page animation is not proof of activation.

Implemented in the development environment

The configured dev backend supports consumer sign-in and joining, browser memberships and QR identity, merchant setup, stamps/redemption, referral rewards, saved branding, member and outlet reporting, published listings, team access and multiple brands. Production rollout and authenticated end-to-end verification are separate.

Additional gates and known boundaries

The account menu, animated dashboard, stamp cards and phone screens on public pages are demonstrations. Entering details in a signup preview is not a saved profile, opening a sample card is not joining, and a notification illustration does not mean a push message was sent.

Capability	Check before promising availability
Programme operations	Require authorised access and an active subscription. Free workspace creation does not activate operations.
Capacity	Enforced in dev. Additional outlets and email require explicit allowances.
Kardy network	Only eligible, published live data appears. Setup alone does not publish a listing; samples require explicit demo mode.
Email broadcasts	Drafts, consent and the queue are implemented. Sending starts disabled; paid provider setup, server/backend gates and recipient allowance are required. No live scheduler or delivery-confirmation webhooks are enabled.
Merchant MCP	Read-only OAuth and manual-key access is implemented in dev. Owner approval and an active subscription are required; there is no consumer MCP.
Team access	Share invitation links manually; automatic invitation emails are not connected. Ownership verification needs working auth email delivery.
Native wallets	Signing is implemented but issuance starts disabled until issuer credentials and scanner readiness are verified. Automatic pass updates are not implemented.
PWA claim notifications	The iPhone-style coffee-claim notification is a labelled concept preview. Production push delivery is not implemented. Confirm redemption through staff and current Kardy data.
Card design	Saved browser designs are supported in dev. Reward-specific icons and preview stamp counts remain illustrative.
Reporting	Date-filtered totals and complete-day graphs are connected in app code. Incomplete reads show unavailable; authenticated deployment verification is separate. Demo charts use sample data.

Activities and Live view are implemented in app code: searchable audit history and a store globe with checks every 15 seconds while visible. This is not an instant stream or customer-location tracker. Demo feeds are static; authenticated deployment verification is separate. For an account-specific problem, use Help. Do not share an Owner’s login or assume a successful preview is a saved transaction.

Branding and hosting

The product is Kardy, using getkardy.com as its chosen public domain. The merchant workspace uses merchant.getkardy.com; documentation is intended for docs.getkardy.com. These configured destinations do not establish that DNS, hosting, auth redirects or email delivery have been activated. The production backend’s display name is now Kardy. The persistent development branch remains separate. Renaming the product did not rotate QR identifiers, credentials or issued passes.

​Implemented in the development environment

​Additional gates and known boundaries

​Branding and hosting

Implemented in the development environment

Additional gates and known boundaries

Branding and hosting