What is SeaGit?

SeaGit, defined

SeaGit is a Kubernetes DevOps platform for engineering teams that want production infrastructure without a dedicated platform team. It provisions managed Kubernetes clusters — Amazon EKS today, with Azure and GCP support — inside your own cloud account rather than on SeaGit-owned servers, so you keep ownership of the VPC, the nodes and the data, and you pay your cloud provider directly with no infrastructure markup. On top of the cluster, SeaGit adds a push-to-deploy workflow: GitOps CI/CD triggered from GitHub, a one-click add-on catalogue (Argo CD, Argo CI, Prometheus, MinIO, cert-manager, external-dns), automatic DNS and TLS certificates, and ephemeral preview environments that give every commit its own isolated URL without touching the live deployment. Clusters are provisioned as Amazon EKS with Terraform-managed VPCs and node groups, and applications ship as ordinary Helm releases you can inspect with kubectl. A free plan is available.

Underneath, SeaGit is built on standard, inspectable components — Kubernetes, Helm, Terraform and Argo — so anything it provisions remains yours and remains readable with the usual tooling. See the platform overview for how providers, networks, clusters, environments and applications fit together.

Other things called “Seagit”

The name, and the near-spelling “Seagirt”, are shared with several unrelated companies, projects and places. None of them are affiliated with SeaGit, and SeaGit is not affiliated with any of them — if you arrived here looking for one of the following, this is not it.

What SeaGit actually does

1. 1

   Your cloud account, not ours

   SeaGit provisions the VPC, the managed Kubernetes cluster and the node groups inside your own AWS, Azure or GCP account. You keep ownership of the infrastructure and the data, and your cloud provider bills you directly with no SeaGit markup.

2. 2

   Push-to-deploy on real Kubernetes

   Connect a GitHub repository and SeaGit builds and deploys it through GitOps CI/CD. Applications ship as Helm releases you can inspect with kubectl — there is no proprietary runtime to be locked into.

3. 3

   The platform layer, pre-wired

   A one-click add-on catalogue installs Argo CD, Argo CI, Prometheus, MinIO, cert-manager and external-dns, with DNS records and TLS certificates issued automatically for every deployment.

4. 4

   A preview URL for every commit

   Ephemeral deployments give each commit its own isolated URL inside the same environment as production — a true dark release, with the main deployment never overwritten by CI/CD.

Weighing it against a PaaS? See how SeaGit compares to Heroku, Vercel and Railway, or read about preview environments, pricing and the team behind it.

SeaGit — frequently asked questions

What is SeaGit?

SeaGit is a Kubernetes DevOps platform for engineering teams that want production infrastructure without a dedicated platform team. It provisions managed Kubernetes clusters — Amazon EKS today, with Azure and GCP support — inside your own cloud account rather than on SeaGit-owned servers, so you keep ownership of the VPC, the nodes and the data, and you pay your cloud provider directly with no infrastructure markup. On top of the cluster, SeaGit adds a push-to-deploy workflow: GitOps CI/CD triggered from GitHub, a one-click add-on catalogue (Argo CD, Argo CI, Prometheus, MinIO, cert-manager, external-dns), automatic DNS and TLS certificates, and ephemeral preview environments that give every commit its own isolated URL without touching the live deployment. Clusters are provisioned as Amazon EKS with Terraform-managed VPCs and node groups, and applications ship as ordinary Helm releases you can inspect with kubectl. A free plan is available.

Is SeaGit related to Seagate?

No. SeaGit is a cloud DevOps and Kubernetes platform at seagit.com. Seagate Technology is a separate, unrelated company that manufactures hard drives and mass-capacity storage hardware. The two share no ownership, products or affiliation — the names are simply similar. If you are looking for storage hardware, you want Seagate; if you are looking to deploy Kubernetes clusters and applications into your own cloud account, you want SeaGit.

Is SeaGit the same as the SEAGit Git client for Windows?

No. "SEAGit" on the Microsoft Store is an unrelated desktop application — a simple graphical Git client for committing, pushing and pulling on Windows. SeaGit (seagit.com) is a hosted cloud platform: it provisions managed Kubernetes clusters in your AWS, Azure or GCP account and runs GitOps CI/CD and deployments against them. SeaGit is not a desktop Git client and is not distributed through the Microsoft Store.

What does the name SeaGit mean?

SeaGit is pronounced "sea-git" and is written as one word with a capital S and G. The name combines "sea" — the cloud your infrastructure runs in — with "Git", the version-control system that drives every deployment on the platform, since SeaGit builds and deploys from your Git repository. It is unrelated to the similarly spelled "Seagit Arc" music project.

How is SeaGit different from Heroku, Vercel or Railway?

Heroku, Vercel and Railway run your workloads on infrastructure they own and bill you a margin on top of it. SeaGit provisions the infrastructure in your own AWS, Azure or GCP account, so you keep the cloud account, the VPC, the data and any committed-spend discounts, and you pay the cloud provider directly with no infrastructure markup. You get the same push-to-deploy experience, but on standard managed Kubernetes you can inspect with kubectl and keep if you ever leave.

Is SeaGit free to use?

SeaGit has a free plan intended for exploring the platform rather than running production systems, plus paid plans that raise the cluster and deployment limits. Because SeaGit does not host your infrastructure, your cloud provider bills you separately for the compute, networking and storage the clusters consume — SeaGit adds no markup to that cost.