Managed Bytebase Hosting — production-ready from $11 a month
Database CI/CD platform for schema change review, rollout, and access control. Deployed on your own dedicated instance in AWS, Azure, or GCP, kept patched, backed up, and monitored by ManageStacks — standard Bytebase, no lock-in.
Bytebase on ManageStacks is an open-source database CI/CD tool for developers and DBAs, deployed to your own AWS, Azure, or GCP region with flat per-app pricing from $11 a month ($25 on the Standard production plan). It adds review, approval, and rollout workflows to schema changes, replacing manual migration scripts or hosted tools like Liquibase Hub.
What does Bytebase do, and why do teams deploy it?
Bytebase is a database change management platform written mostly in Go. It connects to your database instances and routes schema and data changes through an issue-based workflow where developers submit SQL, automated checks review it, and DBAs approve before rollout. Changes can be applied across environments such as test and production in a defined order, with history kept for every instance. It also provides SQL editing with access controls and can integrate with Git repositories so migrations are versioned alongside application code. Teams use it to bring review and auditability to database changes without building their own process.
- Issue-based workflow for submitting and approving SQL changes
- Automated SQL review rules before rollout
- Staged rollout across test and production environments
- Schema change history per database instance
- Git integration for versioned database migrations
- SQL editor with role-based access controls
Database CI/CD platform for schema change review, rollout, and access control
Bytebase as a self-hosted alternative to Liquibase Pro, Flyway Teams and Atlas Cloud
Instead of paying per-seat fees to a SaaS vendor, teams self-host Bytebase to keep full control of their data and infrastructure. ManageStacks removes the operational overhead — you get the cost and privacy benefits of open source with the reliability of a managed platform.
What does managed Bytebase hosting cost?
Flat per-app pricing, in your chosen AWS, Azure, or GCP region. No per-user pricing — a busy deployment costs the same as a quiet one.
Starter
Staging and internal tools. Dedicated instance, TLS, daily backups, managed upgrades.
Standard
Production workloads. Adds monitoring, staging environment, region choice, priority support.
Business
High-traffic and compliance workloads. Adds a high-availability replica and same-day support.
24×7 SRE retainer
Round-the-clock on-call across every hosted application, for teams that need a pager answered at 3am.
When is self-hosting Bytebase the right answer instead?
“Managed hosting is not always the correct call.”
Self-host when a platform team already runs the infrastructure and on-call rotation to operate Bytebase at genuinely low marginal cost. Self-host when compliance requires an air-gapped or on-premises deployment that no hosted option can satisfy. And self-host when the deployment depends on heavy customisation with a fast internal build-deploy loop, because an internal release process will beat any managed change process.
For everyone else — teams whose engineers have better things to do than shepherd upgrades — managed hosting is cheaper than the hours it replaces.
Which cloud should Bytebase run on — AWS, Azure or GCP?
For most workloads, the choice of cloud matters less than proximity: run Bytebase in the same cloud and region as the applications and data it talks to, because every request between them adds a round trip. The underlying compute performs equivalently across AWS, Azure, and GCP.
In practice, an existing cloud footprint decides it. All plans support all three clouds, and moving regions later is a scheduled migration, not a rebuild.
Deepest managed-service catalog, default when there's no existing footprint
Best fit for teams already on Microsoft 365 or Entra ID
Strongest for data/analytics-adjacent workloads
Every plan supports AWS, Azure, and GCP — region choice included.
Common questions about Bytebase on ManageStacks
What is Bytebase on ManageStacks?
Bytebase is a database CI/CD tool that manages schema changes through review and approval. ManageStacks hosts it in your own cloud account, so connection details for your databases stay inside your environment.
How does Bytebase compare to Liquibase?
Liquibase is primarily a migration library and CLI, with additional commercial products around it. Bytebase is a web platform with approval workflows, environments, and access controls on top of schema changes. Many teams use it to add governance to migrations.
Can Bytebase check my SQL before it runs?
Yes. Bytebase includes SQL review rules that can flag risky or non-conforming statements before a change is approved. You choose which rules to apply per environment, so production can be stricter than test.
Can I keep my migration history if I move to my own Bytebase?
Yes. Migration history is stored in the Bytebase metadata database and your Git repositories, and your target databases remain untouched. You keep ownership of the records and can export or restore them as needed.
Does Bytebase fit a team with separate developers and DBAs?
Yes. Developers submit changes, and DBAs or designated approvers review them under roles you assign. This separates who writes a change from who approves it, which many teams need for audit purposes.
Other devtools tools on ManageStacks
WordPress
Open-source publishing platform for websites, blogs, and online applications
GitLab
Single DevOps platform for Git hosting, CI/CD pipelines, code review, and security scanning
Drupal
Open-source content management platform for structured, multi-author websites
Joomla
Open-source content management system for websites and online applications
Run Bytebase without carrying the pager
Subscribe through your AWS, Azure, or GCP marketplace. We handle provisioning, SSL, monitoring, backups, updates, and security. From $11/mo.