How to choose the right data product for you

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

Product	Pros	Cons
From Parquet exports	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 SQL	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 service - pipe Farcaster data	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 can share 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.