# Best approach to running my own indexer with low latency

**URL:** <https://forum.algorand.co/t/best-approach-to-running-my-own-indexer-with-low-latency/5612>\
**Category:** General\
**Created:** [January 3, 2022, 11:52pm UTC](https://forum.algorand.co/t/best-approach-to-running-my-own-indexer-with-low-latency/5612 "2022-01-03T23:52:20Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![cc9one](https://avatars.discourse-cdn.com/v4/letter/c/73ab20/32.png) [@cc9one](https://forum.algorand.co/u/cc9one)\
**Post date:** [January 3, 2022, 11:52pm UTC](https://forum.algorand.co/t/best-approach-to-running-my-own-indexer-with-low-latency/5612/1 "2022-01-03T23:52:20Z")

</div>

I have learned that geographic proximity is critical between the Indexer writer, the postgres db, and the algod instance if I want low latency between my postgres database and the blockchain.

I am considering running my own node and indexer on the same server.

What are some cost effective approaches for running my own indexer and node for an individual developer like myself? Is most everyone using something like AWS or building their own at home setup?

---

_[View the full topic](https://forum.algorand.co/t/best-approach-to-running-my-own-indexer-with-low-latency/5612)._