Every team can ship. Every change is on the record.
One organization for every storefront you run. Your people sign in through your identity provider, each with the permissions their job needs, and every release, test and refund is written to one audit log.
Hollis & Pine's audit log in Mtrix, under Settings, Security, Audit log. Newest first: Sep 17, 14:32, Marcus Obi shipped experiment "Washed linen first" to 100%. 14:18, Jonas Becker published hollisandpine.eu. 14:05, Theo Grant was not allowed to publish hollisandpine.co.uk, shown as a denied row. 13:51, Dana Whitfield changed Sophie Lindqvist's privileges, with the change View Audit Log from No to Yes. 13:40, Priya Raman refunded order #HP-48211 for $148.00. 13:22, Sophie Lindqvist signed in to Hollis & Pine through Okta over SAML. Each row lists the event type, where it came from, the project and the privilege it needed.
Every storefront,
one organization.
Each storefront is its own project, with its own pages, experiments and analytics. They share one login, one contract and one set of meters, and a big week on one of them never switches anything off.
Hollis & Pine’s settings in Mtrix. First, the project switcher at the top of the app lists four storefronts, Hollis & Pine US, UK, EU and Outlet, with US marked current, and Settings › Projects lists the same four with US active and a Switch project button on the others. Next, Settings › Usage for September 2026: 1,386,420 monthly unique visitors, 48,210,300 monthly events, 612,480 session replays and 2,940 agent minutes, each with no cap on Enterprise; four projects of unlimited; a twelve-month chart; and monthly events by project, 27,962,000 for US, 10,606,300 for UK, 6,749,400 for EU and 2,892,600 for Outlet. Last, Settings › General shows the organization slug hollisandpine, the display name Hollis & Pine and the data region, European Union, which is set when the organization is created.
Sign in once.
See only what your job needs.
Connect your identity provider over SAML and require single sign-on for everyone on your domain. Then give each person a role, and switch individual permissions on or off, from publishing a storefront to refunding an order.
- Single sign-on, required if you want it. Anyone on your verified domain signs in through your identity provider, such as Okta or Microsoft Entra ID.
- Five roles, 29 permissions. Start from Admin, Project Manager, Member, Editor or Tester, then change what one person can do. Permissions are enforced on the server, not just hidden in the interface.
- A login for everyone. Seats are unlimited, so agencies, contractors and every regional team get their own account instead of a shared one.
The Mtrix settings for Hollis & Pine, in three steps. Security, Single sign-on: Okta is connected over SAML 2.0, with its sign-in URL, entity ID and certificate expiry, the verified domain hollisandpine.com, and the switch Require single sign-on being turned on. Members: eight people with their roles, and an invite sent to rosa@northmark.agency as a Tester, which appears as a pending invite. Privileges for Sophie Lindqvist, a Project Manager: her role's permissions are ticked, View Audit Log is ticked as well, and the privileges are saved.
Stage every release.
Roll back from the history.
Publish a storefront to staging and check it on its preview address, then send it to production. Every deploy is kept with the person who made it, so an earlier build can go live again in one step.
The Mtrix builder on the Hollis & Pine UK storefront, with its homepage on the canvas, in three steps. First, the Publish menu lists two destinations, Staging at hollisandpine-uk.mtrix.io and Production at hollisandpine.co.uk; Production is unticked, the release goes to staging, and the progress list runs through compiling the site, pushing to the CDN, building the site and going live. Second, for a member without permission to publish, the Publish button is disabled and says "You do not have permission to publish this website". Third, the Deploy panel shows the live build, the preview address and the deploy history, each build with its commit and the person who published it, one of them a failed build; a production build from September 12 by Jonas Becker is chosen with "Roll back to this build", and the dialog asks "Roll back to this deployment?", explaining that the production website reverts to that version, rebuilds automatically and keeps its commit history.
What your security review
will ask, answered.
Your team will send a questionnaire. Here is what it will find, and where each answer lives in Mtrix.
| Question | Answer | Where it lives |
|---|---|---|
| How do people sign in? | Through your identity provider over SAML 2.0, and you can require it for your whole domain. | Settings Security Single sign-on |
| Who can do what? | Five roles and 29 permissions per person, enforced on the server. | Settings Members |
| Is there an audit trail? | Every change a member makes, and every attempt they weren't allowed to make, with the person, the time and the fields that changed. | Settings Security Audit log |
| Where is our data stored? | In the region chosen for your organization. The European Union is the default. | Settings General |
| How long are replays kept? | Twelve months on Enterprise, for session replays and errors. | Settings Billing |
| What does session replay record? | Password, card and similar fields are masked in the shopper's browser before anything is sent, and any element can be blocked from recording. | SDK data-mtrix-block |
| Is data encrypted before it's sent? | Every payload is encrypted in the browser with AES-256-GCM before it leaves the page, and Mtrix sets no third-party cookies. | SDK |
| Which certifications do you hold? | SOC 2 Type II and ISO/IEC 27001. The report and certificate are shared under NDA. | /security |
| Is there a DPA? | Yes, with the EU Standard Contractual Clauses, the UK addendum and the Swiss adaptation. | /dpa |
A named person on your account,
not a ticket queue.
Enterprise starts with a call about your storefronts and your stack. After that you have a contact who knows your setup, a Slack channel shared with our team, and people who move your pages over with you.
A 24-hour ruler in UTC, from 00:00 to 24:00, with the support window drawn on it as a band from 06:30 to 22:00 UTC. The band starts at 8:30 (GMT+2) and ends at 17:00 (EST).
- Migration is included. Our team moves your pages over with you, with no fee on top of the contract. Even the most complex stores are running on Mtrix within a week.
- A shared Slack channel. Your team and ours in one place, for questions, releases and test ideas.
- Support terms in the contract. The Enterprise agreement includes an SLA.