DocSpring reports eight years running production on Convox PaaS
DocSpring's engineering team describes migrating from Heroku to Convox on AWS in 2018, initially as a way to use free AWS credits without building its own deployment platform. The company now runs production racks in the US and EU plus a staging rack, and has progressively taken over Terraform configuration, moved infrastructure from ECS to Kubernetes, and added its own security, compliance and access controls.
GoKawiil's interpretation of the reporting above, not reported fact.
The account illustrates how a convention-over-configuration PaaS can let a small team defer infrastructure decisions early on while still allowing deep customization later, since Convox's open-source rack runs inside the user's own cloud account rather than a vendor's. DocSpring's experience also shows that adopting such a platform does not lock a team out of eventually rebuilding core pieces, like moving from ECS to Kubernetes, which may be useful context for teams evaluating PaaS tools for long-term AWS deployments.
- DocSpring migrated from Heroku to AWS via Convox in 2018, originally called FormAPI.
- The team has since moved from ECS to Kubernetes and built custom security, compliance, and access layers.
- Convox's open-source rack is Apache-2.0 licensed and runs inside a user's own cloud account, with an optional paid Console for team workflows.
Source: docspring.com, 2026-11-14
Published there as: “Eight years of running DocSpring on Convox”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.