---
title: "Application vs Client Database"
slug: "application-vs-client-database"
updated: 2023-08-25T14:01:10Z
published: 2023-08-25T14:01:10Z
canonical: "docs.ursahealth.com/application-vs-client-database"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ursahealth.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Application vs Client Database

Ursa Studio is a web-based platform that connects to and manages the transformation of healthcare data within a database. This database is referred to as the *Client Database*. Ursa Studio is compatible with all the leading database vendors, including Azure Synapse, Databricks, MS SQL Server, Oracle, PostgreSQL, Redshift, Snowflake, BigQuery, and Vertica.

In addition to this pre-existing database, Ursa Studio requires the deployment of a PostgreSQL *Application Database* to power the app itself. Measure and report definitions, user credentials, user-defined fields, and other such metadata are kept in the *Application Database*. The *Application Database* never contains customer PHI.

In a hybrid deployment, the *Customer Database* is managed by the customer, and the *Application Database* as well as the Ursa Studio application is managed by Ursa Health.