How Springwinter differs from traditional PaaS
Many managed platforms operate the infrastructure on your behalf. Ownership, networking, pricing, and migration options differ by provider. Compare those boundaries against your requirements rather than assuming every platform has the same model. Springwinter inverts this model. You connect your AWS account once, and every resource Springwinter creates belongs to you from the first second. Springwinter reads operational data from that account to provide the dashboard. Resource records, workflow history, cached observations, and project-chat history are retained by the control plane; see Where the data lives. AWS bills you directly for resource usage. The Springwinter platform fee is separate; review current pricing. If you ever stop using Springwinter, every resource it created continues running in your account — you retain the AWS resources, but operating them without Springwinter can require replacing deployment and management workflows. Springwinter provides workflows for supported networking, delegated IAM access, container deployments, certificates, and cost views through a dashboard and REST API. You configure compute capacity; automatic compute scaling is not enabled. AWS availability, quotas, application correctness, and compliance remain part of your operating responsibilities.Get started
Quickstart
Connect your accounts and deploy your first supported service.
Connect AWS
Link your AWS account via a CloudFormation IAM role.
Connect GitHub
Install the GitHub App to enable automatic deploys on push.
API Reference
Explore the full REST API and automate your workflows.
Resource types
Springwinter supports six resource types, each provisioned as a first-class AWS service in your account.Web Servers
Containerized HTTP services running on Amazon ECS with an Application Load Balancer and automatic TLS.
Workers
Background processing services running on ECS with no public URL — queues, cron jobs, and event handlers.
Static Websites
HTML, CSS, and JavaScript sites served from S3 and accelerated by CloudFront with automatic HTTPS.
Caches
Valkey (Redis-compatible) caches on ElastiCache with TLS enforced, accessible from your other services.
Databases
PostgreSQL and MySQL databases on Amazon RDS, provisioned in your VPC with automated backups.
Storage
Private S3 buckets with scoped access policies for assets, uploads, and build artifacts.
Workload resources remain in your AWS account. Operational data passes through Springwinter to provide the product. See Where the data lives and Credentials for stored records, caches, and credential handling.