Live data from Hacker News

Removal of Heroku free product plans

help.heroku.com

551–560 of 590 posts

Re: Removal of Heroku free product plans

#551

Earlier quoted context omitted.

classy! I was just about to write an email too, I guess I won't... yet?

Yeah. I did some Internet sleuthing and found a potential contact for the Salesforce Open Source Program Office and reached out. We'll see if they get back.

So, after contacting Bob Wise via Linked In (as he graciously invited readers of his blog post to do!), I constructed a concise but hopefully persuasive email about why they might want to sponsor me, to eventually successfully get this form response...

> Thank you for reaching out to ospo-heroku-credits@salesforce.com in reference to requesting Heroku Credits for qualified and selected Open Source Programs.

> We are in the process of finalizing the selection criteria and will contact you when we are ready to start the process; we anticipate this as no later than Dreamforce.

> In the meantime, should you have any questions or feedback, please do not hesitate to contact us via the above email address.

["above email address" not sure what it means, the email was sent from a personal email address, which i won't share on HN]

So... not yet, in fact!

I had to look up what/when is "Dreamforce", looks like Sep 20-22.

Re: Removal of Heroku free product plans

#552
I don't mind paying their fees for production resources (e.g. they ALREADY force that for the Team accounts where no free tier dynos are available) but now they effectively killed any kind of experimentation and pipelines — now EVERY single app will have to use the paid Postgres, paid Redis, and paid dynos and that can add up quickly (basically $29 per app, no matter if it's production, staging, or a review app...)

Re: Removal of Heroku free product plans

#553
post #244

Unlike most of their competitors, I don't think I have ever heard of someone migrating to Heroku. Seemingly the only people who are still using it are using it because they started with it, usually with their free product. I'm no expert or anything, but it seems like a bad idea to cut off that funnel of future customers by eliminating that free product.

I used to start my projects on Heroku because the first few iterations of the prototype can run on the free dynos, then hobby tier for the first production, better database when needed, and so on — slowly growing as it should be.

Now I will either replace it by some DigitalOcean droplet or Fly.io or Railway.app or whatnot. Whichever makes most sense for the growth of the project.

I am pretty sure some of my clients will stay on Heroku just because it's easier and they already pay for most services (so no free tier already) but it means NO NEW clients are coming to Heroku from me.

Re: Removal of Heroku free product plans

#554
post #95

We pay Heroku thousands of dollars a month for our Staging and Production environments, and one of the reasons we chose them is that we can spin up a toy widget or proof of concept in seconds for free : we probably do a few of those a day, play around with them for a few days or weeks, and then kill them. Now that these toys aren't free, I would guess likely to move them to AWS or GCP (since they're likely to be chea…

As a CTO of a company which has a very similar situation - I can fully agree on that. We already started looking into a possible migration to another cloud provider. The biggest decision point would be a similar developer experience as with git push heroku master.

I have some experience with AWS ElasticBeanstalk that I used to migrate to my Heroku apps at some point.

With their Amazon Linux 2 they use the Procfile and it feels VERY close to Heroku with deployments (it has its own quirks though, like they have those managed upgrades that are sometimes breaking the app for some reason, etc.) but I am pretty happy with how easy it is compared to the previous AWS EB platform.

The problem is only the cost, i.e., when you have to pay for everything it is a bit more pricey (and settings are pain, those VPCs and security groups and whatnot, not fun)

Re: Removal of Heroku free product plans

#556
post #244

Unlike most of their competitors, I don't think I have ever heard of someone migrating to Heroku. Seemingly the only people who are still using it are using it because they started with it, usually with their free product. I'm no expert or anything, but it seems like a bad idea to cut off that funnel of future customers by eliminating that free product.

I used to start my projects on Heroku because the first few iterations of the prototype can run on the free dynos, then hobby tier for the first production, better database when needed, and so on — slowly growing as it should be. Now I will either replace it by some DigitalOcean droplet or Fly.io or Railway.app or whatnot. Whichever makes most sense for the growth of the project. I am pretty sure some of my clients w…

If you're looking at alternatives, you might check out Adaptable.io. There's a free tier that includes the database.

Re: Removal of Heroku free product plans

#557

Same boat as many others. We spend $5000 a month on Heroku. We run production apps and then over 150 review apps at once. We are using paid dynos but free tier redis and Postgres. With literally a couple entires in redis and a few hundred rows in Postgres. This is going to massively increase the bills for review apps - with 0 positives and no alternatives. The hacks, the downtimes, the communication, the support, lac…

If you are dealing with a lot of "empty databases" you can basically make something like a "core app" — attach cheapest paid redis and postgres to it, then copy the credentials between apps.

I have done this before — had one "X-core" app and "x-whitelabel-1", "x-whitelabel-2", and so on, connected to the same database while each app used different database name.

Re: Removal of Heroku free product plans

#558
When SF bought Heroku, it was something like, hey! We need to get on board with this cloud stuff. Our infrastructure using these pods of oracle + big iron no longer make good sense. So, as a multi billion dollar company what do they do. They don't pay for services, they don't build it from the ground up, they buy the hottest business on the market at the time.

For the first few years it was somewhat hands off. Let things gel and start installing SF leaders into the upper ranks on the Heroku org. Then the endless strategic plans to integrate and transition both advancing SF existing stacks and extending Heroku stacks with SF specialty hooks. Heroku Connect, etc.

The young elite engineers at Heroku had very little interest in build CRM product. So it wasn't necessarily full blown revolt, but rather total lack of enthusiasm and effort. Which led to some key firings in management, and more crony installation until the real heads of Heroku took the reigns and secretly put all future energies into SF integration to the extent that Heroku should ultimately become a product wing of SF much Einstein, Cloud..etc.

At this point, upper management told Heroku staff not to worry. Nothing is getting cancelled and every manner of 'remain calm' language. Narrowly curbing a full blow revolt. The key facilitators of which being coaxed into supplying company wide admissions that they were wrong, and everything is fine, and hurray, I love Heroku and I love SF. All of them were then discreetly fired weeks later, some of which continued the ruse, probably under duress, that everything is great and this is just a move based on growing a career and not dissatisfaction.

Over the next couple years, the typical corporate agenda played out of endless cost cutting, employee benefit slashing, and general freedom neutering. The talent by this point had drastically evaporated.

And here we are today. No talent to extend and create new services. No ability to keep pace with other cloud offerings. Continued denial about the true reality of what is going on with the business. With multi million dollar customers more or less in the dark about the fact they are running on what is tantamount to abandonware. Enter the first waves of service sun setting seasoned with a nice dose of kool aid.

You need to realize something else. Heroku was never unprofitable while SF owned them (possibly ever). It's just that the millions Heroku was generating was literally peanuts compared to the SF earnings. They needed to scratch an itch and thought they could do it by just buying the tool factor rather than the tool. The fact that they drove the tool company into the ground is of little consequence when you look at the numbers in play.

There are specific people who are directly culpable for the downward spiral of Heroku. Yes-men/women without a single stitch of the vision and drive that created Heroku and it's earlier success.

Heroku died in my arms years ago. It's all very sad.

Re: Removal of Heroku free product plans

#559
post #522

Earlier quoted context omitted.

I can’t provide support here, but I can say next week I’m going to be cracking open the source code in that project to look into issues like this and figure out it I can’t get it to also move over the database. If you post about this at https://community.fly.io/ others in the same boat as you and other folks from Fly will see this and give you a better response.

Thanks for your quick response! I was able to work around the broken Turboku form and also get my database migrated to fly.io with a bit of adjustment period with flyctl. Just closed out my last invoice with Heroku and closed my account!

Alrighty, I wrote some docs! https://fly.io/docs/rails/getting-started/migrate-from-herok...

That includes a section on migrating your Heroku DB :-)

Re: Removal of Heroku free product plans

#560
Just moved a django app from heroku hobby to fly.io. flyctl CLI, the documentation was super easy to work with. Fly.io Trial Plan is a decent alternative for Heroku hobby dynos (SSL certs through Let's Encrypt was a pleasant surprise).
Post reply on HN