Simple Container (sc) is a cloud-agnostic deployment tool designed to simplify microservices deployment,
infrastructure provisioning, and CI/CD automation.
It allows developers to deploy services effortlessly, while DevOps teams manage infrastructure centrally, ensuring scalability, security, and reliability across multi-cloud environments.
- Infrastructure as Code (IaC) Simplified – Define infrastructure with lightweight YAML configurations, no need for Terraform or Pulumi.
- Effortless Microservice Deployment – Deploy services with one command, using familiar tools like
Dockerfileanddocker-compose.yaml. - Built-in Secrets Management – Securely store and inject credentials using AWS Secrets Manager, GCP Secret Manager, or Kubernetes Secrets.
- Multi-Cloud & Kubernetes Support – Seamlessly deploy to AWS ECS, Google Cloud Run, Kubernetes clusters, and more.
- Built-in CI/CD & Automated Rollbacks – Deploy, monitor, and rollback services without external CI/CD pipelines.
- Comprehensive CloudWatch Monitoring – Built-in alerts for ECS services and Application Load Balancers with Email, Slack, Discord, and Telegram notifications.
To install sc, run:
curl -s "https://dist.simple-container.com/sc.sh" | bashVerify installation:
sc --version-
Initialize a project
sc init
-
Configure infrastructure (for DevOps)
- Define cloud resources in
.sc/stacks/devops/server.yaml.
- Define cloud resources in
-
Define a microservice (for developers)
- Add a
client.yamlfile in.sc/stacks/<service-name>/client.yaml.
- Add a
-
Deploy a service
sc deploy -s myservice -e staging
Check out the full documentation for detailed guides, examples, and best practices.
Cloud integrations ship as independently released plugin binaries that sc
downloads and talks to over a local gRPC bus. Everything about an operator's
client.yaml stays the same; server.yaml names which plugin release to use.
| Plugin | Repository | Owns |
|---|---|---|
aws |
simple-container-com/sc-plugin-aws | aws provider, aws-lambda / ecs-fargate / aws-static-website templates, s3-bucket / ecr-repository / aws-rds-postgres / aws-rds-mysql / aws-cloudtrail-security-alerts resources, aws-kms secrets-provider, s3-bucket state-store, cloud-helpers Lambda |
cloudflare |
simple-container-com/sc-plugin-cloudflare | cloudflare DNS registrar, Workers overrides, Pages Direct Upload |
cloudru |
simple-container-com/sc-plugin-cloudru | cloudru provider, cloudru-container, cloudru-postgres, cloudru-evolution-vm |
mongodb |
simple-container-com/sc-plugin-mongodb | mongodb-atlas provider + ComputeProcessor for uses: env fan-out, PreDestroy database-drop hook |
yandex |
simple-container-com/sc-plugin-yandex | yandex provider, yc-dns, yc-serverless-container, yc-object-storage, yc-kms, yc-lockbox, yc-service-account, yandex-vm |
echo (template) |
simple-container-com/sc-plugin-echo | Template every new plugin starts from — gh repo create --template and swap in your cloud |
Everything else — GCP, Kubernetes, k3s, vm — is still built into sc.
- Operator guide: docs/docs/guides/upgrading-to-plugins.md
— nothing is required of you (plugins auto-resolve to the latest release), but
pinning the
plugins:block inserver.yamlis strongly recommended. - Author guide: docs/docs/guides/plugin-authoring.md
— step-by-step for a new cloud plugin, starting from
sc-plugin-echo. - Runtime library: pkg/plugin/runtime —
NewContext,Settle,HarvestExports,ResourceInputForComputeProcess,DecodeInputs. Every production plugin builds on this; do not re-copy the equivalents from an older plugin. - Bus protocol: pkg/plugin/README.md and pkg/plugin/proto/README.md — RPC surface, dispatch wiring, extraction checklist.
- Design: sc-plugin-architecture (full rationale + two-gRPC conversation shape).
- Trap catalogue: plugin-extraction-playbook — fifteen live-caught traps as of 2026-11-01, with fix patterns and §4 lint-pass checks for the next extraction.
We welcome contributions! Please see our CONTRIBUTING.md for guidelines on how to get involved, and our CODE_OF_CONDUCT.md for the community standards every participant is expected to uphold.
See ROADMAP.md for current themes, release cadence, and where planned work surfaces in the Issues tracker.
Simple Container is open-source and licensed under the MIT License.
- Feature Requests & Issues – GitHub Issues
- Discussions & Updates – Join our Discord
- Enterprise Support – Contact us at support@simple-container.com
- News and announcements - Follow us on X
Start deploying microservices effortlessly with Simple Container today!