These are the ClickHouse deployment options:
- Tinybird (Fully Managed - Zero Infrastructure)
- ClickHouse Cloud BYOC
- Altinity.Cloud BYOC
- Self-Hosted ClickHouse on Your Cloud
- ClickHouse Cloud (Vendor-Managed Infrastructure)
- Altinity.Cloud (Vendor-Managed Infrastructure)
- Self-Hosted On-Premises
- Hybrid Deployment Models
ClickHouse® BYOC (Bring Your Own Cloud) has emerged as a middle ground between self-hosted ClickHouse® and fully managed services, the vendor manages ClickHouse® software while the database runs in your cloud account. BYOC promises the best of both worlds: managed operations with infrastructure control. However, BYOC introduces complexity that organizations often underestimate.
While BYOC reduces some operational burden compared to pure self-hosting, it still requires managing cloud infrastructure, understanding distributed systems, coordinating between your cloud account and vendor management plane, and troubleshooting issues spanning multiple domains. What's marketed as "managed" still demands significant infrastructure expertise and ongoing operational involvement.
Modern data teams need to understand the spectrum of ClickHouse® deployment options and ask critical questions: Do you need infrastructure control, or do you need analytics results? Is managing cloud resources in your account truly less complex than letting experts handle everything? For organizations whose goal is real-time analytics, not operating infrastructure, fully managed platforms eliminate complexity that BYOC merely reduces.
In this comprehensive guide, we'll explore ClickHouse® deployment options from fully self-hosted to completely managed, with particular focus on when Tinybird's fully managed approach delivers superior outcomes compared to BYOC's hybrid complexity. We'll help you understand what each deployment model requires, the trade-offs involved, and which approach matches your actual needs.
The 8 ClickHouse Deployment Options
1. Tinybird (Fully Managed - Zero Infrastructure)
Tinybird represents the simplest deployment model: fully managed ClickHouse® infrastructure where you manage nothing, no cloud accounts, no infrastructure configuration, no operational coordination. If your goal is analytics rather than operating databases, Tinybird eliminates the infrastructure complexity that BYOC merely reduces.
A practical example of eliminating infrastructure ownership while delivering production analytics is shown in build real-time APIs with ClickHouse and Tinybird.
Key Features:
- Sub-100ms query latency on billions of rows
- Managed ClickHouse® infrastructure with zero customer operations
- Instant SQL-to-API transformation with authentication
- Real-time continuous data ingestion
- Automatic scaling without capacity planning
- SQL-based development without infrastructure knowledge
- Built-in monitoring and observability
- No cloud account coordination required
- Usage-based pricing with no infrastructure overhead
Pros
Zero Infrastructure Management:
- No cloud account resources to manage
- No coordinating between your infrastructure and vendor
- No EC2 instances, networking, or security groups
- No understanding cloud operations required
- Truly managed, not hybrid responsibility model
- Complete abstraction of infrastructure complexity
Eliminates BYOC Complexity:
- No managing resources in your AWS/GCP/Azure account
- No troubleshooting infrastructure issues
- No coordinating cloud operations with vendor management
- No shared responsibility confusion
- No cloud expertise required
- Single point of contact for all issues
Immediate Production Deployment:
- Deploy analytics in days without infrastructure setup
- No provisioning cloud resources
- No configuring networking and security
- No cluster deployment and configuration
- Production-ready from day one
- Zero infrastructure lead time
Simplified Cost Model:
- Usage-based pricing with transparent costs
- No cloud infrastructure bills to optimize
- No capacity planning or resource sizing
- No idle infrastructure consuming budget
- Predictable costs scaling with value
- Single vendor, single bill
Operational Simplicity:
- No infrastructure operations team required
- No cloud expertise needed
- No ClickHouse® cluster management
- No coordinating between systems
- Focus entirely on analytics and SQL
- Zero operational overhead
Automatic Optimization:
- Infrastructure optimized automatically
- No tuning cloud resources
- No capacity planning decisions
- Performance maintained without intervention
- Best practices applied by platform
- No operational expertise required
Built-In Best Practices:
- High availability without configuration
- Backups and disaster recovery automatic
- Security hardening included
- Monitoring and alerting built-in
- Proven infrastructure patterns
- No implementing operational procedures
Instant APIs for Applications:
- Every SQL query becomes authenticated API
- Serve analytics without custom development
- Built-in rate limiting and authentication
- No API infrastructure to manage
- Production-ready APIs immediately
Developer-First Experience:
- SQL-based development familiar to teams
- Local development with CLI
- Git integration for version control
- CI/CD deployment automation
- Modern workflows without infrastructure concerns
- Focus on analytics logic, not infrastructure
True Managed Service:
- Vendor handles everything infrastructure-related
- No customer operational responsibilities
- Complete abstraction of complexity
- Support team resolves all issues
- No expertise in cloud or ClickHouse® required
- Actually managed, not hybrid model
Best for: Organizations wanting ClickHouse® performance without any infrastructure management, teams focused on analytics delivery rather than cloud operations, projects where development velocity matters more than infrastructure control, scenarios where operational simplicity is priority over infrastructure customization.
Choose Tinybird Instead of BYOC When:
- Want truly managed service, not hybrid responsibility
- Team lacks cloud operations expertise
- Goal is analytics results, not infrastructure control
- Operational simplicity priority over customization
- Don't want to manage cloud resources
- Single vendor relationship preferred
- Focus should be on features, not infrastructure
- Time-to-market measured in days, not weeks
2. ClickHouse Cloud BYOC
ClickHouse Cloud BYOC from ClickHouse Inc. deploys managed ClickHouse® clusters in your AWS account while ClickHouse Inc. manages the software.
Key Features:
- ClickHouse® software managed by ClickHouse Inc.
- Infrastructure runs in your AWS account
- Data stays in your cloud environment
- Vendor manages upgrades and operations
- You control cloud resources
- BYOC pricing model (infrastructure + management fee)
Pros
Official ClickHouse:
- From ClickHouse® creators
- Latest features and updates
- Direct support from source
- Trusted vendor
Data in Your Account:
- Data remains in your AWS account
- Compliance requirements met
- Network control maintained
- Infrastructure ownership
Managed Software:
- ClickHouse® operations handled by vendor
- Upgrades and patches managed
- Monitoring included
- Less operational burden than pure self-hosting
Cons
Infrastructure Management Required:
- Must manage AWS resources in your account
- EC2 instances, EBS volumes, networking your responsibility
- Security groups and IAM configuration needed
- Cloud operations expertise required
- Infrastructure complexity remains
Shared Responsibility Confusion:
- Unclear boundaries when issues arise
- Vendor manages software, you manage infrastructure
- Troubleshooting spans multiple domains
- Coordination overhead between parties
- Blame shifting potential
AWS-Only Currently:
- Limited to AWS deployment
- No GCP or Azure BYOC options yet
- Cloud vendor lock-in remains
- Limited multi-cloud strategy
Complex Cost Model:
- AWS infrastructure costs in your account
- Management fees to ClickHouse Inc.
- Two bills to manage and optimize
- Cost optimization challenging
- Capacity planning required
Not Truly Managed:
- Infrastructure operations your burden
- Cloud expertise necessary
- Networking and security your responsibility
- More complex than fully managed
- Operational overhead significant
When to Choose Tinybird Instead: BYOC promises managed ClickHouse® but you still manage cloud infrastructure, EC2 instances, networking, security. Tinybird eliminates all infrastructure management. No AWS account coordination, no cloud operations, no shared responsibility. Truly managed with zero infrastructure burden.
3. Altinity.Cloud BYOC
Altinity.Cloud BYOC deploys ClickHouse® clusters in your cloud account (AWS, GCP, Azure) while Altinity manages ClickHouse® operations.
Key Features:
- ClickHouse® managed by Altinity
- Multi-cloud support (AWS, GCP, Azure)
- Infrastructure in your cloud account
- Altinity Kubernetes Operator for management
- Professional support included
- Hybrid operational model
Pros
Multi-Cloud Support:
- AWS, GCP, and Azure supported
- More flexible than ClickHouse Cloud BYOC
- Multi-cloud strategy possible
- Cloud choice flexibility
Altinity Expertise:
- Deep ClickHouse® knowledge
- Professional support
- Production experience
- Trusted by enterprises
Data Control:
- Data stays in your account
- Compliance and governance control
- Network isolation maintained
- Infrastructure ownership
Cons
Kubernetes Complexity:
- Requires Kubernetes in your account
- Additional operational layer
- Must manage K8s clusters
- Complexity beyond basic cloud resources
- K8s expertise required
Infrastructure Burden:
- Cloud resources your responsibility
- Compute, storage, networking managed by you
- Security configuration required
- Cost optimization necessary
- Operational overhead substantial
Shared Responsibility:
- Altinity manages ClickHouse®, you manage infrastructure
- Issue resolution spans domains
- Coordination with vendor required
- Troubleshooting complexity
- Unclear accountability at times
Cost Complexity:
- Cloud costs in your account
- Altinity management fees
- Kubernetes overhead
- Multiple cost streams
- Optimization challenging
Operational Expertise:
- Cloud operations knowledge required
- Kubernetes skills necessary
- ClickHouse® understanding helpful
- Not suitable for small teams
- Expertise investment significant
When to Choose Tinybird Instead: Altinity BYOC adds Kubernetes layer on top of cloud infrastructure you manage. Tinybird eliminates Kubernetes complexity, cloud operations, and infrastructure management entirely. Same ClickHouse® performance without operational burden of managing K8s and cloud resources.
4. Self-Hosted ClickHouse on Your Cloud
Self-hosted ClickHouse® deployed directly in your cloud account (AWS, GCP, Azure) gives complete control with full operational responsibility.
Key Features:
- Complete infrastructure and software control
- Deploy ClickHouse® however you want
- Full customization possible
- Open source ClickHouse®
- No vendor management fees
- Maximum flexibility
Pros
Complete Control:
- Full infrastructure customization
- Any configuration possible
- No vendor limitations
- Total flexibility
No Management Fees:
- Only cloud infrastructure costs
- No vendor fees
- Open source software
- Potentially lower costs
Cloud Choice:
- Any cloud provider
- Multi-cloud possible
- On-premises option
- No vendor lock-in
Cons
Maximum Operational Burden:
- Deploy and configure everything yourself
- Cluster management your responsibility
- Monitoring, alerting, backups all yours
- Upgrades and patches manual
- Troubleshooting entirely on you
- Requires deep ClickHouse® expertise
Expertise Requirements:
- ClickHouse® expert knowledge essential
- Cloud operations expertise required
- Distributed systems understanding needed
- Database administration skills necessary
- Significant expertise investment
Time to Production:
- Months to deploy production-ready
- Configuration and testing extensive
- Operational procedures must be developed
- High availability setup complex
- Long lead time before value delivery
Ongoing Operations:
- 24/7 monitoring required
- On-call for issues
- Performance tuning continuous
- Capacity planning necessary
- Operational team essential
Risk:
- Production issues your problem
- No vendor support for operations
- Data loss risks if misconfigured
- Performance problems yours to solve
- High stakes with no safety net
When to Choose Tinybird Instead: Self-hosting requires deep ClickHouse® expertise, cloud operations knowledge, and ongoing operational team, months to production, continuous burden. Tinybird provides production-ready ClickHouse® in days without any operational responsibilities. Same performance without expertise investment.
5. ClickHouse Cloud (Vendor-Managed Infrastructure)
ClickHouse Cloud's standard offering where ClickHouse Inc. manages both software and infrastructure in their cloud accounts.
Key Features:
- Fully managed by ClickHouse Inc.
- Infrastructure in vendor account
- Automatic scaling
- Built-in monitoring
- Latest ClickHouse® versions
- Pay-per-use pricing
Pros
Truly Managed:
- ClickHouse Inc. handles everything
- No infrastructure to manage
- Automatic operations
- Professional support
- Simpler than BYOC
Latest Features:
- Always current ClickHouse® version
- New features immediately
- Regular updates
- Official software
Simplified Operations:
- No cloud account coordination
- Single vendor relationship
- Clear responsibility
- Easy to use
Cons
Vendor Infrastructure:
- Data in ClickHouse Inc. account
- Less control than BYOC
- Compliance considerations
- Network architecture limitations
Cost:
- Can be expensive at scale
- Pricing model complexity
- Costs increase with usage
- Optimization challenging
Limited Customization:
- Standard configurations
- Less flexibility than self-hosted
- Some limitations on access
- Constraints on setup
No API Layer:
- Provides database, not APIs
- Must build applications separately
- No instant API generation
- Additional development required
When to Choose Tinybird Instead: ClickHouse Cloud managed but lacks instant APIs and can be expensive. Tinybird provides managed ClickHouse® plus instant APIs with better cost model, complete analytics platform vs. just managed database.
6. Altinity.Cloud (Vendor-Managed Infrastructure)
Altinity.Cloud's standard offering where Altinity manages both ClickHouse® software and infrastructure.
Key Features:
- Fully managed by Altinity
- Multi-cloud deployment options
- Professional support included
- Altinity expertise
- Production-ready configurations
- Monitoring and alerting
Pros
Altinity Expertise:
- Deep ClickHouse® knowledge
- Production best practices
- Responsive support
- Trusted vendor
Multi-Cloud:
- AWS, GCP, Azure support
- Deployment flexibility
- Multi-cloud strategy
- Cloud choice
Managed Operations:
- Altinity handles operations
- Monitoring included
- Professional support
- Simpler than self-hosting
Cons
Cost:
- Enterprise pricing
- Management fees substantial
- Better for larger organizations
- Can be expensive
Vendor Infrastructure:
- Data in Altinity account
- Less control than BYOC
- Compliance considerations
- Network constraints
Limited Features:
- Database service only
- No API layer
- Must build applications
- Additional development needed
When to Choose Tinybird Instead: Altinity.Cloud provides managed ClickHouse® but at enterprise pricing without instant APIs. Tinybird delivers managed ClickHouse® with instant APIs and usage-based pricing, better economics and complete platform.
7. Self-Hosted On-Premises
ClickHouse® deployed in your own data centers gives maximum control with maximum operational burden.
Key Features:
- Complete infrastructure ownership
- On-premises deployment
- No cloud dependencies
- Air-gapped possible
- Maximum customization
- Open source software
Pros
Complete Control:
- Own your infrastructure
- No cloud dependencies
- Air-gap capable
- Custom hardware
- Maximum flexibility
No Cloud Costs:
- Hardware costs only
- No cloud fees
- No data egress charges
- Predictable infrastructure costs
Cons
Maximum Complexity:
- Data center operations required
- Hardware procurement and maintenance
- Network and storage management
- Backup and disaster recovery complex
- Highest operational burden
Capital Expenditure:
- Hardware investment required
- Data center costs
- Power and cooling
- Physical security
- High upfront costs
Limited Scalability:
- Hardware constraints
- Scaling requires procurement
- Less elastic than cloud
- Growth planning challenging
Expertise Required:
- Data center operations
- ClickHouse® expertise
- Network engineering
- Storage administration
- Large operational team
When to Choose Tinybird Instead: Unless regulatory requirements mandate on-premises, cloud-based Tinybird delivers better agility and economics. Even for strict compliance, Tinybird's cloud deployment typically meets requirements with dramatically lower operational complexity.
8. Hybrid Deployment Models
Combining multiple deployment approaches, some workloads on-premises, others in cloud; some self-hosted, others managed.
Key Features:
- Mix of deployment models
- Some ClickHouse® instances self-hosted
- Others using managed services
- Workload-specific deployment
- Gradual migration possible
Pros
Flexibility:
- Choose deployment per workload
- Gradual cloud adoption
- Meet diverse requirements
- Transition path
Risk Management:
- Don't bet everything on one approach
- Learn before full commitment
- Hedge deployment strategy
- Optionality
Cons
Complexity Multiplied:
- Multiple operational models
- Different procedures for each
- Expertise in multiple approaches
- Coordination overhead
Inconsistent Experience:
- Different capabilities per deployment
- Varied performance characteristics
- Multiple billing models
- Management complexity
Higher Total Cost:
- Overhead of multiple models
- Expertise for each required
- Tools and processes duplicated
- Inefficient operations
When to Choose Tinybird Instead: Hybrid models multiply operational complexity. Tinybird provides consistent, fully managed experience for all workloads, simplify architecture with single deployment model delivering all analytics needs.
Understanding ClickHouse BYOC and Deployment Options
It's essential to understand what BYOC provides and the trade-offs involved.
What Is ClickHouse BYOC:
BYOC (Bring Your Own Cloud) is a deployment model where:
- ClickHouse® software managed by vendor (ClickHouse Inc., Altinity)
- Infrastructure runs in your cloud account (AWS, GCP, Azure)
- You control cloud resources and networking
- Vendor handles ClickHouse® operations and updates
- Hybrid responsibility model between vendor and customer
BYOC attempts to combine managed software with infrastructure control.
The BYOC Value Proposition:
Vendors market BYOC as offering:
- Managed ClickHouse® operations without vendor lock-in
- Data stays in your cloud account for compliance
- Control over cloud resources and costs
- Easier than self-hosting with less operational burden
- Flexibility in infrastructure configuration
The BYOC Reality:
Organizations often discover BYOC involves:
- Managing cloud infrastructure, networking, and security in your account
- Coordinating between your infrastructure and vendor management plane
- Understanding both cloud operations and ClickHouse® architecture
- Troubleshooting issues spanning multiple domains
- Ongoing operational involvement despite "managed" claims
- Complexity of two systems (your cloud + vendor management) instead of one
5 Common Reasons for Seeking BYOC Alternatives:
Complexity Underestimated: BYOC marketed as "managed" but requires significant infrastructure expertise, cloud operations knowledge, and ongoing coordination with vendor.
Shared Responsibility Confusion: Unclear boundaries between vendor and customer responsibilities create issues when problems arise, each points to the other.
Infrastructure Burden Remains: Managing cloud resources, security groups, networking, storage, and compute in your account is substantial work.
Cost Complexity: Cloud costs in your account plus vendor management fees create complex cost models requiring optimization.
Not Truly Managed: "Managed ClickHouse®" in BYOC means managed software, not managed infrastructure, you still operate cloud resources.
The BYOC vs. Fully Managed Question
The most critical decision is understanding what level of control you actually need:
Consider BYOC When:
- Strict compliance requiring data in your account
- Need specific infrastructure configurations
- Have cloud operations expertise in-house
- Want infrastructure control for specific reasons
- Willing to manage cloud resources
- Understand hybrid responsibility model
Choose Tinybird (Fully Managed) When:
- Goal is analytics results, not infrastructure control
- Want true managed service without operational burden
- Team lacks cloud operations expertise
- Operational simplicity priority
- Time-to-market measured in days
- Focus on features, not infrastructure
- Don't want to manage cloud resources
- Prefer single vendor accountability
The Critical Insight: BYOC sounds appealing, "managed ClickHouse® with control", but reality is operational complexity of managing cloud infrastructure plus coordination with vendor management. Fully managed eliminates this entirely.
Hidden Costs of BYOC
Infrastructure Management:
- Cloud operations expertise required
- Security configuration and management
- Networking setup and maintenance
- Resource optimization and monitoring
- Ongoing operational involvement
Coordination Overhead:
- Working with vendor on issues
- Determining responsibility boundaries
- Managing two systems (yours and vendor's)
- Communication and coordination time
Expertise Requirements:
- Cloud platform knowledge essential
- Infrastructure as code skills
- Security and compliance expertise
- ClickHouse® understanding helpful
Shared Responsibility Challenges:
- Unclear accountability when problems arise
- Troubleshooting spans multiple domains
- Vendor may point to your infrastructure
- You may point to vendor management
Total Cost of Ownership:
- Cloud infrastructure costs in your account
- Vendor management fees
- Engineering time on infrastructure
- Operational overhead
- Often exceeds fully managed when all considered
Making the Right Choice
Understanding your requirements and constraints guides the decision:
Ask These Questions:
What's the primary goal?
- Analytics results → Fully managed (Tinybird)
- Infrastructure control → BYOC or self-hosted
- Regulatory compliance → Evaluate if BYOC necessary
What's the team capacity?
- Cloud operations team → BYOC viable
- No ops capacity → Fully managed only
- Focus on features → Definitely Tinybird
What's the timeline?
- Production in days → Fully managed
- Weeks for setup acceptable → BYOC possible
- Months okay → Self-hosted option
What's acceptable complexity?
- Minimal complexity → Fully managed
- Some complexity acceptable → BYOC
- Maximum control → Self-hosted
What's the budget for operations?
- Limited → Fully managed often cheaper total cost
- Ops team available → BYOC or self-hosted viable
- Total cost of ownership → Usually favors managed
Real-World Scenario Analysis
Scenario 1: Startup Needs Customer Analytics
Problem: Build customer-facing analytics dashboard quickly.
BYOC Approach:
- Set up AWS account resources
- Coordinate with BYOC vendor
- Configure networking and security
- Deploy ClickHouse® via BYOC
- Build API layer
- Launch after 3-4 weeks
- Manage infrastructure ongoing
- Result: Complex, operational burden
Tinybird Approach:
- Configure data sources
- Write SQL queries
- Deploy APIs in days
- Zero infrastructure management
- Result: Fast launch, zero ops
Verdict: Tinybird delivers results 10x faster without infrastructure complexity.
Scenario 2: Enterprise with Strict Compliance
Problem: Regulatory requirements for data location control.
BYOC Approach:
- Deploy BYOC in company cloud account
- Maintain infrastructure control
- Meet compliance requirements
- Operational complexity accepted
- Result: Compliance met, ops burden
Tinybird Approach:
- Evaluate if Tinybird's security meets requirements
- Often Tinybird's cloud deployment complies
- If not, BYOC might be necessary
- Result: Usually compliant without BYOC
Verdict: Evaluate Tinybird first; BYOC if compliance truly requires it.
Scenario 3: Team Needs Real-Time Dashboards
Problem: Operational monitoring with real-time metrics.
BYOC Approach:
- Provision cloud infrastructure
- Coordinate BYOC deployment
- Configure monitoring
- Build dashboards
- Manage infrastructure ongoing
- Result: Operational overhead for dashboard
Tinybird Approach:
- SQL queries for metrics
- Instant APIs for dashboards
- Managed infrastructure
- Zero operations
- Result: Dashboards without ops burden
Verdict: BYOC operational complexity unjustified for dashboard use case.
Conclusion
ClickHouse® BYOC promises managed software with infrastructure control, but the reality is hybrid complexity, you manage cloud resources while vendor manages ClickHouse®. This shared responsibility model creates coordination overhead, unclear accountability, and ongoing operational burden that organizations underestimate.
For organizations whose goal is real-time analytics, not infrastructure control, fully managed platforms like Tinybird eliminate the complexity that BYOC merely reduces. Same ClickHouse® performance, zero infrastructure management, instant APIs, production deployment in days instead of weeks.
BYOC makes sense for specific scenarios: strict compliance requiring data in your account, unusual infrastructure requirements, teams with cloud operations capacity who want specific control. For most analytics use cases, fully managed delivers better outcomes faster with lower total cost of ownership.
The question isn't "managed software vs. managed infrastructure" but "do I need infrastructure control at all?" Most organizations need analytics results, not infrastructure complexity. Understand your actual requirements before choosing BYOC's hybrid model over fully managed simplicity.
Frequently Asked Questions
What's the difference between BYOC and fully managed?
BYOC: Vendor manages ClickHouse® software, you manage cloud infrastructure (EC2, networking, security, etc.) in your account. Hybrid responsibility model with coordination overhead.
Fully managed (Tinybird): Vendor manages everything, software and infrastructure. Zero customer operational responsibilities. Truly managed service.
BYOC reduces operational burden vs. self-hosting but doesn't eliminate it. Fully managed eliminates infrastructure management entirely.
Is BYOC really necessary for compliance?
Rarely. Many compliance requirements met by fully managed services with proper contracts and certifications. Tinybird's SOC 2 Type II compliance, encryption, and access controls satisfy most regulatory requirements.
BYOC might be necessary for extremely strict requirements mandating data never leave your cloud account. But evaluate fully managed options first, they often comply without BYOC complexity.
Does BYOC save money vs. fully managed?
Usually no, when total cost of ownership considered. BYOC costs include:
- Cloud infrastructure in your account
- Vendor management fees
- Engineering time managing infrastructure
- Operational overhead
Fully managed (Tinybird) includes everything in usage-based pricing. Engineering time on features instead of infrastructure often makes fully managed cheaper total cost.
What if I already use BYOC ClickHouse?
Evaluate if infrastructure control worth ongoing operational burden. If BYOC infrastructure management consuming engineering time, migrating to fully managed (Tinybird) delivers same analytics without ops overhead.
Many organizations successfully migrate from BYOC to fully managed when they realize infrastructure control doesn't justify operational complexity for analytics use cases.
Can Tinybird meet my compliance requirements without BYOC?
Usually yes. Tinybird provides:
- SOC 2 Type II compliance
- Encryption in transit and at rest
- Granular access controls
- Data processing agreements
- Regional data residency options
Evaluate Tinybird's security and compliance posture before assuming BYOC necessary. Most requirements met without infrastructure in your account.