# Thinking to save 1 million records

**URL:** <https://community.fibery.io/t/thinking-to-save-1-million-records/11455>\
**Category:** Get Help\
**Created:** [October 24, 2026, 5:33pm UTC](https://community.fibery.io/t/thinking-to-save-1-million-records/11455 "2026-10-24T17:33:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Manas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/manas/32/15056_2.png) [@Manas](https://community.fibery.io/u/Manas)\
**Post date:** [October 24, 2026, 5:33pm UTC](https://community.fibery.io/t/thinking-to-save-1-million-records/11455/1 "2026-10-24T17:33:22Z")

</div>

For historical data of financial products, can fibery store million records? Daily new 12000 records to be added once. Not much filtering or sorting will be done on UI. Mainly it will be for API fetch in another app.

Basically can we use Fibery for this, as replacement of nocode DB? Or need to spin up and maintain separate DB, e.g., Neon?

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [October 24, 2026, 10:55pm UTC](https://community.fibery.io/t/thinking-to-save-1-million-records/11455/2 "2026-10-24T22:55:33Z")

</div>

I wouldn’t recommend it. Fibery is not designed to be a highly-performant headless db.