
Salt
Salt faced a bottleneck: their developers were spending too much time fighting flaky RPC infrastructure rather than building the product. By partnering with us, they removed that hurdle, letting the team focus entirely on the app — and delivered reliable web3 experiences on par with web2.
Published October 23, 2025
“RPC reliability was crippling our dApp workflow — our devs were spending more time fighting backend infra than building the app. Once you took over the RPC layer, we could stop worrying and focus entirely on Salt’s features. The user experience improved, scaling became manageable, and everything just got smoother.”— Jason (CTO)
The Challenge
Salt’s users expect web2-grade reliability from their dApp experience. But developing in web3 means relying on RPC endpoints and blockchain infrastructure, which can be unpredictable, slow, or flaky. For Salt this meant:
- Developers spending time managing backend infrastructure layers (RPC endpoints, failovers) instead of building features for their app.
- Unreliable RPC access creating hidden costs, slower iteration, and risk of poor user experience.
- The need for a partner who could guarantee high availability, support burst traffic, and relieve Salt of the infrastructure burden so their devs could focus on the product.
The Solution
We stepped in to handle the heavy lifting:
- We provided robust RPC infrastructure with high reliability, so Salt’s developers didn’t have to build or maintain it themselves.
- We supported the bursty traffic patterns typical in web3 — so when Salt’s dApp usage spiked, the backend held up without them needing to scale it themselves.
- We freed the Salt team to focus purely on app development, user flows and product features, rather than backend reliability concerns.
- Through our partnership, the infrastructure became a solved problem for Salt — letting them allocate developer resources toward features and growth.
The Results
- Salt’s development team shifted focus away from “infrastructure firefighting” and back to building the experience their users expect.
- Backend reliability improved — fewer outages, smoother user flows, less manual intervention needed.
- The user experience improved — aligning more with the “web2-level” expectation Salt’s users have.
- Salt was able to scale features and growth without the equivalent scaling burden on infrastructure.
Significantly reduced
Developer time spent on infra vs product
Improved noticeably
RPC reliability / backend downtime
Faster due to fewer infrastructure blockers
Time to roll out new features