Sanctum: four arms explained — App, Institutions, Ironforge, Token

Sanctum bills itself as the staking layer Solana runs on. On X, @sanctumso splits the house into four named arms — App, Institutions, Ironforge, and Token — each with its own account. That split confuses people who only know “the LST protocol.” This piece maps the four arms and how they relate.

Site: sanctum.so. Docs: learn.sanctum.so/docs. Deeper LST mechanics already on DevRels: Sanctum LST mechanics · Sanctum developer API / Gateway.

Click to zoom

The one-line map

App            retail staking product (INF / LSTs)     @sanctumapp
Institutions   B2B staking-as-a-service                 @sanctumstaking
Ironforge      Web3 DevOps platform                     @ironforgecloud
Token / IR     $CLOUD investor relations                @sanctumIR

Hub            @sanctumso  ·  sanctum.so

Think of @sanctumso as the parent brand. The four arms are distribution channels and product surfaces for different buyers — end users, protocols/CEXes, developers running infrastructure, and token holders / researchers following the business.

1. App — @sanctumapp

What it is: the consumer staking product. Web at app.sanctum.so; mobile called out as Sanctum App (iOS/Android). Users liquid-stake SOL into INF (Infinity) or other Solana LSTs, earn yield, and use Sanctum’s liquidity engine rather than locking native stake with a long unbonding UX only.

Who it’s for: retail holders and anyone who wants LST exposure without running a validator. Infinity is the flagship LST-oriented pool that made launching and swapping LSTs far cheaper by shared liquidity — the mechanics piece covers that path in depth.

Builder angle: if you integrate “stake SOL in our app,” you are usually talking to this surface or the underlying stake-pool / router programs — not Ironforge and not the IR site.

2. Institutions — @sanctumstaking

What it is: Staking-as-a-Service. Sanctum operates white-label validators and/or custom LSTs for partners so brands can earn when users stake SOL with them — without building stake-pool ops from scratch.

Public examples on Sanctum’s materials include Jupiter (jupSOL), Bybit (bbSOL), Drift (dSOL), crypto.com (cdcSOL), DeFi Dev Corp (dfdvSOL), and others. Pitch lines on the institutions page: share of inflation / MEV / block / staking rewards, customizable delegation, liquidity without seeding your own thin pool, managed ops.

Who it’s for: exchanges, wallets, DeFi protocols, and corporates that want a branded staking product and revenue share. Investor pages break out partner LSTs and validator services as material revenue lines — this arm is the B2B engine behind many “branded SOL” tickers users see elsewhere.

Builder angle: launching a partner LST or white-label validator is a commercial + ops integration with Sanctum’s staking team, not a self-serve consumer mint on the App alone.

3. Ironforge — @ironforgecloud

What it is: Ironforge, marketed as a complete Web3 DevOps platform — observability, incident management, networking, and security tooling so app teams spend less time debugging RPC and delivery issues. Sanctum’s homepage also cites large daily request volume through this line.

Who it’s for: engineering teams (wallets, DEXs, bots) that need production visibility — priority fees, compute, provider performance — rather than end users staking SOL.

How it fits: Ironforge is not an LST. It is infrastructure adjacent to “make Solana apps reliable,” sitting next to Sanctum’s staking business under the same parent. Sanctum’s site also lists Gateway (gateway.sanctum.so) for transaction optimize/deliver/observe; that is closely related developer infrastructure. The X bio’s four-arm list names Ironforge explicitly; Gateway is the staking-team’s tx-delivery product on the main site — worth knowing so you don’t merge “DevOps SaaS” and “tx landing API” into one box.

4. Token — @sanctumIR

What it is: investor relations for $CLOUD, Sanctum’s token / community layer — not the place you stake SOL day to day. Public hub: investors.sanctum.so. Related: vote.sanctum.so, research.sanctum.so.

IR surfaces publish business metrics (product revenue breakdown, TVL, treasury) so holders and analysts can see how App + Institutions (+ other lines) translate into numbers. Treating @sanctumIR as “another staking app” is the usual mistake — it is the capital-markets and transparency arm.

How the arms connect

Retail user  →  App (INF / LSTs)
Partner brand →  Institutions (validator + custom LST)
App engineers →  Ironforge (+ Gateway for landing)
Holders / IR  →  Token / @sanctumIR ($CLOUD, metrics)

Shared core: stake pools, LST liquidity (Infinity), Sanctum ops

Infinity and the LST router are the technical center of gravity for staking. Institutions productize that stack for brands. App is the direct-to-user UI. Ironforge (and Gateway) monetize and support the broader Solana builder stack. Token/IR sits above the business for governance and disclosure.

Quick “which account do I follow?”

• Want yield / mobile staking news → @sanctumapp
• Want partner LST / SaaS deals → @sanctumstaking
• Want DevOps / infra product → @ironforgecloud
• Want $CLOUD / financials → @sanctumIR
• Want the umbrella → @sanctumso

Resources

• sanctum.so · Institutions · App · Ironforge · Investor relations
• LST mechanics · Developer API / Gateway
• Sanctum on DevRels

Bottom line

Sanctum’s four X arms are four audiences: retail stakers (App), branded staking partners (Institutions), developers running production stack (Ironforge), and token/IR followers ($CLOUD). Same company, same staking core — different doors. Use the arm that matches the job; read the LST and Gateway deep-dives when you need protocol detail under the App and Institutions doors.