> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getkardy.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What's new

> A snapshot of Kardy's current experience, with links to the complete feature guides.

## 13 September 2026 · Current product snapshot

This summary describes the local repository, not a production release notice.
Check [feature availability](/availability) before relying on a deployed capability.

### Kardy and Kardy Network

Brown is now **Kardy**. The chosen public domain is **getkardy.com**. The
`kardy | MERCHANT` identity marks the business workspace; `kardy | NETWORK`
marks public rewards discovery. They are two surfaces of the same product,
not separate customer accounts.

[Kardy Network](/features/kardy-network) lets customers search eligible published
rewards, browse categories and locations, inspect shops and continue to joining.
An empty marketplace stays empty rather than being filled with fictional offers.

### Account setup and previews

Signup separates email entry from personal details and password setup. Phone
input is country-aware and validated on submission. Merchant signup includes a
read-only workspace preview; uneditable example actions appear as placeholders.
The login illustration pairs a merchant dashboard with the consumer phone view.
Neither preview signs in, saves a profile, issues a pass or creates a membership.

See [Accounts and access](/accounts/overview) and [Joining a programme](/customer-journey/join).

### Consumer wallet

The [browser wallet and PWA](/features/browser-wallet) remains the place to review
current memberships, stamp balances, rewards and recent activity. Its mobile
navigation links to Wallet, Places, Rewards and Activity. Adding Kardy to the Home
Screen is separate from saving an Apple Wallet or Google Wallet pass.

The coffee-claim demonstration now uses a consumer PWA screen. Its iPhone-style
notification is a **concept**, not an implemented push-delivery service. Native
passes identify the member; they do not automatically update stamp balances.

### Merchant operations

* [Overview](/features/analytics): shared date/store filters, visits and redemption
  totals, trend comparisons, location performance and current member progress.
* [Activity list](/features/activities): member search, store/action filters,
  pagination and recorded event details.
* [Live view](/features/live-view): store globe and recent events, checked every
  15 seconds while visible—not a customer-location tracker.
* [Rewards](/features/rewards) and [referrals](/features/referrals): programme rules,
  eligible outlets, performance and recorded claims.
* [Branding](/features/branded-cards), [join pages](/features/join-pages) and
  [QR signs](/features/qr-signs): saved customer-facing design and joining materials.
* [Members](/features/members), [outlets](/features/outlets),
  [team access](/features/team-access) and [multiple brands](/features/multiple-brands):
  organisation-scoped management with role boundaries.

Destructive controls use red styling and confirmation where provided. This does
not make every item deletable: scans and redemption events remain append-only.

### Services with activation requirements

[Native wallet issuance](/features/native-wallets), [broadcast delivery](/features/broadcasts)
and [billing](/merchants/billing) need the relevant deployment configuration.
[Merchant MCP](/features/merchant-mcp) is scoped and read-only, requires Owner
approval and an active subscription, and does not expose consumer data.
[Usage allowances](/features/usage-limits) remain finite and enforced independently
of what a preview displays.