# Building on Permissionless

> Markdown export of the Gearbox Protocol documentation page for agents and retrieval systems.

Canonical page: https://docs.gearbox.finance/developers/gp-building
Source file: content/developers/gp-building.mdx
Section router: https://docs.gearbox.finance/developers/llms.txt
Section full export: https://docs.gearbox.finance/developers/llms-full.txt

Gearbox's permissionless architecture is designed for extensibility. You can build new components that plug into the system without requiring governance approval for the integration itself.

## What You Can Build

| Extension Type | Description | Guide |
| --- | --- | --- |
| **Adapter** | Add support for a new DeFi protocol (DEX, vault, staking) so Credit Accounts can interact with it | [Adapter Development](https://docs.gearbox.finance/developers/gp-adapters) |
| **Protocol Integration** | Compose with Credit Accounts from your own smart contracts — build strategies, keepers, or automated managers | [Protocol Integration](https://docs.gearbox.finance/developers/gp-integration) |
| **Core Extension** | Extend the protocol itself — custom interest rate models, pool hooks, Credit Manager spokes | [Core Extension](https://docs.gearbox.finance/developers/gp-extension) |

## How It Fits Together

```mermaid
flowchart LR
    subgraph "Your Code"
        Adapter[New Adapter]
        Integration[Protocol Integration]
        Extension[Core Extension]
    end

    subgraph "Gearbox Protocol"
        CM[Credit Manager]
        Pool[Pool]
        Facade[Credit Facade]
    end

    subgraph "External DeFi"
        DEX[New DEX]
        Vault[New Vault]
    end

    Adapter -->|"wraps"| DEX
    Adapter -->|"wraps"| Vault
    CM -->|"calls via"| Adapter

    Integration -->|"multicall"| Facade
    Extension -->|"extends"| Pool
    Extension -->|"extends"| CM
```

## Approval Flow

While building is permissionless, deploying to production uses the BCR verification process:

1. **Build** your adapter/integration/extension
2. **Test** with Foundry or Hardhat against forked mainnet
3. **Submit** for audit
4. **Register** in the [Bytecode Repository](https://docs.gearbox.finance/developers/gp-bcr) with dual signatures
5. **Curators enable** your component in their Credit Suites

Steps 1-2 are fully permissionless. Steps 3-5 ensure production safety.