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

# Introduction

> What Alforse is, who it's for, and how this documentation is organized.

## What is Alforse

Alforse is a contract operating platform for equipment sales and leasing teams. It replaces a
fixed spreadsheet ledger with a governed contract workspace: saved views, workflow boards,
configurable fields, approval control, payment execution, file traceability, tenant
administration, and audit-style history for every sensitive action.

## Applications

Alforse is a small family of applications that share one backend API and one tenant/permission model.

<CardGroup cols={2}>
  <Card title="Deals" icon="briefcase" href="https://deals.alforse.com">
    The day-to-day workspace: contract intake, ledgers, collections, payments, invoice evidence,
    and workflow control. This is what most users mean by "Alforse."
  </Card>

  <Card title="Console" icon="sliders" href="https://console.alforse.com">
    Organization administration: members, invitations, role permissions, workflow controls,
    subject companies, notification channels, and audit review for your own organization.
  </Card>

  <Card title="API" icon="webhook" href="/api-reference/introduction">
    The shared backend that the applications above call, and the same API that Business,
    Enterprise, and Self-hosted plans can call directly for integrations.
  </Card>
</CardGroup>

## Who this documentation is for

* **Workspace users and admins** — read the [Concepts](/concepts/tenants-and-platform) and
  [User Guide](/guides/dashboard) sections to understand how contracts, permissions, and workflow
  stages work in Deals and Console.
* **Developers integrating with Alforse** — start with [Quickstart](/quickstart) and then the
  [API Reference](/api-reference/introduction). External API access is part of the Business plan
  and above; see [Plans & Editions](/concepts/plans-and-editions).
* **Self-hosted deployment teams** — read [Installation](/installation) and
  [Configuration](/configuration) for the Docker Compose based deployment.

## Terminology

Alforse documentation and UI use these terms consistently:

| Term                | Meaning                                                                                                |
| ------------------- | ------------------------------------------------------------------------------------------------------ |
| **Tenant**          | A customer organization using Alforse — the organization you log into with a `tenantSlug`.             |
| **Subject company** | A company or legal entity inside a tenant whose contracts, payments, and files are managed in Alforse. |

In this documentation, "admin" means a tenant administrator using the Console for their own
organization.

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Get a tenant and your first contract created, on Alforse Cloud or self-hosted.
  </Card>

  <Card title="API Reference" icon="code" href="/api-reference/introduction">
    Authenticate and call the API directly.
  </Card>
</CardGroup>