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

# Market

> Where AiQL sells and who it is built for

AiQL sells to organizations that must reason over large, fragmented bodies of documents, standards, and expert knowledge, and that must defend the result. Named accounts belong on [Clients](/clients/overview). Approved partners belong on [Partners](/partners/overview).

## Geographic focus

The primary market is the Middle East. Expansion is the United States, then the European Union, then worldwide.

<Steps>
  <Step title="Middle East">
    Primary commercial focus. Regional data residency and tenancy options include Saudi Arabia and the UAE. See [Data regions](/commercial/data-regions) and [Tenancy tiers](/commercial/tiers).
  </Step>

  <Step title="United States">
    Next expansion market. US data residency is offered in Virginia.
  </Step>

  <Step title="European Union">
    Then the EU. EU data residency is offered in Frankfurt for GDPR.
  </Step>

  <Step title="Worldwide">
    After those markets, AiQL expands further. Other data regions already include India and Singapore.
  </Step>
</Steps>

Hosting regions and tenancy tiers are deployment choices. They are not the same as the order in which AiQL sells.

## The buyer

AiQL is aimed at knowledge-intensive, regulated work: healthcare, financial services, government, pharma, and construction. Generic systems search documents and guess. These buyers need answers that are precise, traceable, and consistent with the organization's own rules. How that differs from model-only products is on [About AiQL](/company/about).

Typical buyers hold knowledge across disconnected sources: clinical or legal standards, contracts, policies, operational data, and expert judgment. They need a reasoning layer over that material, not a chatbot on a file dump.

Large regulated and government buyers tend to sit on dedicated or split tenancy under [custom deployments](/commercial/custom). Smaller private buyers tend to sit on [self-service SaaS](/commercial/saas) or on managed or central tenancy. See [Tenancy tiers](/commercial/tiers).

## Client profiles

These are composites for investors. They are not named clients.

<Columns cols={2}>
  <Card title="Healthcare system" icon="heart-pulse">
    A hospital group or health authority. Protocols, insurance rules, and clinical standards sit in different documents. Clinicians need reasoning that can be applied beyond a single physician, with an audit trail.
  </Card>

  <Card title="Bank or insurer" icon="landmark">
    Credit, compliance, or claims teams. Policies and regulations change. Decisions need an explainable rationale chain that can be shown to an auditor.
  </Card>

  <Card title="Public sector" icon="landmark-flag">
    A ministry or regulator. Policy, statute, and case history must stay in-region. Answers have to be defensible in review, not only plausible.
  </Card>

  <Card title="Pharma" icon="flask">
    Safety, medical affairs, or regulatory operations. Drug, trial, and labeling knowledge is layered. Submissions and pharmacovigilance need traceable support from structured guidelines.
  </Card>

  <Card title="Construction and real estate" icon="building">
    A developer or contractor. Contracts, FIDIC or local codes, and past project files must be interpreted consistently for permits and design reuse.
  </Card>
</Columns>