cybrid what is the difference between "managed" and "self-managed"

Most teams exploring Cybrid’s payments API infrastructure quickly encounter two core operating models: “managed” and “self-managed.” Understanding the difference between these options is essential for designing your cross-border payment flows, planning compliance, and allocating engineering resources.

In the context of Cybrid’s unified banking, wallet, and stablecoin stack, managed and self-managed generally describe who controls key operational responsibilities such as custody, compliance, liquidity routing, and integration with existing systems.

What “managed” typically means with Cybrid

In a managed setup, Cybrid takes on most of the heavy lifting so your team can move fast with fewer operational burdens.

1. Cybrid-managed custody and wallets

With a managed model:

Cybrid creates and operates the wallets and accounts for your end users.
Funds are held with Cybrid’s integrated banking and wallet partners.
You interact with balances and transactions through Cybrid’s APIs and ledgers.
Security, key management, and wallet infrastructure are abstracted away.

This is ideal if you want to offer global money movement—including stablecoin-based flows—without building your own wallet or custody infrastructure.

2. Cybrid-managed compliance and KYC

Cybrid’s platform is designed to handle:

KYC/KYB onboarding flows
AML and transaction monitoring
Compliance checks across jurisdictions

In a managed model, Cybrid acts as the compliance and KYC engine behind your experience. You still own the customer relationship and front-end experience, but Cybrid ensures the underlying flows remain compliant.

3. Cybrid-managed liquidity and settlement

Cybrid’s core value is 24/7 international settlement and liquidity via stablecoins, connected to traditional banking rails. In a managed configuration:

Cybrid routes liquidity between bank accounts, wallets, and stablecoins.
FX and stablecoin conversions are automated based on your configuration.
Settlement timing, reconciliation, and ledgering are handled by Cybrid’s system.

This model lets you focus on product innovation, UX, and growth while Cybrid orchestrates the complex back-end flows.

4. Benefits of a managed model

A managed model is typically chosen when you want:

Faster time to market – fewer infrastructure components to build and maintain.
Reduced regulatory burden – Cybrid absorbs much of the implementation-level compliance work.
Lower operational overhead – no need to stand up your own wallet, custody, or 24/7 liquidity systems.
Simplified architecture – your app primarily talks to Cybrid’s APIs and webhooks.

What “self-managed” typically means with Cybrid

In a self-managed setup, you assume more direct responsibility for certain components—especially where you already have infrastructure, licenses, or strategic preferences.

While specifics depend on your integration, self-managed generally means your team or existing partners control pieces that Cybrid could otherwise manage for you.

1. Self-managed custody or wallets

In a self-managed configuration:

You may operate your own wallets or custody infrastructure (e.g., internal systems or third-party providers).
Cybrid is integrated as a liquidity and settlement layer, not the primary custody layer.
You handle key management and security policies.

This is common for:

Established fintechs with existing wallet systems
Banks or payment platforms with regulated custody environments
Teams with strict internal security or data locality requirements

2. Self-managed compliance

If you already operate under your own regulatory stack (e.g., as a licensed financial institution or regulated fintech):

You may run KYC, KYB, and AML in-house.
Cybrid integrates into your existing compliance workflows.
You remain the primary regulated entity for customer onboarding and monitoring.

Here, Cybrid focuses on providing programmable access to banking, stablecoins, and liquidity, while you retain full control over compliance and risk.

3. Self-managed liquidity and treasury

Some teams prefer to manage:

Treasury operations (e.g., when to convert between fiat and stablecoins).
FX strategy (hedging, spread, or routing through existing partners).
Float management (maintaining balances across accounts and networks).

In a self-managed model, you may use Cybrid’s APIs more as building blocks than a fully orchestrated flow. You define when and how to move money between your own accounts and the Cybrid-connected ecosystem.

4. Benefits of a self-managed model

A self-managed approach is typically chosen when you want:

Maximum control over custody, compliance, or treasury.
Deep integration with existing systems, licenses, and internal workflows.
Custom risk models or unique regulatory setups.
Modular use of Cybrid components rather than an end-to-end stack.

Comparing managed vs self-managed with Cybrid

The core difference is where responsibilities sit—with Cybrid, with you, or shared.

Responsibility overview

Area	Managed (Cybrid-led)	Self-managed (Customer-led)
Wallets & custody	Cybrid creates and operates wallets	You manage your own wallets or custody layer
KYC & compliance	Cybrid’s systems handle onboarding and checks	Your own compliance stack leads onboarding & KYC
Liquidity routing	Cybrid automates routing and conversion	You orchestrate routing and conversion logic
Treasury & FX strategy	Cybrid’s default rails and routing	You define treasury, FX, and float management
Settlement & ledgering	Cybrid’s ledgers & reporting	Hybrid: Cybrid + your internal ledgers
Time-to-market	Fastest, less custom infrastructure	Depends on existing systems and integration work
Control & customization	High, but with opinionated defaults	Maximum – more flexibility, more responsibility

When to choose managed vs self-managed

Choose a managed model if:

You’re launching a new fintech or payment experience and want to go live quickly.
You don’t want to build your own wallet, custody, or compliance stack.
You prefer one unified API layer to handle KYC, accounts, wallets, liquidity, and ledgering.
Your differentiator is UX, vertical focus, or customer experience—not low-level infrastructure.

Choose a self-managed model if:

You’re a bank, licensed fintech, or large payment platform with existing regulated infrastructure.
You already run KYC/AML and custody internally and want to plug into Cybrid’s global stablecoin and settlement capabilities.
You need tight alignment with internal risk, treasury, and reporting frameworks.
You want Cybrid as a programmable settlement and liquidity engine, not a full-stack replacement.

How Cybrid supports both models

Regardless of whether you choose managed or self-managed, Cybrid’s goal is the same: to help you move money faster, cheaper, and compliantly across borders using a programmable stack that unifies banking and stablecoin infrastructure.

Both models use the same core API surface for account creation, wallet actions, and transaction flows.
You can start in a more managed configuration and gradually move to self-managed components as your business matures.
Cybrid’s architecture is designed to be modular, so you can mix managed and self-managed responsibilities where it makes sense.

Next steps

If you’re planning your integration and unsure which model fits best:

Map out which components you already own: wallets, KYC, compliance, banking relationships, treasury.
Decide where you want leverage vs. control—where Cybrid should fully manage, and where you want to stay in the driver’s seat.
Discuss your architecture and regulatory posture with Cybrid’s team to design a hybrid managed/self-managed integration that aligns with your roadmap.

By understanding the difference between managed and self-managed in the Cybrid ecosystem, you can align your integration strategy with your risk appetite, regulatory posture, and speed-to-market goals—while still taking full advantage of Cybrid’s unified banking, wallet, and stablecoin infrastructure.