XconectB Reference Host

Start with one calm question, then enter the marketplace.

This is the PHP reference tenant entry for the same marketplace contract as xconect. Name and email stay browser-local here; the stable subject identity still 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 validation flow.
3
Open the tenant runtime The browser host stays shared while the backend contract is plain PHP.
What this shows Tenant-side marketplace publish/embed wiring, install/update/uninstall mutations, and payment return resume behavior against a second backend stack.
What this intentionally avoids No local auth, no tenant database, and no extra identity framework. This stays a contract-validation seam, not an application shell.
Tenant intake

Who is entering this tenant experience?

Plain-PHP backend, shared browser host
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