Bring your own cloud
Your cloud account. Your Kubernetes. Our automation.
SeaGit provisions managed Kubernetes clusters inside the AWS, GCP, Azure or Digital Ocean account you already own — so you keep the VPC, the data, the region and the cloud bill, without running the platform layer yourself.
What is bring your own cloud?
Bring your own cloud (BYOC) is a deployment model where the platform you buy runs inside infrastructure you already own, instead of on the vendor's servers. With SeaGit you connect your own cloud account with least-privilege access, and SeaGit provisions a VPC, a managed Kubernetes cluster — Amazon EKS today, with Azure and GCP support — and the node groups it needs, all inside that account. Your cloud provider bills you directly for the compute, storage and networking, and SeaGit charges a flat per-seat platform fee with no infrastructure markup. The practical consequences are ownership ones: your data stays in your VPC and your region, your existing compliance agreements keep applying, and if you stop paying for the platform you still have standard EKS clusters running the applications you deployed. A vendor-hosted PaaS gives you none of those.
What runs in your account, and what doesn't
In your cloud account
- • The VPC, subnets and CIDR ranges
- • The Kubernetes cluster and every node group
- • Your applications, their containers and their data
- • Cluster add-ons: ingress, external-dns, cert-manager, monitoring
- • Container images built in your own cluster
- • DNS zones and TLS certificates for your domains
On SeaGit
- • The control panel and API you drive it all from
- • The automation that plans and applies infrastructure changes
- • Deployment orchestration, history and rollbacks
- • Your account, team, roles and audit log
- • Scheduled automation rules for cost control
Why teams choose BYOC over a hosted PaaS
No infrastructure markup
You pay your cloud provider what your cloud provider charges. A hosted PaaS buys the same compute and resells it to you, which is why the gap widens as you scale. SeaGit's fee is per seat and does not move when your traffic does.
Compliance you already have
Workloads never leave your account, so the controls and agreements you hold with your cloud provider — including SOC 2 and HIPAA arrangements — continue to cover them. There is no new processor sitting between your application and its data.
A real exit path
The clusters are standard managed Kubernetes provisioned with Terraform, and deployments are ordinary Helm releases. Leaving the platform means keeping infrastructure you already own, not migrating off someone else's.
Cost controls that are actually yours
Because the resources are in your account, you can scale node groups, use spot instances, and power non-production clusters off on a schedule with action rules — the levers a hosted platform cannot give you.
Read next
Bring your own cloud — FAQ
What does bring your own cloud (BYOC) mean?
- Bring your own cloud means the platform runs your workloads inside a cloud account you own, rather than on the vendor’s infrastructure. With SeaGit you connect your own AWS, GCP, Azure or Digital Ocean account, and SeaGit provisions the VPC, the Kubernetes cluster and the node groups inside it. You keep the account, the network, the data and the direct billing relationship with your cloud provider; SeaGit operates the platform layer on top.
Who pays for the infrastructure under BYOC?
- Your cloud provider bills you directly for compute, storage and networking, because the resources live in your account. SeaGit charges a flat platform fee per seat and never marks up your infrastructure. That also means cost controls are yours to use: action rules can scale clusters down or power them off on a schedule, which is how non-production environments get cheaper rather than by negotiating with a vendor.
What happens to my clusters if I stop using SeaGit?
- The clusters are standard managed Kubernetes — Amazon EKS today — in your own account, created with Terraform and deployed to with Helm. They do not stop existing when a SeaGit subscription does, and your applications keep running. This is the practical difference between BYOC and a vendor-hosted PaaS: the exit path is keeping what you already own rather than migrating off someone else’s servers.
What access does SeaGit need in my cloud account?
- You connect a provider with least-privilege access, and SeaGit uses it to provision and manage the resources you ask for: networks, clusters, node groups, DNS records and certificates. Nothing is provisioned that you have not requested through the platform, and every action is recorded in the audit log.
Is BYOC available on the free plan?
- Yes. SeaGit is bring-your-own-cloud on every plan, including Free — there is no tier where workloads move onto SeaGit-owned infrastructure. Several competitors reserve BYOC for their higher tiers, which is the usual reason a comparison looks cheaper until you reach the plan that offers it.
Does my data leave my cloud account?
- Your applications and their data run in your VPC, in your account, in the region you chose. Because the workloads never move onto vendor infrastructure, the compliance posture you already have with your cloud provider — including SOC 2 and HIPAA agreements — continues to apply to them.