SEAGIT DOCS
Overview

SeaGit Platform Overview

A comprehensive DevOps platform that simplifies cloud infrastructure management and application deployment. Deploy production-grade Kubernetes clusters and applications in minutes, not weeks.

Get Started

What is SeaGit?

SeaGit is a comprehensive DevOps platform that abstracts away the complexity of Kubernetes, cloud providers, and CI/CD pipelines while giving you full control over your infrastructure. It bridges the gap between simple PaaS solutions (like Heroku) and complex infrastructure-as-code tools (like Terraform), providing a visual interface backed by production-grade automation.

Key Features

🌐 Multi-Cloud Support

Deploy to AWS, GCP, Azure, and Digital Ocean from a single interface. Switch providers without rewriting infrastructure code.

☸️ Kubernetes Made Easy

Create production-grade EKS clusters with best practices built-in. No YAML expertise required.

🚀 GitOps Ready

Native integration with GitHub, ArgoCD, and popular CI/CD tools. Deploy from source code, containers, or Helm charts.

💰 Cost Optimization

Automated scaling, spot instances, and scheduled shutdowns. Save up to 60% on non-production environments.

🔒 Enterprise Security

RBAC, secrets management, network isolation, and audit logs. SOC2 and HIPAA compliance ready.

👨‍💻 Developer Friendly

Support for Node.js, Python, Go, Java, and more. Build from source with automatic language detection.

Platform Architecture

SeaGit follows a hierarchical resource model that mirrors real-world DevOps workflows:

Account (Organization)
├── Providers (Cloud Credentials)
│   ├── AWS
│   ├── GCP
│   └── GitHub
├── Networks (VPCs)
│   └── CIDR, Subnets, Regions
├── Clusters (Kubernetes)
│   ├── Node Groups (On-Demand, Spot)
│   ├── Add-ons (Ingress, DNS, Monitoring)
│   └── Logs
├── Environments (Logical Boundaries)
│   ├── DNS Configuration
│   ├── Ingress Settings
│   ├── Spaces (Namespaces)
│   └── Attached Clusters
├── Applications (Templates)
│   ├── Source Configuration
│   ├── Resource Requirements
│   └── Network Settings
└── Application Instances
    ├── Environment Assignment
    └── Deployments

Core Concepts

1. Infrastructure Layer

  • Providers: Connect your cloud accounts (AWS, GCP, etc.) with least-privilege access
  • Networks: Virtual Private Clouds (VPCs) with custom CIDR ranges and subnets
  • Clusters: Kubernetes clusters (EKS) with configurable node groups and add-ons

2. Deployment Layer

  • Environments: Logical groupings (dev, staging, prod) with DNS and policies
  • Spaces: Kubernetes namespaces for team/project isolation
  • Applications: Reusable templates defining how apps are built and deployed
  • Instances: Environment-specific deployments of application templates

3. Operations Layer

  • Deployments: Individual application releases with logs and monitoring
  • Variables & Secrets: Configuration management with inheritance
  • Action Rules: Scheduled automation for cost optimization
  • Domains: Custom domain management with automatic DNS and TLS

How SeaGit Works

1. Setup Infrastructure (One-time)

  1. Add cloud provider credentials
  2. Create network/VPC
  3. Create Kubernetes cluster
  4. Install add-ons (ingress, cert-manager, etc.)

2. Configure Environments (One-time)

  1. Create environments (dev, staging, prod)
  2. Attach clusters to environments
  3. Configure DNS and ingress
  4. Set up variables and secrets

3. Deploy Applications (Ongoing)

  1. Create application template
  2. Define source (code, container, Helm)
  3. Set resource requirements
  4. Create instance per environment
  5. Deploy and monitor

4. Optimize & Automate (Optional)

  1. Set up action rules for scheduled scaling
  2. Configure monitoring and alerts
  3. Implement multi-cluster deployments
  4. Add custom domains

Why SeaGit?

❌ Without SeaGit

  • Hours of manual YAML configuration
  • Managing credentials across multiple tools
  • Debugging failed deployments with cryptic errors
  • No visibility into application health
  • Manual DNS and certificate management
  • Expensive 24/7 running dev environments

✅ With SeaGit

  • One-click cluster creation with best practices
  • Centralized credential management
  • Clear deployment logs and error messages
  • Real-time monitoring dashboards
  • Automatic DNS and TLS certificates
  • Scheduled shutdowns saving 60% on costs

Who Uses SeaGit?

🚀 Startups

Get production infrastructure in minutes, not weeks. Focus on your product, not DevOps.

👨‍💻 Development Teams

Deploy without DevOps expertise. Self-service deployments with guardrails.

🏗️ Platform Engineers

Maintain consistency across projects. Reusable templates and centralized policies.

💼 CTOs

Reduce cloud costs and improve security posture. Audit logs and compliance reports.

Platform Comparison

FeatureSeaGitAWS ConsoleTerraformManual K8s
Setup Time5 minutes2 hours1 day3 days
K8s ExpertiseNoneSomeAdvancedExpert
Multi-Cloud✅ Yes❌ AWS Only✅ Yes✅ Yes
Cost Optimization✅ Built-in❌ Manual❌ Manual❌ Manual
GitOps Ready✅ Yes❌ No⚠️ Complex⚠️ Complex
GUI + API✅ Both✅ Both❌ CLI Only❌ CLI Only

What's Next?

Ready to get started? Here are the recommended next steps:

Getting Started →

Complete tutorial to deploy your first app

Set Up Cluster →

Create your first Kubernetes cluster

Deploy Application →

Learn how to deploy your app

Support & Community

Next: Providers