Skip to content
Marketrix Docs

Applications Overview

Applications are the foundational container in Marketrix. Each Application represents a web app or website you connect to the platform — so Marketrix can learn it through Simulations, then power autonomous testing, UX research, and live customer support on top of that understanding.

What is an Application?

Section titled “What is an Application?”

An Application is the link between your product and Marketrix. It tells the platform where your app lives, how to access it, and which domains it is allowed to navigate. Everything else in Marketrix — knowledge, personas, simulations, skills, widgets, and QA Flows — is organized under an Application.

Application types

Section titled “Application types”

An Application is one of two types:

  • App — For applications behind a login. You provide a username and password so Marketrix can sign in and interact with authenticated pages. Use this for dashboards, admin panels, and SaaS products.
  • Website — For publicly accessible sites that don’t require authentication. Use this for marketing sites, documentation portals, and landing pages.

When you create an Application, the type is set by the This application requires authentication credentials toggle: turn it on for an App, leave it off for a Website.

Key fields

Section titled “Key fields”

| Field | Description | |-------|-------------| | Name | A display name for the Application (for example, “Production Dashboard”) | | URL | The base URL of your web app or website | | Type | Either App (authenticated) or Website (public) | | Username / Password | Sign-in credentials, used for App type only | | Description | Optional note about what this Application is for | | Allowed Domains | Optional list of domains Marketrix is permitted to navigate during simulations. Leave empty to allow all domains |

How Applications connect to everything else

Section titled “How Applications connect to everything else”

Applications sit at the top of the Marketrix hierarchy:

Application
├── Knowledge — Documents and videos Marketrix reads about your product
├── Simulations — Autonomous runs that explore your app
│   ├── Graph — The Application Graph: what Marketrix sees across all runs
│   └── Skills — Reusable routines distilled from completed runs
├── Personas — Models of your real user types
├── Widgets — Embeddable chat interfaces deployed on your site
└── QA Flows — Test flows generated from your requirements
  1. Create an Application to connect your web app to Marketrix.
  2. Add Knowledge (documents, videos) so Marketrix understands your product.
  3. Run Simulations to let Marketrix autonomously explore and test your app, building up the Application Graph and Skills.
  4. Deploy Widgets to put AI-powered support directly on your site.

Next steps

Section titled “Next steps”