§ 01 — THE PROBLEM

Three quiet failures. Every SPV runs into them.

Investors don't ask about custody until something goes wrong. By then it's too late to make custody look credible. These are the three failures that surface most often in due diligence — and the three that an independent custodian eliminates by structure.

Failure 01

Investors want proof. You can't give it without trusting yourself.

You hold the documents. You wrote the spreadsheet that lists them. You sent the email that summarizes them. Every artifact pointing to "we have your subscription documents" originates from you. That is not custody; that is self-attestation.

"How do I know you actually still hold that FPA?"
Failure 02

Fund administrators don't solve this — and they cost more than the SPV.

Traditional fund admins charge $25k–$75k/year per SPV, and their "custody" is an Excel cell that says "yes." Bringing one on for a single-asset $5–20M SPV destroys the economics. Most sponsors skip it; investors notice. Fund Base Camp instead provides a lightweight per-SPV custody pricing structure designed specifically for private-market vehicles.

"We don't use a fund admin for vehicles this size."
Failure 03

Building your own proof system isn't worth your engineering quarter.

You could build the hashing, the anchoring, the verification page, the receipt PDF generator, the audit pipeline. You won't. You'll do the deal first and write a note saying "we'll add custody verification in v2." That note will still be open in two years.

"We'll add the verification page after the close."
§ 02 — WHAT WE SHIP

Drop documents in. Get verification codes out.

The full system, wired and tested. You upload via dashboard or API; we hash, anchor, store, and issue codes. Your investors receive their codes at subscription and verify on demand — without ever asking you.

Per-SPV isolated custody storage

AES-256-GCM at rest, KMS-managed keys, CloudTrail logging on every object access. One bucket and one keyring per sponsor SPV — no commingled data.

SHA-256 hash, anchored to Bitcoin

Every document is hashed on deposit and the digest is anchored to OpenTimestamps. ≥3 Bitcoin confirmations make the anchor mathematically final.

Transaction codes per investor & sponsor

Opaque, fixed-length, case-insensitive codes embedded in subscription confirmations. Format: FBC-[series]-[role]-[ticket].

Public verification page & API

Investors verify at the public verification portal; engineers integrate via GET /api/v1/verify/{code}. No account, no auth, rate-limited.

Receipt PDF, signed and printable

One-click downloadable PDF with the full custody record, anchor reference, and instructions for offline re-verification. Belongs in the investor's records.

Annual independent CPA attestation

A licensed CPA firm runs Agreed-Upon Procedures over Fund Base Camp's records each year. The report PDF is published openly. Every verification response references it.

E&O + crime + cyber + D&O insurance

Carriers, limits, and effective dates are disclosed on the security and insurance disclosures page. Coverage is appropriate to the asset values under custody — and provided to your prospects on request.

Legal scaffolding included

Custody Services Agreement, PPM disclosure language, AUP scope template, and disclosure form for investor-facing documents — drafted and ready to execute.

§ 03 — ONBOARDING

Live in five days. Including the contract.

The legal and technical work has already been done. Onboarding a new sponsor is repetitive, not bespoke — so we treat it that way. Most sponsors begin by reviewing the Custody Services Agreement framework and operational requirements.

01

Discovery call & scope sheet.

Thirty minutes. We confirm which SPVs are in scope, expected document volumes, whether you need API integration or just the dashboard, and any sponsor-specific disclosure requirements.

Duration≈ 30 minutes · live or async Outputscope sheet · price quote
02

Sign the Custody Services Agreement.

Counsel-reviewed template, lightly negotiated. Standard turnaround is two business days. The CSA covers indemnification, insurance, attestation cadence, and the operational separation guarantees that make the independence story credible to your investors.

Duration≈ 2 business days Negotiablelimits · cadence · termination
03

Provision storage & issue API keys.

We spin up your per-SPV storage bucket, generate ingestion API keys, and pre-populate transaction-code ranges for any SPVs you're about to close. Dashboard credentials are issued to designated sponsor users, with implementation details available through the integration and API documentation.

Durationsame day, after CSA Outputcredentials · API docs · code ranges
04

Deposit the first batch & co-test verification.

Upload your initial documents. We hash, anchor, and confirm the codes resolve on the public verification page. You receive a sample receipt PDF for each. Embed the verification link in your subscription confirmation template, and you're live.

Duration≈ 1 business day Resultlive · verifiable · printable
05

Optional: integrate into your investor portal.

If you run a portal (InvestNext, Juniper Square, your own), we'll provide widget code to embed the verify endpoint so investors don't leave your site. The widget is read-only and accepts the transaction code as a parameter.

Duration≈ 2–4 hours engineering Surfaceiframe · JSON · server-to-server
§ 04 — INTEGRATION SURFACE

Three endpoints. That's the API.

Ingest, verify, and download. We don't believe in expansive surface area for the kind of system whose entire value is being narrow and auditable. Additional infrastructure disclosures and operational controls are documented on the security architecture page.

Endpoint
Purpose
Surface
POST/api/v1/ingest
Sponsor-side. Upload a document, attach metadata (SPV, role, document type, executed date), and receive the SHA-256 digest, deposit timestamp, and resulting transaction code linkage.
multipart/form-data · auth: Bearer + HMAC · idempotency-key required
GET/api/v1/verify/{code}
Public, read-only. Returns the custody record: SPV, documents, hashes, anchor reference, latest attestation. No identity returned, no authentication required.
application/json · rate-limited per IP · 200 / 404 / 429
GET/api/v1/receipt/{code}.pdf
Public. Returns the printable PDF receipt for a verified code — self-contained, including .ots proof references and offline verification instructions.
application/pdf · same rate limits as verify
WEBHOOKanchor.finalized
Sponsor-side. Optional. Fires when a deposited document's anchor reaches ≥3 Bitcoin confirmations. Useful for portals that show investors "anchor pending" → "anchor final" state.
POST to sponsor URL · signed with HMAC-SHA256 · retried 3×
EMBED/embed/verify.js
Drop-in widget for sponsor portals. Renders the verify endpoint with sponsor styling tokens applied. No iframe required, no data leaves sponsor domain except the code.
≈ 8 KB gzipped · zero dependencies · CSP-safe
§ 05 — PRICING

Per-SPV, predictable. No per-investor surcharge.

Pricing is annual, per active SPV under custody. There is no per-investor or per-document fee — the unit economics of custody don't scale that way, and we don't price them that way. Independent attestation and insurance allocations are bundled. Sponsors comparing service levels can also review the broader sponsor infrastructure overview.

Tier 01 — Starter
Single SPV.
Light volume.

For one-off vehicles, single-asset SPVs, family-office club deals, and proof-of-concept onboarding before broader rollout.

  • One SPV under custody
  • Up to 50 documents / year
  • Dashboard + public verify
  • Annual AUP coverage prorated
  • Email support
Quote me
Tier 03 — Enterprise
Custom volume.
Custom terms.

For platforms with their own admin team, institutional reporting requirements, or unusual document volumes. Custom AUP scope, custom insurance allocation, custom SLA.

  • Unlimited SPVs
  • Unlimited documents
  • Dedicated isolation
  • Custom AUP / SOC 2 coordination
  • Custom insurance lines
  • Quarterly business reviews
Talk to us

Note   Pricing is private and provided per scope sheet. Most sponsors at Tier 02 budget roughly the cost of a single mid-tier engineer-week per year, per SPV under custody. For context: at a 4% placement fee on $10M of subscriptions, custody runs well under 5% of placement.

§ 06 — LEGAL SCAFFOLDING

Contracts. Disclosures. All drafted.

Each one is the artifact your counsel would produce if they billed for a week. We've already produced them. Your counsel can red-line; you don't have to start from a blank page. Supporting disclosures, policies, and operational notices are also available through the Fund Base Camp legal documentation center.

Doc 01 · Master

Custody Services Agreement

The master contract between FBC and sponsor. Covers indemnification, insurance carriage, attestation cadence, termination, and operational independence covenants.

EXECUTED · standard template
Doc 02 · Disclosure

PPM custody disclosure

Drop-in disclosure language for PPMs and subscription documents referencing FBC as custodian, the verification flow, and the independence relationship.

EXECUTED · counsel-reviewed
Doc 03 · Attestation

AUP engagement template

The agreed-upon-procedures scope shared with the CPA firm — sampling methodology, anchor verification, attestation publication path. Adapted per sponsor as needed.

EXECUTED · standard scope
Doc 04 · Insurance

One-page insurance summary

Carriers, lines, limits, effective dates. Provided to sponsor's prospects on request and published at /security. Refreshed at each policy renewal.

EXECUTED · refreshed annually
Doc 05 · Investor

Investor-facing verification guide

A two-page PDF you can include in subscription packets explaining what FBC is, what the code does, and how the investor can verify independently.

EXECUTED · co-brandable
Doc 06 · Ops

Independence covenant

The covenant by which FBC commits to operational separation from any one sponsor — separate signers, accounting, banking, IT. Required by D&O and disclosed in CSA.

EXECUTED · disclosed
Doc 07 · API

Sponsor integration spec

Engineering-facing API documentation with endpoint reference, authentication scheme, idempotency, and example payloads. Versioned semantically; deprecations announced 12 months ahead.

DRAFT · v0.9 · feedback welcomed
Doc 08 · SOC 2

SOC 2 readiness map

The control mapping FBC is using to prepare for SOC 2 Type I (year 1) and Type II (year 2). Available to sponsors and their counsel under NDA on request.

DRAFT · under counsel review
§ 07 — CONTACT

The sooner we start, the cleaner your next close looks.

Most sponsors who reach out close their next SPV with FBC custody disclosed in the PPM. The window for "we'll add this later" closes the moment a sophisticated allocator does their first round of diligence. Better to have the answer ready by reviewing the full custody and verification workflow before your next close.

DIRECT
sponsors@fundbasecamp.com

ENGINEERING
engineering@fundbasecamp.com

SECURITY
security@fundbasecamp.com

MAIL
Fund Base Camp LLC
1200 Coffeen Ave
Sheridan, WY 82801
United States