Anchorage Digital Alternatives for Institutional Custody and Reporting

Compare BitGo, Fidelity Digital Assets, Gemini and Sygnum as Anchorage Digital alternatives, with custody mandate, reporting and transition acceptance checks.

Reviewed by FluidRWA Research Team · November 20, 2026 · Editorial update November 20, 2026

Short answer

Investigate BitGo for a scoped custody proposal, Fidelity Digital Assets for institutional custody and trading, Gemini for its custody approval and reporting workflow, and Sygnum when banking requirements are part of the review. Compare the actual entity, assets, authority, settlement dependencies and exit evidence rather than treating brands as interchangeable.

A new custodian must take over the obligation, not just receive the coins

The withdrawal is approved, the receiving address is ready, and finance is waiting for a statement that explains the movement. Then somebody notices that an asset is staked, a second account has a pending trade, and an old corporate-action record exists only in the incumbent portal. The transfer looked like a wallet operation. The institution is actually changing an operating relationship.

That is the right starting point for Anchorage Digital alternatives. Identify whether you are selecting a new custody service, adding a second custodian or replacing an existing arrangement. Those decisions have different consequences for account ownership, asset availability, trading connections, reporting and incident response. A shortlist should follow the mandate rather than precede it.

Anchorage Digital presents custody alongside trading, self-custody, staking and financial infrastructure. This guide compares the custody-service decision. It does not assume another custody account replaces every product or relationship a customer may use under the Anchorage Digital brand.

Four custody alternatives, alphabetically

Alternative and primary sourcePublished starting pointFit to investigateClarify before selection
BitGoCustody, self-custody and related institutional servicesA custody-service proposal connected to wider asset operationsExact product, entity, authority and account model
Fidelity Digital AssetsInstitutional custody and tradingAn institutional custody relationship with defined trading needsInstitutional service scope rather than retail-product assumptions
GeminiCustody with MPC, portal and API workflowsA proposal joining custody operations with an accessible reporting interfaceEntity, approvals, available assets and service commitments
SygnumDigital-asset custody within a banking offeringA custody proposal considered alongside banking requirementsWhich entity, jurisdiction and contracted services apply

These are investigation paths, not equivalent bundles or a ranking. A provider may offer several account types, and a brand may operate through different entities. Require the proposed agreement to identify the service and customer eligibility. Do not substitute a group's marketing footprint for a review of the entity that would actually serve the institution.

Write the custody mandate before requesting proposals

Start with the assets and the reason they are held. Long-term reserves, operating liquidity, client assets and collateral positions can require different controls. Record the owning entity, authorized decision makers, intended activities and reporting obligations. The mandate should tell a candidate what it must safeguard and how the institution expects to use it.

Separate must-have activities from possible future activities. A future interest in a network or staking service should not obscure whether the core custody arrangement works for today's holdings. Conversely, a critical activity should not be left as an informal expectation because the custody account itself is available. Have the responsible business owner approve the launch scope.

Ask counsel and compliance to specify the evidence needed for the mandate, including any applicable custody or safeguarding requirements. This article does not determine whether a particular entity satisfies those requirements. The procurement process should collect exact agreements and relevant regulatory records for professional review, rather than turn a product description into a legal conclusion.

Ten criteria for a defensible custody comparison

The following table describes evidence to request. It does not score providers or establish that any proposed contract includes every item. A material failure should remain a condition of approval even if other parts of the demonstration are convincing.

CriterionEvidence to obtainAcceptance exercise
Service entityProposed agreement and eligibilityConfirm which entity accepts the institution
Ownership recordsAccount structure and statementsReconcile ownership independently
Asset coverageExact asset, network and activity listDemonstrate a permitted deposit and withdrawal
Withdrawal authorityInitiation, approval and review rulesReject an unauthorized or changed instruction
RecoveryAccess restoration and emergency proceduresOperate with an unavailable approver
Settlement linksCounterparty and release conditionsResolve a pending obligation
ServicingRewards, staking and asset-event recordsReconcile an event to the institution's books
ReportingFormats, identifiers and correction historyReproduce a period-end reconciliation
Risk evidenceFinancial, operational and insurance scopeIdentify exclusions and accountable owners
ExitTransfer, export and closure supportRehearse a limited transition with residual cases

Request artifacts that the operating team can use, not only descriptions of controls. A policy document may explain an intention; an approved instruction and its audit trail demonstrate how that intention was applied to the proposed account. Keep those forms of evidence distinct when the committee reviews the shortlist.

BitGo: specify the custody product you intend to buy

BitGo distinguishes custody and self-custody products. That distinction matters when the institution is comparing a service relationship rather than only wallet technology. Ask the proposal to name the specific product and entity, without assuming that every product under the brand carries the same responsibilities.

The practical evaluation should follow an instruction from internal approval through the provider's acceptance and final reporting. Ask who can change an address, who can approve a withdrawal and what evidence the institution receives. Test the relationship between account permissions and API access. A convenient integration should not create an alternate authority path that the custody policy never considered.

BitGo belongs in the investigation when the institution wants a scoped custody proposal and related operational connections. Do not select it merely because another product from the same group appears suitable for a separate treasury or trading workflow. Ask which services require additional agreements, onboarding, collateral arrangements or operational approvals before including them in the implementation plan.

Fidelity Digital Assets: keep the institutional service in view

Fidelity Digital Assets presents institutional custody and trading separately from retail Fidelity Crypto access. Evaluate the institutional arrangement actually being proposed. Familiarity with a retail account does not establish the account hierarchy, controls or reporting needed by a fund, adviser or corporate treasury.

Prepare a demonstration brief that names the asset, account ownership, authorized roles and desired trading relationship. Ask how records connect across custody and execution, and what remains the institution's responsibility. Include a trade that does not settle as expected. The team should know where the unresolved obligation sits and who can provide authoritative evidence of its status.

This is a useful starting point when an institution is reviewing custody alongside a defined trading requirement. It should not be treated as proof that every asset or operational configuration is available. Obtain the exact scope, support process and reporting deliverables for the mandate, then assess those against the same acceptance exercises used for the other candidates.

Gemini: test the current approval and reporting experience

Gemini's custody page describes MPC and portal or API access for balances, withdrawals and statements. Use that current description rather than assuming the service is defined only by older cold-storage accounts. Architecture and service terms are different diligence questions.

Ask the team to demonstrate an approved-address change followed by a withdrawal. Show how the institution's permissions, provider review and audit records interact. Then attempt the same operation through the API. The question is whether the proposed interfaces preserve the agreed approval model, not simply whether both interfaces exist.

Gemini belongs in the shortlist when the institution wants to investigate that custody and reporting workflow. Request the exact asset coverage, contracting entity, approval configuration and support commitments. Public descriptions of insurance or assurance should lead to a request for relevant scope and exclusions, not an assumption that every loss or customer balance is covered.

Sygnum: compare the entity and banking scope explicitly

Sygnum's custody page places custody within a wider digital-asset banking offering. Its public custody-fee explanation describes a volume-related annual basis-point model. Obtain the current proposal for the actual entity and services rather than extrapolating from a historic price sheet.

The institution should state whether banking services are part of the purchase or merely adjacent context. Identify which accounts, cash movements and custody records need to reconcile. A combined commercial conversation can be useful, but the operational owners still need to understand the boundaries between custody, trading, payments and any financing relationship.

Sygnum is an investigation path when those connected requirements matter to the mandate. Do not generalize one entity's terms or jurisdictional position across the group. Ask the proposed contracting entity to identify supported assets, onboarding requirements and operational restrictions, and have the relevant advisers review the resulting arrangement.

Adding a second custodian is different from replacing the first

A second-custodian project can reduce dependence on one operating relationship, but it also introduces more accounts, permissions, reconciliations and support paths. Define the purpose: continuity, a specific asset, a particular activity or an approved concentration policy. Do not add a second account simply to create the appearance of diversification.

Decide how balances and activity will be allocated. A policy might separate operating liquidity from longer-term holdings or assign certain activities to a particular approved service. Whatever the model, the institution should be able to explain it from its own records. Allocation should not depend on a person remembering why an asset was moved last month.

Test a transfer between the two approved arrangements and reconcile both sides. Retain references linking the internal instruction, outgoing record, receiving confirmation and finance entry. A successful onchain movement is only one part of the evidence. Confirm that both services and the internal ledger agree about which entity owns the resulting position.

An illustrative transition packet

Consider a fictional fund with three custody accounts. One holds immediately transferable assets, one contains a pending settlement obligation and one has an activity that requires a separate release process. The example is not a description of any named provider. Its purpose is to make transition dependencies visible before someone promises a single transfer date.

Create a position inventory at an agreed cutoff. Record available quantity, pending movements, restrictions, fees and the owning entity. Have operations and finance review the same packet. A balance reported as held is not necessarily available for immediate transfer, and an instruction accepted by a provider is not necessarily complete.

Move a limited eligible position first, with the institution's required approvals. Compare the debit, fees, receiving credit and accounting entry. If any reference or quantity differs, stop expansion and investigate. The exercise should produce evidence that the operating team can explain, not merely a transaction hash that cannot be tied to the original business instruction.

Keep the pending obligation with an explicit owner and resolution route. Do not erase it from the transition tracker because the associated account is no longer part of the future-state architecture. Closure should follow completion or an approved transfer of responsibility. That distinction prevents a technically successful migration from leaving an institution with an unsupported historical case.

Withdrawal controls need to survive interface changes

Map the internal request, provider instruction, approval, signing and final record as separate steps. State which party can amend each field and what happens when a meaningful detail changes. A changed destination or amount should not inherit approval silently because the original request had already passed a review.

Use a rehearsal with an unavailable approver. Ask how ordinary escalation differs from emergency recovery and which evidence is retained. The objective is not to find a shortcut around the approval model. It is to establish how authorized activity can continue when the usual staffing assumption fails.

Repeat the exercise for privileged configuration changes. Removing a withdrawal permission is not sufficient if the same person can grant it back through another administrative role. Review API keys, account administrators, recovery contacts and policy-editing authority together. Ask the supplier to explain the proposed control boundary in terms the institution's risk owners can approve.

Settlement connectivity is not the same as final settlement

A connection to a trading venue or network can simplify instructions while leaving credit and settlement obligations with separate parties. Identify who owes what, which assets are committed and what evidence releases the obligation. Request the applicable terms for the actual arrangement, rather than infer them from a connectivity diagram.

Test an interrupted settlement and a disputed status. The institution should know which record is authoritative, who investigates and whether another movement is safe. Blindly repeating an instruction can create a second obligation rather than repair the first. Retain durable references and an agreed status-retrieval process before enabling automated recovery.

For a custody change, inventory those connections separately from asset balances. Some may require new admission, account mapping or counterparty confirmation. Plan each dependency as a release condition. A receiving wallet can be ready while the broader settlement arrangement is not, and the migration plan should make that difference obvious.

Reporting must explain history as well as current balances

A custody statement is useful when finance can connect it to internal records. Ask for durable account identifiers, transaction references, fees, asset identifiers and correction history in the agreed format. A dashboard total can support a quick check, but it does not necessarily supply the evidence required for period-end review.

Choose a closed period and reconstruct it using the proposed exports. Include a transaction that was corrected after the initial statement. The reviewer should be able to distinguish original evidence from replacement output and explain the reason for the change. Do not approve a process that overwrites history without leaving a usable trail.

Define the time boundary carefully. A chain event, provider accounting entry and internal ledger posting can occur at different times. The team needs a documented reconciliation rule, not an assumption that all systems close simultaneously. Record exceptions and their owner so a temporary timing difference does not become an unexplained long-term balance.

Staking and tokenized-asset servicing require their own questions

Custody of an asset does not automatically include every activity associated with it. If the mandate involves staking, request the actual workflow, approvals, availability constraints, reward records and exit process. Have the relevant risk owners approve the activity separately from approval of the custody account.

For a tokenized interest, identify which party maintains the authoritative investor record and handles issuer communications or restrictions. A custody balance and an investor's legal or operational eligibility can be different records. The institution should know whom to contact when a transfer is blocked or an issuer requires updated evidence.

Include those dependencies in transition acceptance. A receiving account that can hold the token may not yet be ready to complete a distribution, redemption or other servicing event. Ask the issuer, administrator and proposed custodian to confirm their roles. Do not use a generic supported-asset entry as a substitute for that complete operating conversation.

Insurance and assurance belong in the risk file

Request the actual scope relevant to the proposed service: insured parties, limits, exclusions, claims handling and any material sublimits or aggregate constraints. A public headline figure is not enough to calculate the institution's protection. Qualified advisers should review the documents where the decision requires legal or insurance expertise.

Treat operational assurance separately. An assessment may cover a defined service, period and control environment while leaving customer responsibilities that the institution must implement. Ask how the proposed account, interfaces and operating model fit that scope. A certification logo does not complete the institution's own access, reconciliation or recovery work.

Record what the committee is accepting and what remains a condition. Avoid turning incomplete evidence into a confident numerical score. If a material issue remains unresolved, it should be visible in the approval record with a responsible owner. That is more useful than presenting a polished comparison that conceals the hardest risk decision.

Price the relationship across its full lifecycle

Ask candidates how custody, transactions, optional activities, support and account structures are charged. Model the same asset holdings and activity for each proposal. Do not assume an annual custody rate, a minimum charge and a transaction fee can be compared without understanding the service they purchase.

Include the institution's own operating effort. More manual approvals or reconciliation work can matter even when the supplier's recurring fee is lower. The relevant tradeoff is not automatically good or bad; it should be visible. Ask operations to estimate the work from a rehearsal rather than from a marketing impression.

Add migration, overlap and termination scenarios. Request retained access to historical records, later statement corrections and support for residual cases. Define when an account can actually be closed and which obligations survive closure. An exit estimate based only on transferring the remaining assets can miss the work required to preserve a defensible history.

Ten questions for the custody decision

  1. Which exact entity and service agreement would accept our institution?
  2. Which assets, networks and activities are included at launch?
  3. How are ownership, account segregation and statement records established?
  4. Who can initiate, approve, amend and recover a withdrawal?
  5. How do API permissions interact with the account's approval policy?
  6. What happens to pending trades, restricted positions and servicing events during transition?
  7. Which event proves settlement and permits finance to close the obligation?
  8. What insurance and assurance evidence applies to our proposed arrangement?
  9. Can we reconstruct a corrected reporting period from exportable records?
  10. What must be completed before historical access and the incumbent account can be retired?

A sound decision may be to retain the existing service while adding a narrowly scoped second arrangement, or to delay a transition until a material dependency is resolved. The purpose of alternatives research is a better operating decision, not pressure to replace an incumbent. Preserve the reasons, evidence and conditions in the approval memo.

How we compare and what changed

FluidRWA reviewed the linked primary product pages on November 20, 2026 for the limited service descriptions above. These are not independent security tests, legal determinations, insurance analyses or live custody trials. The fictional transition packet and acceptance exercises are proposed buyer work. No universal winner, comparable performance score or customer-specific price is asserted.

Use the Anchorage Digital profile and custody directory to organize the shortlist. Related reading includes Anchorage Digital vs BitGo vs Fireblocks, institutional custody models, Fireblocks vs BitGo vs Copper, and Fireblocks alternatives.

Change note, November 20, 2026: Created an institutional custody alternatives guide covering mandates, account ownership, settlement dependencies, reporting continuity and controlled exit. Submit your requirements with the owning entity, assets, intended activities and existing relationships so providers can propose the same scope.

FAQ

What are the best alternatives to Anchorage Digital?

BitGo, Fidelity Digital Assets, Gemini and Sygnum are starting points for an institutional custody review. The appropriate proposal depends on the actual contracting entity, asset and activity scope, withdrawal authority, reporting and settlement needs. They are not equivalent bundles.

Should we replace our custodian or add a second one?

Define the objective first. A second arrangement can address a particular asset, activity or continuity requirement, but adds permissions and reconciliation work. A replacement must also preserve history and resolve residual obligations. Test the intended operating model before approving expansion.

Does a supported asset list establish staking or tokenized-asset servicing?

No. Request the exact activity, network and service terms. Staking, issuer eligibility, corporate actions and redemption can require separate workflows and counterparties. Have the responsible operators confirm each required function.

How should institutions evaluate custody insurance?

Request policy scope, insured parties, limits, exclusions and claims handling for the proposed arrangement. Do not assume a public headline amount protects every client, asset or loss. Obtain qualified advice where the decision requires it.

What is the key reporting test before a custody change?

Reconstruct a closed period from account and transaction exports, including fees and a later correction. Reconcile the result to internal books and retain the original and revised evidence. A current balance alone does not demonstrate historical continuity.

When is a custody transition complete?

After assets and records reconcile, pending obligations and servicing cases have owners, successor access works and residual support is agreed. Transferring the final available asset is not necessarily the end of operational responsibility.

Compare custody arrangements

Build a shortlist around the owning entity, assets, approvals, settlement and reporting requirements.

Explore Custody ProvidersSubmit Requirements