Obsfly
byoc · control-plane / data-plane splitlivecustomer VPC · data planeagentreceiverconsumerClickHousedata-plane proxymTLSobsfly cloud · control planefrontendbackend (API)detector (AI)license-server

BYOC

为何受监管 SaaS 用不了 Datadog DBM — 以及 BYOC 解决方案

BYOC 可观测性部署架构:数据在哪里、什么会跨越边界,以及如何在不牺牲 UX 的前提下满足 SOC2 / HIPAA / GDPR。

Published ·Updated ·14 min read

If you’ve tried to put Datadog DBM in front of a regulated SaaS’s security team, you know. Query text is the most sensitive blob in a database — emails, tokens, account numbers, full-text search inputs. SaaS-only DBM means that blob crosses your boundary, hits a multi-tenant ingestion pipeline, and lives in a vendor’s storage. That’s a SOC2 / HIPAA / GDPR landmine.

What BYOC fixes

BYOC (Bring Your Own Cloud) splits a SaaS product cleanly into a data plane (the parts that touch raw telemetry) and a control plane (the UI, identity, billing, AI engine). The data plane runs in your VPC. The control plane runs in ours, and reaches the data plane through one narrow, audited gRPC endpoint.

What crosses the boundary

In a properly designed BYOC deployment: aggregated query results (counts, percentiles, plan blob IDs), anomaly verdicts, alert webhooks. Not: raw query text, plan content, row data, tags that could re-identify users.

How to evaluate a BYOC vendor

  • Ask for the data-plane proxy source (or its protobuf). If they can’t show it, it’s not real BYOC.
  • Ask whether your security team can audit every call the control plane sends.
  • Ask what happens when you turn the proxy off. (Should: graceful read-only.)
  • Ask for the Helm chart. If they ship a custom installer, it’s not portable.
  • Ask what happens at contract end. (Should: hard stop after a 7-day grace, but your data is never deleted by them.)

Obsfly’s answer

Same Go binaries run in SaaS, BYOC, and Sovereign mode — no fork. The data-plane proxy ships with its protobuf in packages/proto/dataplane.proto and a Helm chart in infra/helm/obsfly-data-plane/. Audit logging is a one-line setting.

Full architecture page: /byoc. Sovereign / on-prem option for fully air-gapped: /sovereign.

The license-controller catch

BYOC vendors typically pair their deployment story with a license-control mechanism — annual signed license, daily heartbeat, lifecycle that gracefully degrades after expiry. Obsfly is open about this. The exact heartbeat shape and lifecycle are documented on /sovereign. No query text, no row data, no schemas — only deployment health and DB count.

Is BYOC harder to install than SaaS?+
Yes — typically a 1–2 day spin-up for someone familiar with Helm/Terraform. SaaS is 5 minutes. The trade is what your security team requires.
Does BYOC cost more?+
Up-front yes (typically a $3–10k/mo platform fee on top of per-DB). On TCO, often less than SaaS at scale because you absorb storage cost in your existing cloud spend.
Can I migrate from SaaS to BYOC later?+
Yes. The agent stays the same; only the receiver URL changes. Historical data does not transfer (it lives in our cloud); we keep both data planes running for 30 days during a cutover.

Keep reading

· · ·

像监控服务一样监控你的数据库。

预约 30 分钟演示。我们一起规划你的数据库规模,并报出第一个 30 天合作的报价。

为何受监管 SaaS 用不了 Datadog DBM — 以及 BYOC 解决方案 · Obsfly