> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/start-here/what-is-qore.md).
# What is Qore
High-Velocity Building with Enterprise Control
Qore provides a cloud-native launchpad that helps you move from an idea to a live application with minimal friction. Qore handles environment configuration and dependencies, and you keep full ownership of your security.
Your cloud-native launchpad is deployed within your bank’s network boundaries. No transactional data ever leaves your controlled VPC. See the [Security FAQ](/ai-workbench-qore/control-center/detailed-security-and-runtime-faq.md). For the cloud providers Qore runs on, see [Deployment options](/ai-workbench-qore/start-here/deployment-options.md).
> **Sign-in**: People sign in with **Google**, with **Microsoft** (including Microsoft Entra ID work and school accounts), or with email and password. Each single sign-on method is turned on per deployment. Access is invite-only: an administrator invites each person before they can sign in, whichever method they use. See [Single Sign-On](/ai-workbench-qore/control-center/admin/single-sign-on.md).
## Sharing & Collaboration
Qore makes it easy to bring the right people into the build at the right time.
* **Collaborator Invites**: Invite teammates directly by email. A collaborator joins the account and can open, edit and publish its apps — see [Plan](/ai-workbench-qore/console/app-builder/plan.md#collaboration) for what that covers before you invite someone.
## Meet the Builders: Your Intelligent Ecosystem
The power of Qore lies in how the three core pillars work together. Think of them as the components of a high-performance vehicle:
| **The Pillar** | **Your Strategic Advantage** | **The Analogy** |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **1. App Builder** | **The Interface:** Design the complete, user-facing experience where the human interaction happens. | **The Car Body:** The sleek look and feel that users interact with. |
| **2. Agent Builder** | **The Intelligence:** Create the "brain"—the reasoning engine that manages knowledge and decides the next move. | **The Driver:** The smart core that knows where to go and how to get there. |
| **3. Skill Library** | **The Capabilities:** Providing the individual, reusable actions (API calls, code, MCP servers, document processing) the Agent executes. | **The Toolbox:** Your direct line to the world. Whether it’s a built-in skill or a **custom-connected Third-Party API,** your agent has the muscle to interact with any external system. |
### Around the builders
| Area | What it does |
| ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**Knowledge**](/ai-workbench-qore/console/knowledge.md) | Turns source documents into knowledge bases that agents query. A knowledge base changes only when you sync it, and each sync creates a new knowledge version. |
| [**Flows**](/ai-workbench-qore/console/flows.md) | Builds a fixed, multi-step process that an agent can run as a single skill. |
| [**Design Systems**](/ai-workbench-qore/console/design-systems.md) | Holds a project's shared visual identity, which the apps you build use. |
| [**Console Operator**](/ai-workbench-qore/console/console-operator.md) | The chat surface in Console. Describe a goal, and it plans the work and hands each part to the right agent. It can also run on a schedule. |
| [**Control Center**](/ai-workbench-qore/start-here/control-center.md) | Monitors and governs the whole account: AI Gateway, observability, evals, guardrails, cost, and access. Its **Governance Operator** answers account-wide questions and stages changes for your approval. |
## How It All Converges
### The Lending Example
In Qore, AI isn't a standalone tool; it’s a collaborative ecosystem. Here’s how a standard **Loan Origination** workflow comes to life:
{% stepper %}
{% step %}
#### The user interacts with the app
A Relationship Manager opens your custom Loan App to start a new file.
{% endstep %}
{% step %}
#### The app activates the agent
The interface sends a request to the Agent, such as *"Collect and verify docs for the Smith file"*.
{% endstep %}
{% step %}
#### The agent orchestrates the skills
The Agent maps the execution with its reasoning engine:
1. Use the **Classify Document** skill to identify each uploaded file.
2. Use an **Extract Document Data** skill to pull the fields it needs. With **Sensitive Data Masking** turned on, detected PII is replaced with tokens before it reaches a model.
3. Use an **API Call** skill to push verified data into your core banking system.
{% endstep %}
{% endstepper %}
**The Result:** You’ve transformed a fragmented, manual process into a unified, outcome-driven machine.
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/start-here/what-is-qore.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
