Softwr

Automation Integration · head to head

Census vs turbopuffer

Census logo

Census

Automation Integration

The reverse ETL infrastructure for data activation

From
Free
Free plan
Yes
turbopuffer logo

turbopuffer

Databases

Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.

From
$16/month
Free plan
No

The short version

  • Census is a data activation platform.
  • Census is free; turbopuffer starts at $16/mo.
  • Only Census lists reverse ETL; only turbopuffer lists object storage architecture.
  • Where Census falls short: Census domain permanently redirects to Fivetran (301 redirect).
  • Prices and features on this page were last checked on 13 November 2026.

How do Census and turbopuffer differ?

Census and turbopuffer differ on starting price (Free against $16/month), pricing model (Usage-based against Subscription) and free tier (Yes against No). Only the attributes on which Census and turbopuffer actually diverge.

Attributes where Census and turbopuffer differ
AttributeCensusturbopuffer
Starting priceFree$16/month
Pricing modelUsage-basedSubscription
Free tierYesNo
PlatformsWeb, APIWeb
CategoryAutomation IntegrationDatabases

Not yet recorded: founded for turbopuffer.

Which features does each one have?

They share no listed features; 17 appear only for Census and 10 only for turbopuffer. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Census

  • Reverse ETL
  • Data syncing
  • Transformation
  • Real-time activation
  • Error handling
  • Monitoring
  • Analytics
  • 150+ destinations

Only in turbopuffer

  • Object storage architecture
  • Namespaces
  • Vector search
  • Full-text search
  • Attribute filtering
  • Documented limits
  • Configurable consistency
  • Durable writes

What is each one used for?

The jobs each tool is most often brought in to do.

Census

  • Syncing customer data from a warehouse into marketing and sales tools (reverse ETL)not turbopuffer

turbopuffer

  • A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot Census
  • Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot Census
  • Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot Census
  • Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot Census

Where do Census and turbopuffer fall short?

Census's most cited limit: Census domain permanently redirects to Fivetran (301 redirect). Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Census

  • Census domain permanently redirects to Fivetran (301 redirect)
  • Exact per-tier pricing not listed; customers directed to contact sales or request quotes
  • Annual contracts offer up to 22% savings but discount terms not detailed
  • Usage rates vary by connection type; pricing examples show variance ($17–$202 for different sources)

turbopuffer

  • A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second
  • Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable
  • It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends
  • Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service
  • It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you

How much do Census and turbopuffer cost?

Census is free to use; turbopuffer starts at $16/mo. Plan by plan below, from each vendor's own pricing page.

Census

Free
  • FreeFree
    • 500,000 monthly active rows (MAR) for connections
    • 3,500 MAR for activations
    • 5,000 monthly model runs (MMR) for transformations
  • StandardOn request
    • Usage-based pricing for connections, transformations, activations
  • EnterpriseOn request
    • Greater flexibility and control
    • Custom pricing

turbopuffer

$16/month
  • Launch$16/mo
    • All database features
    • Multi-tenancy deployment
    • SOC2 & GDPR-ready DPA
  • Scale$256/mo
    • Everything in Launch
    • HIPAA-ready BAA
    • Single Sign-On (SSO)
  • Enterprise$4,096/mo
    • Everything in Scale
    • Single-tenancy & BYOC deployment options
    • Private networking

Which should you pick?

Choose Census if

  • You need reverse etl.
  • You want to start without paying.
  • You work on Web, API.
  • You also want data syncing.

Choose turbopuffer if

  • You need object storage architecture.
  • You also want namespaces.

Questions people ask

Is Census or turbopuffer better?
Neither clearly leads. Census starts at Free and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Census or turbopuffer?
Census has a free tier; the other does not. Paid plans start at Free for Census and $16/month for turbopuffer.
Does Census or turbopuffer run on more platforms?
Census runs on Web, API. turbopuffer runs on Web.
Can I use Census for free?
Yes. Census has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
What is Census best used for?
Census is most often used for syncing customer data from a warehouse into marketing and sales tools (reverse etl). Of those, syncing customer data from a warehouse into marketing and sales tools (reverse etl) is not what turbopuffer is typically brought in for.
What can Census do that turbopuffer cannot?
Census covers Reverse ETL, Data syncing, Transformation, Real-time activation. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

Answered from the vendors’ own pages

Census: What happened to Census.com?

Census (formerly getcensus.com) has been acquired by Fivetran. The domain permanently redirects (301) to fivetran.com. Census functionality is now part of Fivetran's data platform.

Source
turbopuffer: Can I self-host turbopuffer?

There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.

Census: How much does Fivetran (formerly Census) cost?

Fivetran uses usage-based pricing. Free tier includes 500,000 monthly active rows (MAR) for connections, 3,500 MAR for activations, and 5,000 monthly model runs for transformations. Paid pricing depends on usage; example: Facebook Ads with 34,479 MAR costs $17.23/month; Snowflake-to-Salesforce with 12,007 MAR costs $202.01/month.

Source
turbopuffer: How fast is it really?

Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.

Census: Do Fivetran/Census offer discounts for annual commitments?

Yes, annual contracts offer up to 22% savings versus monthly pricing. Additional discounts are available for nonprofits, startups, and specific use cases.

Source
turbopuffer: Is it consistent?

Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.

turbopuffer: What is it best at?

Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.

turbopuffer: What are the hard limits?

Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.

Share

Related pages

Other head to heads