DocSpring has run on Convox since migrating from Heroku to AWS in 2018. Convox provides Heroku-style deployments inside a company’s own cloud account: applications are defined in a manifest, and a CLI builds releases, rolls them out gradually, checks health, and can revert failed deployments. Over time, DocSpring’s infrastructure moved from ECS to Kubernetes on AWS EKS. The team now operates production racks in the US and EU plus a staging rack, and has taken on more Terraform management as its needs grew. The author argues that starting with Convox supplied a working platform while also providing a foundation to study and customize, rather than requiring the team to build deployment infrastructure from scratch.
The account also details the responsibilities and costs that come with this control. For SOC 2 requirements, DocSpring built a private API gateway with approval workflows, security-key checks, and audit controls; it also maintains upgrades, monitoring, backups, and security settings. Replacing retired ingress-nginx with Contour required a custom zero-downtime migration and fixes to logging and certificate handling. An example three-zone AWS rack costs about $306 monthly before databases, usage charges, and other services, with roughly $210 in fixed control-plane and networking costs; separate racks add further expense. The author would choose Convox again for teams seeking customizable, Heroku-like deployments in their own cloud, while noting that hosted platforms can be preferable when infrastructure control is unnecessary and that Aptible is another option for strict compliance needs.
Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.