XKOVA Docs
Try the Demos
Two demo surfaces show the same rails from both sides, over one shared, hosted demo tenant: Plover Credit Union. The Plover operator console is the staff view; the Plover member app is the customer view. Nothing runs on your machine, and nothing you do in the demo affects your own workspace.
The two surfaces
| Surface | What it is |
|---|---|
| Plover operator console | The workspace console signed in to the Plover Credit Union demo tenant, where staff manage payments, treasury, compliance, and tokens. |
| Plover member app | The customer-facing front end where members sign in, hold balances, and send money over the same tenant. |
Enter the demo
The demo is entered from the console: on the signup intent screen, choose Try the demo. That takes you to the shared demo chooser (no signup of your own required, and it does not set up or alter your own workspace). From the chooser you pick a surface: enter the operator console as demo staff, or the member app as a demo member.
What to try
- As an operator: watch a payment move through queued, pending, and success on the Payments list; triage the compliance queue; open Treasury and walk a transfer's draft, sign, execute journey. See the Operator Onboarding guide for what each area does.
- As a member: sign in to the member app as a demo member, check balances, and send money; the signing ceremony you complete is the same non-custodial flow your own members would use. See the Non-custodial Model.
- Both at once: send from the member app, then find the same payment in the operator console's list; that round trip is the whole product in one minute.
Next
When you are ready to build against your own workspace, follow the Quickstart, and see Local Development for pointing your local app at the hosted sandbox.