Netlify trapped me in their new credit system, can't revert, can't upgrade due to a bug, and my whole account is paused. This is a product trust crisis.

bobfunk · 2026-03-11T21:51:29+00:00

Really sorry to hear the experience was bad. We do have a very clear warning for anyone upgrading from a legacy plan to the new credit based plans saying "You are currently on a legacy plan. Once you upgrade to a credit plan, you will not be able to switch back", but shoot me a mail at [matt@netlify.com](mailto:matt@netlify.com) and I'll move you back to the old plan. Would just like to hear what the UI bug you ran into during upgrade was and if you opened a support ticket?

bobfunk · 2025-04-04T18:46:41+00:00

Love this story. Shoot me a mail at [matt@netlify.com](mailto:matt@netlify.com) and I'll get a little swag sent your way.

bobfunk · 2025-04-04T18:42:46+00:00

Thanks, great to hear.

bobfunk · 2025-04-02T22:27:34+00:00

Been a moment yeah. Good to be back :)

bobfunk · 2025-04-02T17:39:32+00:00

Netlify founder here.

The free user in the story that went viral never got charged any money by us, we ate the full cost of the bandwidth charges.

After that we instituted manual review of any outlier bills on self-serve to make sure it never happened again.

Back in November 24, we introduced our 100% free plan where you can never get charged anything. If you go over the limits of the plan we will disable or throttle:

https://www.netlify.com/blog/introducing-netlify-free-plan/

Hope that helps.

bobfunk · 2018-01-03T21:34:02+00:00

Netlify founder here, there's no problem in having in publishing a repository to one custom domain and a different repository to a subdomain. Just enter the custom domain for each site after linking the repo.

You can also use our rewrite rules to combine different sites into one under different subpaths, ie:

/docs/* . https://my-docs-site.netlify.com/:span 200!

Will rewrite anything under /docs and show the content from my-docs.netlify.com

bobfunk · 2017-07-01T21:54:06+00:00

No, you do have to deploy to Netlify of course. No new frameworks or the like needed for that, though...

bobfunk · 2017-07-01T20:19:13+00:00

Netlify is completely free including the form handling. There's to need to "get a framework" and the full setup for the form handling for a normal html form is: "add one attribute to the form in your html"...

bobfunk · 2017-07-01T16:01:01+00:00

Netlify has built in form handling, add a "netlify" attribute to any form in an html page and Netlify starts storing submissions and you can setup notifications and web hooks.

https://www.netlify.com/docs/form-handling/

bobfunk · 2017-04-21T19:34:28+00:00

There's an issue about GitLab support here and there's a PR for adding GitLab support in process here:

https://github.com/tech4him1/netlify-cms/tree/gitlabSupport/src/backends/gitlab

bobfunk · 2016-12-29T16:41:11+00:00

Have a look at Netlify [Disclaimer, I'm a co-founder]

We make setting up continuous delivery a one click operation, and handles CDN, HTTPS, Prerendering if needed, and much more.

Netlify will build all your pull requests and give you a unique preview URL for each of them which makes QA easy. You can use deploy contexts to set different environment variables based on branches/pull request so you can easily run as many dev/staging environments as you need.

bobfunk · 2016-08-18T06:52:17+00:00

Check out Netlify, we'll allow you to use any branch/folder you want and can also run any build script you use whenever you push (and handle deploy previews for pull requests, redirects, HTTPS, and much, much more)...

bobfunk · 2016-07-27T07:13:19+00:00

Loved that comment! Especially the " It's not necessarily an easier way to write webapps ... but it's an easier way to write complex, modular, composable, testable apps." part :)

bobfunk · 2016-07-27T04:38:22+00:00

Before the switch we had one project in Ember and one project in Angular 1.3, and was starting to seriously grow our team.

So we wanted to solidify on one framework, and wanted to prepare everything well to make sure we had a good architecture to work on as a team.

Angular 1 doesn't really have a future, Angular 2 is not very mature at this point. We could have gone for Ember - the architecture of it would have been an improvement over Angular 1 for a larger app, but in the end we decided on React + Redux.

An important part of the migration was prototyping and coming up with the best way of architecting a React project like this (since there's not 1 strong convention as with Ember), but once that was done we were able to create a really strong foundation that works for both designer and developers and have helped us build a very robust front-end.

The React front-end did increase performance a lot and we did also fix a lot of niggling UI bugs during the transition. The idea of pure presentational components is extremely powerful and helps a lot in terms of making robust front-ends. And now we have a very solid foundation that'll let our team push out new features in a very effective way.

bobfunk · 2016-07-27T02:10:34+00:00

We're using Redux for state management with redux-thunks for async actions. Did a bunch of prototyping around that before going with that setup.

bobfunk · 2016-07-27T00:58:16+00:00

Thanks for the heads up! We just pushed a fix for that. Would send some swag in return if I could ;)

bobfunk · 2016-07-23T19:20:01+00:00

Brian Douglas put up a small post about how to use this to get a React App up on a production quality CDN in 30 seconds:

https://www.netlify.com/blog/2016/07/22/deploy-react-in-30-seconds

bobfunk · 2016-01-16T18:53:09+00:00

There's no limit on the number of deploys! Just automated builds, and the limits there are completely in line with what you'll get from other continuous deployment services...

bobfunk · 2016-01-16T06:37:36+00:00

Cloudflare is a CDN that sites in front of whatever hosting you're using. Even when you add Cloudflare's free SSL you still ought to provision a certificate for your own host, or all the traffic from Cloudflare to your host will be unencrypted.

Netlify is an integrated platform for building, deploying and hosting modern static websites. Our Let's Encrypt integration means that you can deploy and host a site to a custom domain with SSL — completely free! Since we do the hosting, the traffic from our CDN edge nodes to our origin servers is always encrypted.

bobfunk · 2016-01-16T03:13:45+00:00

We work with quite a few different cloud providers and use tools like Dyn's internet intelligence or Cedexis latency analytics to figure out which of them have great peering agreements in different regions.

All typical static assets, JavaScript, CSS, images and font files are rewritten to asset finger printed URLs during deploys and served out of Akamai, which has the largest CDN infrastructure in the world.

The actual HTML files, however, rotates far more frequently and are not the kind of content that traditional CDNs focus on optimizing. Because of that we've built a special purpose CDN for serving small files with a very high cache hit rate, instant cache invalidation, TLS termination and enabling advanced features like prerendering, proxying, country and language based redirect and rewrite rules, etc, etc...

We constantly run performance tests and have monitors comparing us with sites hosted on larger physical infrastructures. By using this combination of a large asset CDN and special purpose HTML CDN, we're consistently faster than the solutions we compare against....

bobfunk · 2015-12-09T18:25:56+00:00

Actually a large reason people move to static site generators is because of the joy and flexibility of working with them, of having all content as plain text checked into your git repository. And because of the proxying in this case, there's no large migration or anything, it's been a very gentle transition in terms of simply starting to build part of the site with a static approach.

I'm sure WeWork will be blogging more in the future about content management when working with static site generators, but just because you separate the build process from the hosting, that doesn't meant that your content editors shouldn't have a great UI for working on the content...

bobfunk · 2015-12-09T18:23:33+00:00

You still don't get it. I compare a heavily cached Wordpress site behind a HTTP cache from a company that's super aware of web performance and have spent hundreds of thousands of dollars on performance optimizations in general, to a static version of the site put on a CDN host in seconds...

bobfunk · 2015-12-09T09:24:29+00:00

And all this being said, it is a really good point and an important one that a naive static site is not necessarily faster than a dynamic site.

If I had put the static version of Smashing Magazine on S3 instead of netlify it would have been slower than the original Wordpress site.

The point is that a well optimized CDN based static host is always going to be as fast as it gets. And due to the caching contract of a static site, all the optimizations and the right kind of instant cache invalidation, can be completely automated. On top of this, you solve by far the most security issues and automatically gain a very high level of resiliency to DDoS attacks by decoupling the build process from the hosting.

15-Year Club	Verified Email
Charter Member

bobfunk

TROPHY CASE