PropXchain consumer app
The web app for PropXchain, a UK residential
property transaction marketplace, used by sellers, buyers and housebuilders.
Built with Vite, React and Tailwind. It reaches the PropXchain canisters on
the Internet Computer through the
@propxchain/core-client
package.
Screenshots
The landing page at propxchain.com.
A seller's transaction: the stages from sales pack to completion, the
listing details and what the buyer has done so far. Shown with a demo
account and synthetic data.
About this repository
This repository contains the consumer frontend for PropXchain. The code is
open source under the GNU AGPL v3 licence.
What you can do with this code:
- Read, study, and learn from the implementation
- Run it locally for development and evaluation
- Contribute improvements via pull requests
- Fork it under AGPL terms (see LICENSE)
What this code alone does not give you:
- A working property transaction platform. The backend canisters, regulatory
integrations and conveyancer panel are commercial and remain proprietary.
- Access to PropXchain's production infrastructure, which requires a
commercial relationship.
- The ability to process real transactions, which requires the HMLR Business
Gateway access and regulated panel relationships held by PropXchain Ltd.
PropXchain operates an open-core model: this frontend, including the seller,
buyer and builder portals, is open source; the backend platform and premium
add-ons are commercial products. This structure lets the frontend be openly
auditable and community-improvable, while the backend platform
operates under the commercial and compliance terms that property
transactions require.
If you want to use PropXchain to transact, visit
propxchain.com. If you want to build against the
platform's backend, see the API documentation.
Development
pnpm install
pnpm dev # Vite dev server on :3000
pnpm build # vite build + prerender marketing routes
pnpm test # vitest
pnpm lint
pnpm type-check
Copy .env.example to .env.local and fill in the values you have. Canister
IDs, the Supabase project and the Cloudflare Worker URLs are read from the
environment at build time. There is no offline mode: flows that need a
canister or a Worker need it configured.
Every migration in supabase/migrations that creates a public table must
grant privileges on that table explicitly, in the same file: service_role
always, authenticated if the app uses the table, anon only with an
-- anon: <reason> comment. Supabase stopped auto-granting new public tables
on 30 Oct 2026; CI enforces this with scripts/check-migration-grants.mjs.
Deployment
Pushes to main that change the app (not docs-only changes) build it once
and upload the same dist/ to both frontend asset canisters
(.github/workflows/deploy-frontend.yml):
Licence
GNU Affero General Public License v3.0 or later. See LICENSE.
@propxchain/core-client is licensed separately under Apache-2.0.
