> ## Documentation Index
> Fetch the complete documentation index at: https://glide-9da73dea.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Orchestration shell, not a bank stack

> Honest positioning for what Glide OSS is and isn't. The code that orchestrates regulated partners — not the partners themselves.

Glide OSS is **a self-hostable orchestration shell**, not a self-hostable bank stack. This page is the source of truth for what that means in practice.

## What you get

* The web app, mobile app, and MCP gateway that orchestrate money movement.
* 21 vendor connectors as MIT-licensed adapters.
* 6 hero agent skills + the partner-PR scaffolding for community contributions.
* 4 Headless platform packages (`policy-engine`, `schemas`, `grant-wrapper`, `secrets-scan`).
* Self-host quickstart (`@repo/cli`, `@repo/secrets`, `create-glide-app`).
* Public standards at [`glide.co/schemas/agent-banking/draft/`](https://glide.co/schemas/agent-banking/draft/).

## What you bring

| Vendor                                     | What they provide                                  | Contract / posture                                                         |
| ------------------------------------------ | -------------------------------------------------- | -------------------------------------------------------------------------- |
| **Privy**                                  | Auth + embedded wallets + programmable signing     | Multi-tenant tenant required. OSS is Privy-only in v1.                     |
| **Bridge / Noah / Avenia / IDRX / etc.**   | Fiat on/off-ramps + KYC                            | Per-vendor contracts. Adapters MIT; vendor seats yours.                    |
| **Chainalysis / TRM / Elliptic**           | Sanctions screening                                | Per-vendor contract. The Chainalysis adapter ships with a `DISCLAIMER.md`. |
| **Coinbase x402 facilitator** *(optional)* | x402 settlement                                    | Required for the x402 payer / recipient flow at M2.5+.                     |
| **Ory Hydra or BYO OAuth AS** *(optional)* | RFC 7591/8707/9728 OAuth AS for the agent platform | Required for `apps/mcp` production deploy.                                 |

## Why we draw the line here

The OSS Cathedral plan made a deliberate trade-off:

> Glide OSS is the **code** that orchestrates regulated partners — partners still hold all licenses; Glide OSS is the code that orchestrates them. This framing must stay honest in README, SELF\_HOSTING docs, and marketing — calling OSS a "money OS" without surfacing the vendor-lock-in layer creates trust debt.

The alternative ("bake every regulated counterparty into OSS") fails for three reasons:

1. **Vendor licenses are not transferable.** Bridge's MSB license, Noah's vendor agreements, Chainalysis's data-sharing terms — none of these can be redistributed under MIT. The vendor relationship has to live with the operator.
2. **Compliance isn't code.** SOC 2, regulatory examinations, KYC due diligence, off-chain settlement contracts — all of this is the operator's burden. Code can't carry it.
3. **The flywheel works at the orchestration layer.** Glide's wedge is "an MIT-licensed orchestration shell every regulated partner can integrate with for free." If we tried to be every partner, we'd compete with our own ecosystem.

## Three documented parity exceptions

Even with this honest framing, there are three places where "100% code parity between Glide Cloud and self-hosted" needs explicit asterisks. See [Hosted vs self-hosted](/oss/concepts/hosted-vs-self-hosted) for the current status of each:

1. **Chainalysis live adapter (counsel-blocked redistribution).** Status: shipping in OSS as of M2; mitigation if blocked is the existing `chainalysis-mock` + the `permissive` fallback.
2. **Privy Multi-tenant requirement (vendor-only OSS).** Self-hosters without a Privy account cannot run Glide today.
3. **Mobile App Store distribution (platform-controlled).** Apple / Google developer accounts + attestation services aren't transferable to OSS forks.

## Reading list

* [Self-host guide](/oss/self-hosting) — operator runbook.
* [Hosted vs self-hosted](/oss/concepts/hosted-vs-self-hosted) — explicit parity table.
* [Money-safety contracts](/oss/concepts/money-safety-contracts) — the F-rules every money-touching path observes.