🔍 Introducing Scious Search: solve instant search once and for all

For years, instant search in Bubble has been a thorn. The official Algolia integration doesn’t preserve privacy rules, sorting results alphabetically is a pain, and sorting by options is impossible. The Algolia plugins suffer in similar ways and that’s all in addition to the cost of Algolia itself - which gets pricey. On the other side of the cost spectrum, free solutions like the fuzzy search plugin are one of the surest ways to lock a page searching 2,000 records (while now burning workload units).

Crafted from the scorched crucible of this pain and suffering, today I’m launching what I have designed and hope to be the most powerful yet cost effective search plugin for Bubblers: Scious Search (that’s “sci” like science and “us” like you and I ). Despite the name, it’s more like multiple plugins in one - allowing developers to quickly add Algolia, Typesense, and [future] alternative search providers to Bubble apps. As a deep integration, we’ve made this in a way that:

  • Preserves privacy settings across all data types.
  • Does not degrade or slow down as your database grows to millions of records.
  • Returns an actual bubble thing, which can be used like any native bubble data type within the editor.
  • Works with live, test, and other versions of your app so you can test integrations before going live.
  • Can save you money.
  • Quite a bit more.

While the Algolia integration we provide is - we think - objectively better than available alternatives, the money saved by switching from Algolia to Typesense using our plugin can be substantial, with some of our users on track to save hundreds of dollars a year even after including our plugin’s annual cost. If you are a current Algolia user and are curious about saving money on your monthly search bill, check out our savings calculator here.

And speaking of costs, while I did not anticipate this, it turns out this plugin drastically reduces the number of Workload Units (WU) needed to perform instant searches (versus Bubble’s native “Do a search for” ability). Details in the comment below.

So for those interested, you can test drive our features here, checkout our ecommerce template here, and peruse the manual here.

Our plugin comes with:

  • A 10 day free trial. Enough time to try out search providers before having to commit.
  • App transferability. While our plugin can only be used by one Bubble app at a time, unlike regular plugins, a subscription to ours can be switched to other apps. So if you scrap an MVP and start another, you can reinstall our plugin at no added cost.
  • Hands on support. Our annual subscription includes a half hour one-on-one support session for answering any integration questions.

Scious Search is available in “restricted-beta” starting today. Over the next three to four weeks we’ll accept and help 10 early adopters get setup. Then formally launch to the Bubble marketplace. Please DM me if interested in being part of the beta.



Two things - folks interested in learning more about the plugin can ask questions below (of course) or join one of the following live webinars:

Workload Unit impact

And of course, I promised a discussion on Workload Units. It’s been interesting to see how lean our search solution is compared to using Bubble’s native search. To illustrate, note that our demo collectively has 9 search examples. Only two of those use Bubble’s native search. Those searches, which only sift through 3k records, makeup roughly 63% of our Workload Units for Fetching Data. In contrast, the 7 searches that use our plugin - one of which is searching over 250k records - make up less than 28% of WUs for Fetching Data. This works because our plugin only has to fetch individual records from our app database and avoids Bubble’s Search channel entirely.

This means that, if we replaced the two native search examples in our demo with Scious Search, we would reduce our App’s overall WU consumption by about 23%.

Below are screenshots for those wedges as of this writing but you can confirm these (moving numbers) in our editor here. By the way, this is my best interpretation of these numbers so someone please correct me if I’m wrong.


Looks interesting. Just a shame the webinars are at 2am Australia time.

Congrats on getting this out , @zelus_pudding! Sounds pretty great. I bet @christo1 if you register for a session Zelus will send a replay link!

1 Like

I am sure they would. Not a great option for interactivity though, but workable. Also no registration option, just a call in number, which doesn’t really lend itself to receiving a recording.

1 Like

I’m looking into a webinar platform that accepts registration. In the meantime, would 7pm or 8pm CST work for you sometime this week? If so, tell me the day and I’ll setup another webinar for you and our non-US based friends :slight_smile:

Also, probably a known issue, @zelus_pudding, but many of the links in the demo page that I think are supposed to point to (something else) are pointing to the Bubble plugins page.

1 Like

Hey Keith! I appreciate that heads up! Yeah, we have three links that point to the (future) official bubble listing of our plugin. Those will work in about 3 weeks when we go live on the marketplace but - yeah, I’m just going to disable those to minimize confusion.

Also, thanks for the kudos :slight_smile: Feels really good to finally put this out in the open.

1 Like

For us anytime from 6pm CST works as 6PM CST = 9am the following day in most of Australia except the west, which is 2 hours behind, but 7am is still fine. I am also happy with a recording for now as my first intent with the webinar is to see how easy or hard this is to impliment into my current app.

1 Like

Yes, super interested in giving this a try in my app,

1 Like

Very interesting! However, there’s another WU impact I think that you doesn’t mention. According to what I understand, you need to send the data to Typesense (or Algolia). This will consume WU for each item created or updated in Bubble DB. Right?

1 Like

This is correct. Nevertheless, the figure’s I’ve cited cover the last 30 days - a time period over which I (re)uploaded a CSV with 10,000 records two or three different times and re-synced that data to my search providers 3 to 5 times. You’ll notice on my first pie chart the bright (baby) blue section which show those CSV imports. It’s all in the mix.

1 Like

Just reached out to you via DM!

I’ve been using this plugin in beta for a month or so. I can tell you it has been really helpful for us at get-gigs.com, specifically for location based searches. In particular, our users have geographic areas they are looking in and we need to match three or four of those geographic areas with other users’ three or four areas as well as general metropolitan areas (and add in another 30+ combinations of genres, keywords, etc). Previously I had multiple merged searches using a variety of methods and conditions. It was slow (especially the geographic stuff) and difficult to modify because of the complexity. Using typesense has allowed us to move our main gig-searching queries from eight conditional data sources and multiple “unique id is in” type searches to a single query that is generated in javascript based on a data type that gets updated and triggers a new search in typesense. I can’t speak to WU savings as I don’t have a full handle on it for us as yet. I will say that keeping the typesense db up to date should likely not be done through a data trigger, as I would’ve done previously.

Overall, this plugin has improved the user experience for searches and has allowed us to prototype and consider more complicated maps based functionality for our users. @zelus_pudding has been very responsive and helpful as I was learning the ins and outs of the typesense query nomenclature and also when I ran into a bug or two during development. Would recommend you give it a try if it meets your use case.


looks interesting, actually I’m currently developing a commercial directory on Bubble and this might be a very awesome solution. I’ll DM you in a couple of weeks to test it out.


You mentioned you’re happy with a webinar recording at this point - I’ve just updated the webinar links so folks can register / get the recording afterwords. Of course, happy to follow up with you if you have questions :slight_smile:

@grottofilms , I hadn’t realized you were able to compress that many conditional data sources into one of our search filter queries. That’s so awesome! Very glad it’s working well for you :partying_face:

1 Like

I have been using Scious Search in my app for 6 months now and its working incredible well. Some of our tables have >100k records. We were using Fuzzy search and it was taking 25 seconds to return a result.

Now, the search is lightening fast. Scious search returns results in a few milliseconds. The plugin also lets us sort data alphabetically and separate it by user using the privacy rules.

We sync to Typsense which is costing us about $10/m. The cost is negligible compared to the performance we now get.

I highly recommend Scious search for anyone looking to hold more than 2K records in their database.


Is there a support for list containing or intersecting with other list?

Yes! Both Algolia and Typesense support searching for an item within a list - this is a very common operation. We even do it a few times in the demo (note my yellow highlight in our filters setup):

1 Like

Great! Sign me up for beta!

1 Like