machine viewenglish onlyraw: /cases/silo-finance.md

Case study — Silo Finance

The entire data layer owned end to end — subgraphs, multichain APIs across 4+ chains — with infrastructure costs cut 80%.

4+ Chains served by one API · 80% Infrastructure costs cut · 5 Build phases from subgraph to multichain API · 99.9% Uptime SLA target

Silo is a permissionless lending protocol where each market is an isolated silo — lenders and borrowers interact within contained risk environments. Running it takes a data layer that keeps up with the protocol: indexers, APIs, and liquidation infrastructure across every chain the protocol reaches.

Shipped:

V2 subgraph: The indexing layer the protocol’s apps are built on

Multichain API: One API across 4+ chains, built in 5 phases from subgraph replacement on

Liquidation infrastructure: Monitoring and execution built for market stress

Chain integrations: New chains brought online on launch timelines

GraphQL API + docs: The data layer, documented for integrators

Outcome: Silo ships a multichain lending protocol while Bleu keeps the data layer running underneath it — end to end, across every chain, at a fraction of the original cost.

Contact: [jose@bleu.builders](mailto:jose@bleu.builders)

THE DATA LAYER, OWNED END TO END

Silo Finance

The entire data layer owned end to end — subgraphs, multichain APIs across 4+ chains — with infrastructure costs cut 80%.

Chains served by one API

80%

Infrastructure costs cut

Build phases from subgraph to multichain API

99.9%

Uptime SLA target

Overview

The core team needed to stay on the protocol, not the plumbing

Each new chain multiplied indexing and API surface

Liquidation infrastructure had to stay reliable under market stress

Costs had to come down without giving up reliability

Our role

Bleu owns Silo’s data layer end to end — subgraph, indexers, multichain APIs, and liquidation infrastructure — while the core team stays on the protocol.

What changed

The data layer stopped being a tax on the core team. New chains land on the protocol’s launch timelines, and one API serves its apps and integrators.

One multichain API across 4+ chains instead of per-chain plumbing
Infrastructure costs cut 80% without giving up reliability
Liquidation infrastructure runs as a monitored, playbook-driven service
New chain integrations land on the protocol’s launch schedule

“Easy to work with. Take ownership, which is not easy. Can be trusted to deliver, also not easy.”

Siros

Silo Finance

ONGOING INFRASTRUCTURE PARTNERSHIP

What we’ve shipped

The entire data layer, owned end to end — while Silo’s team stays on the protocol.

V2 subgraph

The indexing layer the protocol’s apps are built on

Multichain API

One API across 4+ chains, built in 5 phases from subgraph replacement on

Liquidation infrastructure

Monitoring and execution built for market stress

Chain integrations

New chains brought online on launch timelines

GraphQL API + docs

The data layer, documented for integrators

Areas we took ownership of

ONE API FOR EVERY CHAIN

Each new chain used to mean more per-chain plumbing.

Multichain API

Every chain the protocol reached multiplied the indexing and API surface the core team had to carry.

5-phase build from subgraph replacement to full multichain API
Chain-specific indexers feeding one API surface
4+ chains served from a single integration point

RELIABILITY AS THE PRODUCT

Lending infrastructure earns trust under stress, not on quiet days.

Liquidation + monitoring infrastructure

For a lending protocol, the liquidation and data stack has to hold in exactly the moments markets are ugliest.

Liquidation infrastructure run as a monitored service
Playbook-driven incident response and recovery
Infrastructure costs cut 80% along the way

Why this partnership works

Silo’s engineers are protocol engineers. The data layer around the protocol — indexers, APIs, liquidation bots — is critical, but it isn’t the work the core team should be staffing.

Bleu runs that layer as a product: owned end to end, monitored, documented, and optimized for cost — so reliability doesn’t depend on the core team’s attention.

Outcome

Silo ships a multichain lending protocol while Bleu keeps the data layer running underneath it — end to end, across every chain, at a fraction of the original cost.