Skip to content

docs: add BYOC cloud page#526

Open
romange wants to merge 1 commit into
mainfrom
docs/add-byoc-page
Open

docs: add BYOC cloud page#526
romange wants to merge 1 commit into
mainfrom
docs/add-byoc-page

Conversation

@romange
Copy link
Copy Markdown
Contributor

@romange romange commented May 6, 2026

Summary

  • add a dedicated Dragonfly Cloud BYOC page under cloud/byoc
  • move BYOC information out of the old enterprise page and remove that page
  • link the new BYOC page from the main Dragonfly Cloud overview

Verification

  • verified the page in the local browser at /docs/cloud/byoc
  • verified /docs/cloud/enterprise returns Page Not Found
  • full production build was not run in this environment because the workspace is using Node.js 18 while the docs project requires Node.js >=20

@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview, Comment May 6, 2026 0:43am

Request Review

Copy link
Copy Markdown
Contributor

@ashotland ashotland left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see some optional comments

Comment thread docs/cloud/byoc/byoc.md

The Dragonfly Cloud control plane runs in the Dragonfly Cloud account, while the data plane runs in your cloud account.

If you are interested in Dragonfly Cloud BYOC, please [contact us](https://www.dragonflydb.io/enterprise) to start a proof-of-concept.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought enterprise is on prem - and byoc is business https://www.dragonflydb.io/pricing

Comment thread docs/cloud/byoc/byoc.md

- Dragonfly Cloud assumes this role only when it needs to provision or manage BYOC resources.
- The role follows the **principle of least privilege**.
- Access is limited to resources tagged as `managed-by: dragonfly-cloud`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think gcp support this

Comment thread docs/cloud/byoc/byoc.md
- Dragonfly Cloud assumes this role only when it needs to provision or manage BYOC resources.
- The role follows the **principle of least privilege**.
- Access is limited to resources tagged as `managed-by: dragonfly-cloud`.
- Role assumption is protected with a **shared secret**, so only your Dragonfly Cloud BYOC account can use it.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is AWS only feature

Comment thread docs/cloud/byoc/byoc.md
- AWS CloudFormation: [customer_role.yaml](https://prodv2-control-plane-byoc-public.s3.us-east-1.amazonaws.com/customer_role.yaml)
- GCP Terraform: [main.tf](https://prodv2-control-plane-byoc-public.s3.us-east-1.amazonaws.com/main.tf)

For stronger isolation, Dragonfly recommends using a **dedicated cloud account or project** for BYOC workloads.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

stronger -> strict ?

Comment thread docs/cloud/byoc/byoc.md

## Why Choose BYOC

BYOC is a strong fit when you need one or more of the following:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BYOC is a suitable when any of the following requirements hold:

Comment thread docs/cloud/byoc/byoc.md
BYOC is a strong fit when you need one or more of the following:

- **Data residency or compliance controls** that require workloads to stay inside your cloud account
- **Private networking requirements** with no inbound public access for management
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cloud also has this right ?

Comment thread docs/cloud/byoc/byoc.md

- **Data residency or compliance controls** that require workloads to stay inside your cloud account
- **Private networking requirements** with no inbound public access for management
- **Operational offload** without giving up ownership of infrastructure placement
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Managed service experience

Comment thread docs/cloud/byoc/byoc.md

The Dragonfly Cloud control plane runs in the Dragonfly Cloud account, while the data plane runs in your cloud account.

If you are interested in Dragonfly Cloud BYOC, please [contact us](https://www.dragonflydb.io/enterprise) to start a proof-of-concept.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants