[NEW PLUGIN] OptiCache PRO ⚡ - Stop Wasting WUs! Zero-Latency Caching with TTL & SessionStorage

Showcase Plugins
1

Hey Bubblers! :waving_hand:

If you are fighting to reduce your Workload Unit (WU) consumption and want your app to feel instantly fast, you need to stop querying the database for data that hasn’t changed.

I just released OptiCache, a frontend caching engine that turns the user’s browser into a lightning-fast database with 0ms latency and 0 WUs cost.

The Problem: Fetching a list of countries, product categories, or a user’s dashboard stats on every page load burns your WU budget and makes the user wait for the loading bar.

The Solution: Fetch it once, save it in OptiCache, and load it instantly from the user’s browser on any other page.

I’ve released two versions:

:green_circle: OptiCache FREE: Perfect for basic caching. Save texts or JSON payloads to localStorage. Pass large amounts of data between pages instantly without using messy URL parameters.

:gem_stone: OptiCache PRO: This is for serious/enterprise apps. We introduced Smart Memory Management:

  • :stopwatch: Auto-Expiring TTL: Set your cache to expire in 30 minutes, 2 hours, etc. The plugin tracks the clock. When time is up, the cache self-destructs so the user never sees outdated “zombie” data!

  • :card_index_dividers: Session Storage: Choose to save data in sessionStorage (which automatically wipes itself the second the user closes the browser tab).

  • :locked: User ID Isolation: Add a User ID to your cache saves. This sandboxes the data, ensuring that if two people share the same computer, they never see each other’s cached preferences.

:link: Check out OptiCache Free: HERE

:link: Check out OptiCache PRO: HERE

Let me know what you think! I’m planning to add server-side Redis integrations in the future for global caching, but for now, enjoy the blazing-fast frontend speeds! :high_voltage: Happy building!

2

What is it using for cache? Is it just session storage?

3

Hi Matthew!

The cache is saved on the browser device local storage up until 5mbs.

For the free version it is only saved as local so you can restart your pc and the data is still there.

For the Pro version you can chose local or session.

Cheers!

4

Hey Bubble community! :waving_hand:

Until today, OptiCache has been helping you save Workload Units (WUs) by storing data locally in the user’s browser. But what happens when you have a public dashboard, a product list, or global settings that thousands of users need to access at the same time?

If you query the Bubble database for every single user, your WU costs will skyrocket! :chart_decreasing:

Today, I am thrilled to announce OptiCache (Pro) V2: The Backend Revolution. :globe_showing_europe_africa::high_voltage:

We have fully integrated native Server-Side Actions powered by Upstash (Redis)—the fastest serverless database on the planet!

:fire: What this means for your app: Instead of a user calculating heavy data and keeping it to themselves, your app can now run a calculation once, save it to the Upstash Redis Server using the new Set Server Cache action, and serve it instantly to every other user using the Get Server Cache action!

  • Zero database reads.

  • Zero complex API Connector setups.

  • Millisecond response times.

  • Massive WU savings.

You can also use the Invalidate Server Cache action to clear the memory globally whenever you actually update the real data in your database.

Upstash offers an incredibly generous free tier, making Enterprise-level caching accessible to every Bubble developer. Setting this up takes less than 2 minutes.

Let me know what you guys think about bringing Redis natively to Bubble! Happy scaling! :rocket::hammer_and_wrench:

5

Hey Bubble Community! :waving_hand:

Are external API calls and heavy database searches eating up your Workload Units (WUs)? Are your users staring at loading spinners every time they navigate your app?

Today, we are officially launching Opticache Pro V3, moving beyond basic browser storage and bringing Enterprise-Grade Distributed Caching natively to Bubble!

Here is how V3 transforms your application’s architecture:

:globe_showing_europe_africa: Multi-Layer Hybrid Caching (L1 ➔ L2 ➔ L3) You no longer have to manage storage types manually. With our new Hybrid Action, Opticache acts as an intelligent retriever. It checks the ultra-fast Session RAM (L1). If missing, it checks Local Disk (L2). If it’s a complete miss, it securely triggers a backend call to your Upstash Redis server (L3). Once found, it automatically pushes the data back to L2 and L1. Subsequent loads happen in 1 millisecond.

:counterclockwise_arrows_button: Stale-While-Revalidate (SWR) - Zero Loaders! This is the same caching pattern used by Next.js, Twitter, and Spotify. If a user’s cache has expired, instead of showing a blank screen or a loading spinner, Opticache instantly displays the old (stale) data while silently triggering a background refresh. Your users get a native, instant-load experience every single time.

:carpentry_saw: Invalidation Trees & Versioning No more “Clear All Cache” nuclear options. Our new key taxonomy ([namespace]:[version]:[user_id]) allows for surgical precision. You can now clear cache only for a specific namespace (e.g., “dashboard”) without deleting “settings”. Or simply bump your API version to v2 and let the engine gracefully ignore legacy data.

:bar_chart: Prove Your ROI (WU Analytics Engine) Every API call via Bubble Backend Workflows costs at least ~0.7 WUs (0.1 outbound + 0.6 backend action + data weight). Opticache V3 actively tracks your Cache Hit Rate locally. Set your average WU cost per call, and expose our new Element States directly on your admin dashboard to see exactly how many thousands of WUs the plugin is saving you in real-time.

V3 is a complete paradigm shift for high-performance Bubble apps. It’s live in the marketplace right now! Upgrade your element, set up your namespaces, and let us know how many WUs you save this week! :backhand_index_pointing_down::fire::high_voltage: