machine viewenglishraw: /cases/silo-finance.mdbuild: d68074d2026-08-05T14:02Z

Case study — Silo Finance

Industry: Financial infrastructure

Infrastructure costs cut 80% and one API serving 4+ chains. Bleu owns the entire data layer of Silo, a lending platform — indexing, multichain APIs, liquidation — while Silo’s team keeps building the product.

80% Infrastructure costs cut · 4+ Chains served by one API · 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

Contact: [Start a conversation](https://bleu.builders/contact/)

Financial infrastructure · FROM SUBGRAPH TO SETTLEMENT · ONGOING

Silo Finance

80%

Infrastructure costs cut

Chains served by one API

Build phases from subgraph to multichain API

99.9%

Uptime SLA target

The problem

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. Silo’s team keeps building the product.

What changed

New chains land on launch timelines, and one API serves apps and integrators.

One multichain API across 4+ chains instead of per-chain plumbing
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

Areas we run

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

bleu / silo-v2-ponderPublic

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 cost treated as a product metric

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

RELATED OFFERING

See how Bleu structures this kind of work

The case shows what happened in one partnership. The offering explains the entry point, scope, and first delivery.

See the offering: 1 → 100

Bring us the problem.

Tell us what is going on. After you send it, the calendar opens so you can choose 15 minutes.

See how we work

15 MINUTES · A CLEAR NEXT STEP.