Insofar as you can decouple yourself from Heroku service offerings, you are able to decouple from Heroku.
Whether that's a full-service standalone platform like Cloud Foundry (partly inspired by, and partly sharing code with, Heroku), an IaaS-smoothing platform like Convox (founded by Heroku alumni), integrating some intermediate platforms like Deis or rolling your own with Kubernetes or Marathon.
Disclosure: I work for Pivotal, which sells a commercial distribution of Cloud Foundry. And I work in the Cloud R&D section on opensource bits of it. So I have a horse in this race.
Again, disclosure, I work for a competitor.
Pricing is similar for Heroku CI -- you pay for dyno time to run your tests.
Note: I work for Heroku and feedback welcome at [email protected] (about features or docs).
> During the beta period [team name] will only be billed for dyno usage when tests run. After the beta period ends, each pipeline with Heroku CI enabled will be billed at $10/month plus dyno usage.
I guess that's actually a more general criticism of Heroku in the microservices context; high availability (at least 2 dynos per service) and predictable performance (non-shared dynos, Performance-M at minimum) combine to make the cost of a "production" setup start at $500/mo/service. Non-issue for a monolith, quite tough for small microservices.
(To be fair, we compromise on both of those requirements and use both single-dyno apps and shared dynos, and so Heroku is very affordable for us. But the downside of those choices ends up biting us often enough that I, in turn, end up lamenting about it on HN.)