Differences between Connected and Native App
QPR ProcessAnalyzer using Snowflake calculation is available in the following deployment options: connected app and Native App. Both let process mining analyses be run on data stored in Snowflake, but they differ in where the application runs, how it is accessed, and which features are available.
Overview
In the connected app, QPR ProcessAnalyzer runs outside Snowflake and is connected to a Snowflake account through an ODBC connection. QPR ProcessAnalyzer Server creates the SQL queries needed for the calculations and sends them to Snowflake for execution, while the eventlog data stays in Snowflake. QPR ProcessAnalyzer needs a Snowflake schema where it can create functions and store cache tables, so write permissions to that schema are required.
The connected app is available in two variants:
- Managed: QPR Software provides and runs QPR ProcessAnalyzer as a managed service, and the customer connects it to their Snowflake account.
- Self-hosted: Customer installs and runs QPR ProcessAnalyzer in their own infrastructure (cloud or on-premises) and is responsible for operating, updating and maintaining it.
In both variants the application is separate from Snowflake and is accessed through its own web address using a web browser.
The Snowflake Native App runs entirely inside the customer's own Snowflake account as a container-based application (Snowpark Container Services). It is installed from the Snowflake Marketplace or from a private listing. The process data stays in the customer's Snowflake environment, and the app uses Snowflake's security, access controls and governance. The Native App is updated automatically, so users do not need to perform any update actions.
Deployment options comparison
| Aspect | Connected app | Native app |
|---|---|---|
| Where application runs | Outside Snowflake on the customer's own servers (self-hosted), or on a managed service in QPR Cloud provided by QPR Software. | Inside the customer's Snowflake account, as a Snowpark Container Services application. |
| Accessing app | Through the QPR ProcessAnalyzer web address with a web browser. | Opened from the application page in Snowsight. Access is given by assigning the application role USER to Snowflake account roles. |
| User management and authentication | Authenticated using QPR ProcessAnalyzer user credentials, or Snowflake user credentials. Additionally, SAML 2.0 authentication is available to connect to an external identity provider. | Authenticated using Snowflake user credentials. |
| Access to Snowflake data | Connection string contains a single Snowflake user identity determining the permissions to the data for all users. Alternatively each user can access Snowflake data with their own Snowflake user permissions. | Native App has one common application identity for managing the access to the data for all users. |
| AI Assistant | AI Assistant is available. | AI Assistant is not available. |
| AI Root Causes Analysis | AI Root Causes Analysis is available. | AI Root Causes Analysis is not available (due to Snowflake's current limitations). Note that the classic root causes analysis is still available. |
| MCP server | QPR ProcessAnalyzer can be configured as an MCP server, where agents (such as Claude, Microsoft Copilot, OpenAI GPT) can connect to using OAuth and API key. | MCP server is always available and Snowflake Cortex Agents and CoWork can access it. It is also available outside Snowflake using programmatic access tokens (PATs). OAuth is not supported for external access. |
| Connecting to external data sources | Available, for example SAP, Salesforce, ODBC and web service sources. | Not available through QPR ProcessAnalyzer. Data must first be loaded into Snowflake using Snowflake's features, such as Snowpipe or Openflow. |
| Scripting | Expression language and SQL scripts are available. | Expression language scripts are available, but SQL scripts are not available. SQL operations can be run using Snowflake procedures. |
| Installation |
Self-hosted: Customer installs the software and configures the Snowflake connection. |
Installed from the Snowflake Marketplace listing or a private listing. |
| Updates |
Self-hosted: Customer administrator updates the environment. |
Updates are made available by QPR Software, and Snowflake automatically updates the installed Native Apps. |
| Data storage | Data can be stored and managed in Snowflake and SQL Server tables. | Data can be stored and managed in Snowflake tables. SQL Server storage is not available. |
| Logging and monitoring | QPR ProcessAnalyzer write a file log, available for the administrator. | Logs, traces and metrics are written to the Snowflake Event table and viewed in Snowsight. |
| Configuration data backups | Handled as part of the self-hosted installation or by QPR Software in the managed service. | Snapshots of the container block storage are taken and restored with Snowflake SQL commands. |
Common between Deployment Options
Both are the same QPR ProcessAnalyzer product used with Snowflake, so the following applies to both:
- Process mining calculations are run on data in Snowflake: the eventlog data is located in Snowflake tables and the queries are executed by a Snowflake warehouse.
- The process data stays in the customer's Snowflake environment, without moving or duplicating it outside Snowflake.
- Snowflake's security, access controls and governance are used for the data in Snowflake.
- QPR ProcessAnalyzer can act as an MCP server, giving AI assistants and agents access to process intelligence.