Xconect Reference Host

Start with one calm question, then enter the marketplace.

This page stays intentionally stateless, but the experience should still feel like a real tenant entry flow. Name and email stay browser-local here; the stable subject identity comes from the gateway resolve flow, so the same email returns to the same subject.

1
Identify the tenant subject Use name + email only, without a login system yet.
2
Choose the launch surface Marketplace or single xapp, depending on the demo you want to show.
3
Open the tenant runtime Install/update/payment resume stays in the shared SDK flow.
What this shows Tenant-side marketplace publish/embed wiring, install/update/uninstall mutations, and payment return resume behavior, all through the shared embed SDK.
What this intentionally avoids No local auth, no tenant database, and no extra identity framework. This stays a reference seam, not an application shell.
Tenant intake

Who is entering this tenant experience?

Stateless bootstrap, stable subject
Question 1 of 2

Use the person who should own the marketplace state. The same email resolves to the same subject again.

Question 2 of 2

Choose how much framing the tenant host should keep around the marketplace or a single xapp.

Direct-open one deployed xapp without the marketplace shell.
Open backend reference