> For the complete documentation index, see [llms.txt](https://docs.shadow.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadow.xyz/getting-data/database-syncs.md).

# Database syncs

{% hint style="info" %}
Database syncs are included on paid [Pro Shadow Fork plans](https://www.shadow.xyz/pricing).
{% endhint %}

Database syncs allow you to stream data to your own database in realtime.

Data will appear within seconds of a transaction on mainnet landing, and Shadow handles re-orgs for you automatically by replacing rows.

## Steps

1. **Choose your data:** Export shadow and/or mainnet data (coming soon), and specify which contracts and events you want to export.
2. **Choose your destination:** You can send your data to your own Postgres database.
3. **Choose your settings:** You’ll be prompted to set a start block for the recurring export if you’d like to export historical data.

<figure><img src="/files/e1Eu1dXXzK7VrJ7ztPnD" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
If you choose to export shadow data, you’ll only be able to select events from contract addresses that you have shadowed (e.g. deployed modifications to).\
\
If you shadowed the implementation of a proxy contract, you’ll need to perform a “no-op deploy” on the proxy contract by hitting “Compile > Deploy” in the editor without making any shadow changes. We’re working on a better experience for this!
{% endhint %}