Squads Labs

• Name: Squads Labs
• URL: https://squads.xyz/company
• Category: smart-account and stablecoin-finance operating company / multisig-plus-API operator / Solana account-control entity
• Tags: solana-ecosystem
• Summary: Squads Labs belongs in companies/ because the analytically useful question is not only how do Squads Protocol smart accounts work? but which named operator is packaging multisig, business accounts, consumer wallet flows, and Grid APIs into one hosted company shell around those accounts? The public site says Squads Labs is a financial technology company building products and APIs for the stablecoin economy, while the terms define the service relationship with Selimor Investments Limited ("Squads"). That boundary matters because the company, not the protocol alone, controls the site, app, API/platform terms, onboarding flow, supported account products, vendor-composed rails, and the business-facing workflow around Altitude, Fuse, Grid, and Squads Multisig.
• What it does:
  • Operates the public Squads site and company-branded product shell around Squads Multisig, Altitude, Fuse, and Grid
  • Packages Squads Protocol smart accounts into hosted business-account, wallet, payments, cards, and yield workflows rather than leaving them as a raw protocol primitive
  • Defines the contractual platform boundary for the Squads Platform, including the site, apps, documentation, and services offered to customers
  • Composes self-custodial smart accounts with third-party services for fiat rails, cards, payments, rewards, trading, and yield workflows
  • Markets Grid as the stablecoin API for accounts, payments, cards, and yield, with onboarding, key-management-diversity, and account-model packaging controlled at the company layer
  • Sits as the named operator boundary above the protocol whenever the sharper question is about product defaults, account onboarding, service packaging, or the practical workflow customers inherit first
• Key claims:
  • The company page says Squads is a financial technology company building products and APIs for the stablecoin economy and explicitly lists Altitude, Fuse, Squads Multisig, and Grid as the product set built on its infrastructure
  • The homepage says Squads Labs is a financial technology company, not a bank or a digital asset custodian, which is useful because it makes the entity boundary explicit while also clarifying how the company wants the trust posture understood
  • The terms say the agreement is between the customer and Selimor Investments Limited ("Squads") and that the Squads Platform includes the site, apps, and services, which is strong evidence that the operator boundary is not just inferred from branding
  • The same terms define Altitude Accounts, Fuse Wallets, Multisigs, and Smart Accounts as productized account types deployed via Squads Protocol, which is exactly why the protocol note and the company note should not be flattened together
  • The terms also say Squads is not a bank and that third-party services connect the accounts to payment, card, rewards, and yield flows, which makes the company boundary useful for understanding where protocol mechanics stop and vendor-composed operating workflow begins
  • The Grid page says the API supports accounts, payments, cards, and yield, highlights email onboarding, key-management diversification, and multiple account models, and frames the company as the production packaging layer above the open-source protocol foundation
  • The multisig docs still pitch a traditional SaaS-like product experience wrapped around onchain asset management, which is a useful reminder that the practical onboarding and UX shell remains company-shaped even when the underlying account rules live onchain
• Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials are the current company page, protocol page, terms, Grid page, and multisig docs, captured in ../whitepapers/squads-company-primary-sources-2026-08-11.md.
• Sources:
  • https://squads.xyz/
  • https://squads.xyz/company
  • https://squads.xyz/protocol
  • https://squads.xyz/grid
  • https://squads.xyz/legal/terms-of-service
  • https://docs.squads.so/main
  • https://raw.githubusercontent.com/Squads-Protocol/v4/main/README.md

Internal linkages

• Protocol-layer note: squads.
• Useful signer / treasury comparison set: safe, fireblocks, bitgo, and privy.
• Useful adjacent stablecoin-finance operator comparison set: bridge-xyz, modern-treasury, and stripe.

Protocol / company boundary

• squads should stay focused on the onchain smart-account and multisig surface: approval rules, vault semantics, program upgrade authority handling, validator management, role and timelock capabilities, and the broader autonomous finance layer framing.
• This note isolates the company boundary where Squads Labs packages those accounts into business accounts, consumer finance, payments, cards, yield, onboarding, support, and API workflow.
• The useful analytical question is not does Squads use smart accounts? It is which parts are protocol-enforced account mechanics, and which parts are company-packaged product and access workflow built on top of those accounts?
• That split matters because the same public materials that emphasize self-custody and onchain enforcement also define a company-run platform, apps, terms, and product surface that many users and integrators will treat as the default way to reach Squads at all.

Control surface

• Practical leverage sits in product packaging, onboarding, supported account modes, API and app workflow, third-party service composition, and what the company chooses to make easy around the smart-account substrate.

• Grid makes the company boundary especially concrete: stablecoin accounts, payments, cards, yield access, key-management-diversity packaging, and account-model choices are presented as one integrated service shell above Squads Protocol.

• Altitude and Fuse extend the same pattern into business and consumer finance. The protocol may enforce account logic onchain, but the company still shapes the first-party workflow, partner composition, and service envelope most customers inherit.

• Read the durable risk here as packaging power around a protocol-native account stack: the protocol explains how authority is enforced, but the company still decides how much of modern-money workflow gets mediated through its own apps, APIs, support channels, and vendor composition.

• Last reviewed: 2026-08-11 UTC