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

# Native Integrations

> Leverage the Tight API’s wide range of seamless integrations

## Zero dev effort

All of Tight's integrations are native integrations such that your company will not need to pull or push any data from
the integration provider.

For example, if you want to integrate bank transactions (via [Plaid](/integrations/banking/plaid)), you can simply
provision a Plaid developer account and grant Tight partner-level access to that account, and Tight takes care of the
rest; no infrastructure for your team to build around pulling/storing/refreshing tokens and handling error scenarios.

If you want to integrate tax filings (via [April](/integrations/tax/april)), you can simply provision a Column
Tax developer account and grant Tight partner-level access to that account, and Tight takes care of the rest; no need
for your team to aggregate all the user's transactions and push them into Column Tax's API directly.

## Own the relationships with your providers

The Tight API serves as the general ledger and glue for all of the accounting data that your users accumulate. All the
relationships (and any associated economics) with integration partners like Plaid, Column Tax, Stripe, etc. are owned by
your company, giving you the same flexibility you would get if working with those integrations directly, but without any
of the development/integration overhead.

## One-stop shop

By enabling the integrations that make sense for your user base, you enable your platform to become the true one-stop
shop that every business owner is after.

<Note>
  If you don't see an integration that you're looking for, don't hesitate to reach out to the Tight team at [api@tight.com](mailto:api@tight.com). Tight is architected to support infinite integrations and is always adding new integrations based on customer-partner demand.
</Note>
