Perpblock

✦ For institutions

Crypto management built to your operational standards.

Perpblock for family offices, RIAs, small funds, and treasury teams. Non-custodial architecture. Custom risk limits. Performance-fee pricing. Dedicated infrastructure. White-glove onboarding. Founder-direct relationship.

Perpblock institutional

Account structure

OwnerFull access · revoke any role
AdminConfigure · no trading
TraderExecute allowed strategies
AuditorRead-only · export access

Risk limits · active

Max leverage
ENFORCED
Max drawdown
−18%ENFORCED
Concentration cap
30% per assetENFORCED
Daily turnover
$2.5MENFORCED

On-chain anchoring

22,099 trades anchored · Base mainnet

Who it's for

Four institutional profiles.

Family offices

Managing $10M-$500M with a direct digital asset allocation. Counsel has cleared SaaS-execution architecture. The operational team needs auditor-grade reporting, multi-user controls, and an external counterparty that can sign a real DDQ.

Registered Investment Advisors

With clients who want crypto exposure but where the RIA cannot custody or trade it directly. Perpblock as the SaaS execution layer the RIA recommends. The RIA continues to advise. We execute. Compatible with the SEC's 2023 position on non-custodial software.

Small and emerging crypto funds

Running $5M-$100M who need execution infrastructure but don't yet have a full engineering team. Strategy library, per-account risk limits, performance-fee billing.

Crypto-native treasury teams

At protocol DAOs, foundations, and operating companies holding native tokens or stablecoin reserves. Yield strategies, hedging overlays, execution against operational policy.

If you have an investment committee, a compliance officer, or an annual external audit, this is the page.

Architecture

SaaS execution. Qualified custodian. No commingling.

Perpblock is software. We are not a broker, not a custodian, not a money transmitter. Your assets remain at the qualified custodian — Coinbase Prime, Kraken, Fireblocks via API, or your existing exchange relationship — per the SEC's 2023 position on non-custodial software providers. We execute against a read-only API key. We hold nothing. We see nothing beyond what the API exposes.

Client assets at custodianRead-only API keyPerpblock execution engineOrder placementSettlement at custodian

At no point in the flow does Perpblock take possession of the asset.

Same architecture 47% of US family offices use to hold digital assets directly. We're built for it, not retrofitted into it.

Read the architecture overview

Operations

What institutions actually need.

Multi-user RBAC

Owner, admin, trader, auditor. Auditor is read-only. Trader can execute against allowed accounts but cannot change configuration. Admin can change configuration but cannot trade.

Custom risk limits per account

Per-account hard caps on leverage, drawdown, instrument, venue, position size, daily turnover, and any other axis your compliance memo requires. Enforced at the execution layer.

Dedicated infrastructure

Isolated compute and execution pipelines per institutional account. No shared rate limits with retail traffic. No noisy neighbors.

Audit log + SIEM stream

Every consequential event written immutably. Stream the log to your SIEM (Splunk, Elastic, Datadog) via webhook for live monitoring.

Cross-account portfolio aggregation

One consolidated view of all sub-accounts. Profit and loss, exposure, risk metrics, market state — one screen, drillable to each underlying account.

The features above are the difference between "could work for an institution" and "is built for an institution."

Operational requirements

Multi-user RBAC

Owner · Admin · Trader · Auditor

Wave 3 · 12mo

Custom risk limits per account

Hard caps: leverage, drawdown, venue, size

Available now

Dedicated infrastructure

Isolated compute · no shared rate limits

Available now

Audit log + SIEM stream

Immutable log · Splunk, Elastic, Datadog

Available now

Cross-account aggregation

Multi-fund consolidated view

Wave 3 · 12mo

Performance

Reporting that survives diligence.

Institutional performance reporting can't be screenshots. The standard is verifiable provenance, defensible methodology, third-party-reproducible numbers.

Per-trade on-chain anchoring

Every trade hashed within 15 seconds of fill on Base mainnet. Verifiable independently.

Quarterly transparency pack signed on-chain

Methodology, lot-traceability standards, anchor receipts, attestation. The pack itself is anchored — verifiable as unmodified after publication.

GIPS-compatible reporting on request

Composite construction, time-weighted return, after-fee returns, dispersion measures. Returns calculated to GIPS 2020 standards where requested.

Tax-lot-level provenance on every disposal

Lot ID, where it came from, accounting method, on-chain proof. Audit-defensible for external review.

Numbers that survive an external auditor's questions. Not just numbers that look good in a deck.

Quarterly transparency pack · Q1 2025
On-chain anchor22,099 trades · Base mainnet
GIPS-compatible return+47.8% TWR · after fees
Max drawdown−18.4%
Profit factor2.43
MethodologyGIPS 2020 · available on request
Pack signed on-chain0x4fa2...9b71 ✓
Pack anchored · independently verifiable

Pricing

Three commercial models.

Flat subscription

$25K–$150K/year

For institutions that prefer predictable budgeting. Annual fee scaled to seats, sub-account count, and operational complexity. No AUM fee. No performance fee.

Performance fee

Subscription + carry

For institutions that prefer alignment via performance fee. Subscription plus an agreed percentage of net realized gains above a high-water mark. Performance-fee terms negotiated per relationship.

Hybrid

Negotiated

Subscription for the platform plus a performance fee on a defined subset of strategies. Common for treasury teams running yield strategies with a defined benchmark.

The commercial structure is negotiated in onboarding. The features and SLAs are the same across all three.

Onboarding

What the first 60 days look like.

01

Initial call

30-45 minutes. We learn your structure, existing custody relationships, compliance constraints, performance expectations.

02

DDQ package

25-40 pages covering governance, security architecture, custody position, performance methodology, audit history, regulatory posture.

03

Technical scoping

We map your exchange relationships, custody arrangements, and reporting requirements. Confirm SSO, multi-user setup, audit-log destination.

04

Test account

We provision a test account with a small allocation. Strategies run in production conditions. Performance anchored on-chain. Typical window: 30-60 days.

05

Production rollout

After test-account approval, we provision production, complete user provisioning, and finalize the technical integration.

The pace is yours. We've moved institutions in 30 days. We've moved institutions in 6 months. Either is fine.

Honest limits

The honest list.

Self-hosted or on-prem deployment

Multi-tenant SaaS only at the moment. On-prem is on the roadmap but not committed.

SOC 2 Type II

In progress. Report not yet published. Status updates on request.

Regional regulatory licensing

MiCA, MAS, ADGM. We operate as US-domiciled software. Not licensed in additional jurisdictions.

Options strategies

The current strategy library is delta-one plus funding arbitrage. Volatility products are not on the immediate roadmap.

Insurance on custodied assets

We don't custody. Our partners do. Insurance coverage on custodied assets is between you and your custodian.

We'd rather tell you what we don't do than have you discover it in week 4.

Common questions

What diligence teams ask.

Get started

The starting point.

Institutional access begins with a 30-minute call with the founder. We use the call to determine whether Perpblock fits your structure and to scope the diligence process. After the call, we send the DDQ and supporting documents for your team's review. Or email directly: institutional@perpblock.com