Welcome to Seagit Docs
A DevOps platform that simplifies building cloud infrastructure and deploying applications. Spin up a secure, globally distributed footprint for your startup in minutes—not weeks.
Providers connect Seagit to your cloud account Link a provider to grant least-privilege access—required before Seagit can deploy applications or create infrastructure in your account.
Create and manage Networks in Seagit to define a virtual private network (VPC). This isolated, secure fabric is where you deploy clusters and applications.
Configure regions, CIDR ranges and subnets, routing and peering, and attach gateways and policies to control connectivity between environments.
Clusters
Kubernetes clusters run containerized workloads in the cloud, providing scheduling, autoscaling, self-healing, rolling updates, service discovery, networking, and policy controls across a pool of nodes.
Today Seagit supports AWS Elastic Kubernetes Service (EKS). We are working on adding Amazon ECS next, and we plan to expand support to additional cloud providers (e.g., GKE, AKS) soon.
Environments
Environments group multiple clusters under a single logical boundary that dictates how applications are deployed across them. They centralize policies, quotas, RBAC, secrets, and network rules, and define promotion paths (dev → staging → prod). Deployments can fan out to many clusters with per-cluster overrides, supporting strategies like canary and blue-green while enforcing consistent guardrails.
Environments can enforce DNS boundaries for applications. Define a base domain per environment (e.g., dev.example.com, staging.example.com, prod.example.com) and require every service to publish under that suffix. Seagit reserves subdomains, updates DNS records (A/AAAA/CNAME), and issues TLS certificates automatically, preventing collisions across teams. Policies can restrict custom domains, require HTTPS/HSTS, and control wildcard usage. Provider integrations (Route53, CloudDNS, Cloudflare) keep records in sync across deployments and multi‑cluster rollouts while preserving a consistent FQDN per environment.