Bytebase Docs home page
Search...
⌘K
Ask AI
GitHub
bytebase.com
bytebase.com
Search...
Navigation
Install
Self-Host vs Cloud
Get Started
Features
Administration
Integrations
Tutorials
API Reference
Changelog
Introduction
Why Bytebase
Supported Databases
Use Cases
Core Concepts
FAQ
Install
Self-Host vs Cloud
Self-Host
Cloud
Connect Your Database
Quick Start
Step 1: Deploy with Docker
Step 2: Register Account
Step 3: Configure Environments
Step 4: Add an Instance
Step 5: Create a Project
Step 6: Change Schema
Step 7: Query Data
Onboarding Guides
Onboarding Plan
POC Checklist
SQL Editor Data Access Control
Organize Projects
On this page
Key Differences
Choose Self-Host For
Choose Cloud For
How to Deploy
Install
Self-Host vs Cloud
Copy page
Choose the right Bytebase deployment for your databases
Copy page
Quick Answer
: Use
Self-Host
for private databases (VPC, on-premises). Use
Cloud
for public cloud databases (Neon, Supabase, RDS with public IP).
Key Differences
Choose Self-Host For
Private databases
without public internet access
VPC environments
(AWS VPC, Google VPC, etc.)
On-premises
corporate databases
Compliance requirements
(data sovereignty, security policies)
Custom configurations
(external PostgreSQL, custom domains)
Choose Cloud For
Cloud databases
with public connectivity:
Neon, Supabase
AWS RDS with public IP
Google CloudSQL with public IP
Azure Database with public access
Quick evaluation
without infrastructure setup
Small teams
wanting zero maintenance
How to Deploy
Self-Host Guide
Deploy with Docker in 5 minutes
Cloud Signup
Start instantly at hub.bytebase.com
Not sure? Start with Cloud for testing, then migrate to Self-Host if you need private database access.
Was this page helpful?
Yes
No
FAQ
Deploy with Docker
Assistant
Responses are generated using AI and may contain mistakes.