Skip to main content
Springwinter is a hosted control plane that deploys supported resources into your AWS account. Your workloads run in that account; the Springwinter control plane is operated separately. Connect AWS and GitHub to build and deploy applications, inspect resource state, and review costs. You remain responsible for application security and compliance. Automatic compute scaling is not enabled by choosing minimum and maximum task counts.

Quickstart

Connect your accounts and deploy your first supported service.

Connect AWS

Link your AWS account with a one-click CloudFormation stack.

Connect GitHub

Enable automatic deploys from your GitHub repositories.

API Reference

Explore the full REST API for the Springwinter control plane.

What You Can Deploy

Springwinter manages the full lifecycle of every resource type — from first deploy to teardown — all within the AWS account you own.

Web Servers

Containerized HTTP services built from GitHub.

Workers

Background processes with no public URL.

Static Websites

S3 + CloudFront sites built from GitHub.

Caches

Valkey (Redis-compatible) caches over TLS.

Databases

PostgreSQL and MySQL in your account.

Storage

Private S3 buckets with cost and metrics.

How It Works

1

Create an account

Sign up at springwinter.dev with your organization email.
2

Connect your AWS account

Launch a one-click CloudFormation stack. Springwinter assumes a role you control — it never holds permanent credentials.
3

Connect GitHub

Install the Springwinter GitHub App on your organization or personal account to enable automatic builds and deploys.
4

Deploy a service

Create a project, pick a resource type, point it at a GitHub repository, and your first deploy is live.
Your AWS account owns the deployed workload resources. Springwinter reads operational data to display it, and retains resource records, workflow history, cached observations, and project-chat history. See Where the data lives for the boundary.