GET /api/openapi.json before it creates a project or deploys a resource. Reading the schema needs no token; customer data and deployment operations require authentication.
Springwinter guides you from account setup to a supported service in your AWS account. Build and AWS provisioning times depend on your application, selected resources, and account readiness. This guide walks you through every step — creating an account, linking your AWS account and GitHub repository, and watching your first deployment go live. By the end you will have a real ECS service or CloudFront-backed static site running inside your own AWS account.
Before you begin, make sure you have:
- An AWS account with permissions to create CloudFormation stacks and the resources Springwinter needs (ECS, RDS, S3, etc.).
- A GitHub account with at least one repository that contains either a
Dockerfile(for web servers and workers) or a static build output directory (for static websites). - Time for account verification, a source build, and AWS provisioning. No fixed completion time is guaranteed.
1
Create your Springwinter account
Open https://springwinter.dev/auth?mode=signup and sign up with your email address and a password. Confirm the emailed code, then complete onboarding. Google and Microsoft sign-in are not currently enabled.
2
Connect your AWS account
Springwinter deploys resources into your AWS account using a CloudFormation-provisioned IAM role — no long-lived credentials are ever stored. In the dashboard, open Settings → Cloud and click Connect AWS. Springwinter generates a CloudFormation link that creates the required role in your account.Follow the full walkthrough in Connect Your AWS Account, then return here once Springwinter verifies the prepared connection role.
3
Connect your GitHub account
Open Settings → Source control and click Connect GitHub. You are redirected to the GitHub App installation page where you choose which repositories Springwinter can access. After you confirm the installation, you are returned to the dashboard automatically.See Connect GitHub for details on permissions and multi-organization setups.
4
Create a project
In the dashboard, click New Project, give it a name, and confirm. Projects group your related services together and share the same AWS connection and team members. Every resource you create lives inside a project.
5
Add a web server or static website
Inside your new project, click Add Resource and choose the resource type that matches your repository:
- Web Server — your repo has a
Dockerfileand exposes an HTTP port. - Static Website — your repo produces an
index.html(React, Next.js export, Astro, plain HTML, etc.).
6
Watch the build and visit your live URL
The dashboard streams your build logs in real time. For a web server, Springwinter builds your Docker image, pushes it to ECR, and rolls it out on ECS behind a load balancer with a TLS certificate. For a static website, it uploads the build output to S3 and provisions a CloudFront distribution.When the status indicator turns green, click the URL shown on the resource card — your service is live.
What to do next
Web Servers
Configure CPU, memory, task copies, health checks, domains, and environment variables for containerized services.
Workers
Deploy background processing services that run alongside your web servers without a public endpoint.
Static Websites
Customize your CloudFront distribution, set up redirects, and configure build commands.
Observability
Explore CloudWatch logs, CPU and memory metrics, request rates, error rates, and live cost estimates.