Announcing Bring Your Own Cloud (BYOC) for mobile observability

Today, we are announcing Bring Your Own Cloud (BYOC) for Amazon Web Services (AWS) in bitdrift Capture. With BYOC in bitdrift, you can take advantage of bitdrift's radical new take on observability to get better visibility, squash bugs instantaneously, and build better apps – all while maintaining total control of your log data at rest. At bitdrift, we offer a very different take on observability: on-device intelligence that gives you 1000x the observability at 1% of the cost. Instead of sending loads of expensive telemetry data only to later sift through it for a few precious insights, we couple a sophisticated device SDK, local storage, and real-time control via our control plane SaaS, in order to dynamically fetch only the data needed to understand customer behavior and solve problems quickly. . bitdrift’s architecture means that we are uniquely positioned to grow with you to unlimited scale: from startup all the way to the Fortune 50.

Deployment options for everyone

With the addition of BYOC, we now have three different deployment options that bitdrift Capture customers can choose from:

1. Our turnkey SaaS: sign up, get an API key, and go. This is the most frictionless option. It’s no security slouch either. The SaaS is SOC 2 Type II certified!
2. Bring your own bucket (BYOB): We announced this option last year. BYOB is a low-cost, low-friction option that keeps the most critical data (session logs and crash reports) entirely owned by the customer, without adding operational overhead.
3. BYOC: When you bring your own cloud to bitdrift, you have the opportunity to own all resources and can also own the security posture and policies on top of those resources. bitdrift then operates the deployment effectively as a private SaaS. Though the highest in cost and friction of the three options, for the most demanding enterprise customers this option also provides the highest level of security and compliance control.

How BYOC works

From the customer perspective, setting up BYOC is straightforward:

1. Provision an empty AWS sub-account and provide temporary admin access to bitdrift.
2. bitdrift will provision bootstrap provisioning IAM roles. Admin permissions can then be removed.
3. Next, bitdrift will provision the rest of the Capture stack with tightly scoped IAM permissions on each role.
4. bitdrift will then operate Capture on the customer’s behalf. The only data that leaves the account is operational telemetry that bitdrift uses for monitoring and alerting.
5. You, the customer, can provision and enforce any security controls and policies you desire within the account.

Enterprise customers can now enjoy a private SaaS where all data and infrastructure are under your complete control!

BYOC completes the AI observability stack

By allowing on-cloud direct access to your mobile telemetry via API, BYOC for bitdrift supports AI workflows without the data export tax. Gain AI insights, build training models, and enable future facing tool/skill/mcp development -- all without the egress costs associated with traditional SaaS observability platforms. Got OpenTelemetry? The bitdrift BYOC mobile observability platform can correlate front-to-back with OpenTelemetry traceIDs and correlate with your BYOC APM solution as well!

Join us for the future of observability

BYOC is available today for all enterprise customers. New and existing customers can contact us to learn more. Capture is changing the mobile observability game by adding a control plane and local storage on every mobile device, providing extremely detailed telemetry when you need it, and none when you don’t. If lack of strict data ownership was keeping you away, now is the time to give us a try! Interested in learning more? Here are some options:

• Get in touch for a demo.
• Check out the sandbox or start a free trial to dive right into the product and see what working with Capture is like.
• Join us in Slack to ask questions and share feedback.

We can’t wait to see what you think.

Frequently asked questions

What does BYOC mean?

BYOC stands for Bring Your Own Cloud. In a BYOC deployment model, the customer provides their own cloud account (for example, an AWS sub-account), and the vendor deploys and operates the application inside that environment. Unlike traditional SaaS, the infrastructure and data reside entirely within the customer’s cloud perimeter.

How is BYOC different from traditional SaaS?

In traditional SaaS:

• The vendor owns the infrastructure
• Your telemetry data is stored in the vendor’s cloud account
• You rely on contractual and certification guarantees

In BYOC:

• You own the cloud account You control IAM, networking, security posture, and policies
• Your telemetry never leaves your environment (except limited operational telemetry for monitoring)

You get SaaS-like operations with enterprise-grade control.

What is the difference between BYOC and BYOB?

BYOB (Bring Your Own Bucket) allows customers to store specific high-value artifacts like session logs and crash reports in their own storage bucket. BYOC (Bring Your Own Cloud) goes further:

• The entire Capture stack runs inside your AWS account
• All infrastructure and data are owned by you
• You define and enforce the security model

BYOC is designed for highly regulated or security-conscious enterprises.

Why would an enterprise choose BYOC for mobile observability?

Common reasons include:

• Strict data residency requirements
• Security teams that prohibit third-party SaaS data storage
• Compliance frameworks that require infrastructure ownership
• Desire to eliminate vendor lock-in risk
• Avoiding large telemetry egress costs

BYOC enables these organizations to adopt modern mobile-first observability without compromising policy.

Does BYOC reduce telemetry egress costs?

Yes. Because the data is stored and accessed within your own AWS environment:

• You avoid SaaS egress fees
• You avoid duplicative data export pipelines
• You can connect directly to internal analytics, AI, and data systems

This is particularly valuable when using mobile telemetry to train AI models or power internal dashboards.

How does BYOC work with OpenTelemetry?

bitdrift supports correlation with OpenTelemetry trace IDs. In a BYOC deployment:

• Mobile session telemetry lives in your AWS account
• Backend traces collected via OpenTelemetry can also live in your cloud
• Trace IDs allow front-to-back correlation without exporting data externally

This enables unified distributed tracing while maintaining full data control.

What is the bitdrift control plane?

The bitdrift control plane is the SaaS service that remotely configures device behavior. It allows teams to:

• Dynamically adjust logging
• Fetch specific telemetry on demand
• Enable targeted debugging workflows
• Change observability logic without redeploying the app

The control plane sends instructions to devices. The device stores telemetry locally and emits only what is needed — eliminating the “ingest everything” model.

Is BYOC compliant with SOC 2 and enterprise security standards?

bitdrift’s SaaS is SOC 2 Type II certified. In a BYOC deployment:

• Infrastructure resides in your AWS account
• You control encryption, IAM, VPC boundaries, and monitoring
• You can apply your internal compliance policies directly

BYOC enhances security posture by aligning observability infrastructure with your existing governance model.

Can I start with SaaS and move to BYOC later?

Yes. Many customers:

1. Start with SaaS for fast evaluation.
2. Move to BYOB for selective data ownership.
3. Graduate to BYOC as enterprise requirements evolve.

The architecture supports all three deployment models.