Salt

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.

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.

• 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.