Published, not exposed.
shop.acme.com, not tenant42.vendor.app
Every portal gets an instant hostname the moment you publish — and bringing your own domain is a guided flow with managed TLS; nothing routes until domain ownership is proven.
Even anonymous has a badge
Anonymous visitors run as a real least-privilege identity through the same record- and field-security engine; signed-in customers see exactly what their account allows — their orders, their invoices, their cases.
Customer service, storefront, employee desk — same designer
Design pages with the platform’s own rendering engine; brand with theme tokens; draft and publish with versioning and a one-click kill switch.
Publish is a toggle, not a deployment.
The capabilities, stated plainly.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Portals |
|---|---|
| Multiple portals per tenant | Native |
| Instant hostnames on publish | Native |
| Custom domains with managed TLS | Native |
| Draft-to-publish with versioning | Native |
| Published live-data views with caps | Native |
| Governed anonymous access | Native |
| Self-service signup with invite rails | Native |
| Customer sign-in scoped to their records | Native |
| Visual portal builder | Native |
| Theme tokens | Configurable |
| One-click kill switch | Native |
Everything in Portals.
The questions evaluators ask.
Who are the portals for — customers, partners, employees?
All three. One tenant runs multiple portals — a dealer portal, a customer portal, a partner portal — each with its own on-off switch, and the same builder turns inward for employee portals and internal tools. Every portal composes visually in the designer, goes live on an instant hostname, and can move to your own domain with the certificate managed for you. Explore xMatix Portals.
Do portal users see only their own data?
Yes. Signed-in customers see their orders, invoices and cases scoped to the person who logged in — nothing else. Published data views carry a chosen filter and cap, so visitors see current data but never more than was granted. Anonymous visitors get the least access possible, enforced by the same security engine that guards your staff, and signup runs through invite rails that never leak who else has an account.
Can portals run on our own domain?
Yes — shop.yourbrand.com, with managed TLS: paste two DNS records and you are live, certificate handled for you. Until domain ownership is proven, nothing routes anywhere. Publishing is equally deliberate — changes stay in draft until you say go, every publish is a version you can point back to, and a one-click kill switch takes the whole portal offline instantly when it matters.
Does commerce share the same catalog and stock?
Yes — the storefront sells the same catalogue, prices and schemes as the rest of the platform, scoped per store so each dealer sees their own assortment. Credit control checks the buyer's real outstanding at save, orders flow into the same fulfilment and invoicing pipeline, and online payments land in the same collection flow finance already runs. Explore xMatix Commerce.
What makes a good B2B dealer ordering portal?
Truthfulness under the surface. A B2B dealer ordering portal earns adoption when every screen is a live window onto the system of record: each dealer sees their own catalogue at their negotiated terms, schemes price in the cart by the same rules invoicing applies, credit is checked against the real outstanding at order save, and despatch, statement and claim status answer themselves. A portal fed by uploads drifts from reality and dealers go back to phone calls within a quarter.
