<aside> 💡 Now here: https://docs.neynar.com/docs/how-to-choose-the-right-data-product-for-you

</aside>


Archive

April 25, 2024

Available products

[Public] Premium Parquet User Docs

[Public] Postgres Database Access

[Public] Farcaster Indexing Service

Why

Developers can focus on what they are building instead of running a hub and replicator which can be significant cost & effort over time

How to pick the right product for your team

Product Pros Cons
Parquet export No need for developer to share access to database w/ Neynar Need to set up parquet ingestion workflow (we will make sample github code available soon)
Developer ingests parquet files and can read/write to their own db as needed
Hosted Postgres read only access Directly write sql queries against a postgres hosted db, no need to set up anything additional Developer has no write access to db

creating new indexes, etc. requires reaching out to Neynar

no changes to overall table schema | | Indexer as a service | Neynar writes to a db on the developer’s side, no need for developer to manage hubs or replicators

Neynar handles all hub and replicator related upgrades and maintenance | Developer needs to have a db that they are comfortable sharing write access to | | | Developer has flexibility to let Neynar pipe specific tables instead of all FC data | | | | Developer can manage the db as they see fit — create new indexes, etc. | |

easf