> For the complete documentation index, see [llms.txt](https://mariadb.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mariadb.com/docs/mariadb-cloud/quickstart/bring-your-own-account-byoa.md).
# Bring Your Own Account (BYOA)
Bring Your Own Account (BYOA) allows large enterprises to deploy fully managed MariaDB Cloud databases directly within their own public cloud infrastructure. This deployment model offers the operational simplicity of a managed service while satisfying strict requirements for data sovereignty, compliance, and cloud cost optimization.
With BYOA, the Control Plane (UI, API, Monitoring) remains in MariaDB Cloud, while the Data Plane (Compute, Storage, Backups) resides entirely in your cloud account.
```mermaid
flowchart LR
classDef control fill:#e3f2fd,stroke:#1565c0,stroke-width:2px,color:#0d47a1;
classDef data fill:#fff3e0,stroke:#e65100,stroke-width:2px,color:#bf360c;
classDef external fill:#eceff1,stroke:#546e7a,stroke-width:1px,color:#263238;
User([DevOps Team]):::external
App([Application]):::external
subgraph CP ["MariaDB Cloud — Control Plane"]
direction TB
Portal["Portal and API"]:::control
Orch["Orchestrator"]:::control
Bastion["Secure Bastion"]:::control
end
subgraph CU ["Your Cloud Account — Data Plane"]
direction TB
IAM["IAM Role /
Service Account"]:::data
subgraph VPC ["Your Private VPC"]
direction TB
DB[("Database Node")]:::data
Storage[("Storage")]:::data
end
end
User -->|"1 Request"| Portal
Portal -->|"2 Trigger"| Orch
Orch -->|"3 Provision"| IAM
IAM -.->|"creates"| VPC
Orch -.->|"internal"| Bastion
Bastion -->|"4 Manage (TLS)"| DB
App -->|"5 Connect (private)"| DB
DB <--> Storage
```
## How it works
A BYOA environment is a secure, isolated set of resources within your own cloud provider account (Azure, AWS, or Google Cloud) that is managed by MariaDB Cloud.
```mermaid
flowchart LR
classDef step fill:#e3f2fd,stroke:#1565c0,stroke-width:2px,color:#0d47a1;
S1["1. Account Linking
IAM handshake"]:::step
S2["2. Provisioning
Compute, storage, network"]:::step
S3["3. Management
Patching and health"]:::step
S4["4. Connectivity
Private access"]:::step
S1 --> S2 --> S3 --> S4
```
1. Account Linking: You authorize MariaDB Cloud to access your specific cloud subscription via a secure IAM role or Service Principal with least-privilege permissions.
2. Resource Provisioning: When you create a service, MariaDB Cloud orchestrates the deployment of Virtual Machines, Storage, and Networking directly into your account.
3. Management: MariaDB Cloud monitors health, performs backups, and applies patches automatically, just like a standard managed service.
4. Connectivity: Your applications connect to the database locally within your cloud network (VPC/VNet), ensuring low latency and high security without exposing data to the public internet.
### Why use BYOA?
BYOA is designed for enterprise organizations with specific regulatory or infrastructure requirements:
* Compliance & Data Sovereignty: Since data never leaves your cloud account, you maintain absolute control over data residency. This simplifies meeting strict regulatory standards such as HIPAA, PCI-DSS, and GDPR.
* Cloud Cost Optimization: You pay your cloud provider directly for the underlying infrastructure. This allows you to burn down existing committed spend (e.g., Azure MACC, AWS EDP) and leverage your negotiated enterprise discounts.
* Network Security: Database nodes are deployed into a private VPC/VNet. You can enforce your own security group rules, routing policies, and network isolation without complex peering arrangements.
* Advanced Workloads (PowerPlus): Enables the PowerPlus tier, allowing for advanced topologies like Galera Clusters to run in your own environment.
### Who is eligible for BYOA?
BYOA is an enterprise-grade feature with specific commercial and technical prerequisites:
* Service Tier: Your organization must be on the Power or PowerPlus tier.
* Support Plan: You must have Standard Support with the Remote DBA add-on enabled.
* Contract: Available to customers with annual contracts or minimum spend commitments.
{% hint style="info" %}
BYOA is a Tech Preview, currently available on Amazon Web Services and Microsoft Azure. Google Cloud support is coming soon.
{% endhint %}
### BYOA Pricing and Billing
The BYOA setup splits your costs into two separate components. This model ensures transparency and allows you to apply your own cloud credits or reserved instance savings to the infrastructure portion of the cost.
```mermaid
flowchart LR
classDef maria fill:#e8f5e9,stroke:#2e7d32,stroke-width:2px,color:#1b5e20;
classDef cloud fill:#fff8e1,stroke:#f9a825,stroke-width:2px,color:#f57f17;
classDef customer fill:#eceff1,stroke:#546e7a,stroke-width:1px,color:#263238;
Customer(("Your
Organization")):::customer
subgraph B1 ["Invoice 1 — MariaDB Cloud"]
M["Management fee
Support (Remote DBA)
Software licenses"]:::maria
end
subgraph B2 ["Invoice 2 — Your Cloud Provider"]
C["Compute
Storage
Data transfer"]:::cloud
end
Customer -->|"service fees"| M
Customer -->|"infrastructure costs"| C
C -.->|"apply committed spend and discounts"| Customer
```
1. MariaDB Cloud Invoice: You receive a bill from MariaDB for the management fee, software licensing, and support.
2. Cloud Provider Invoice: You receive a bill directly from your cloud provider for the consumed infrastructure resources (Compute, Storage, Network).
### Get Started
For the Tech Preview, onboarding is a guided process.
1. Contact Sales: Submit a request via the MariaDB Cloud Portal or contact your account representative to validate eligibility.
2. Onboarding: Our support team will provide the necessary IAM/Service Principal templates and guide you through the account linking process.
3. Deploy: Once linked, "Bring Your Own Account" will appear as a deployment target in your Create Service wizard.
*This page is: Copyright © 2026 MariaDB. All rights reserved.*