Alternatives to Netlify logo

Alternatives to Netlify

Surge, Heroku, GitHub Pages, CloudFlare, and Firebase are the most popular alternatives and competitors to Netlify.
2.1K
1.6K
+ 1
186

What is Netlify and what are its top alternatives?

Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment.
Netlify is a tool in the Static Web Hosting category of a tech stack.

Top Alternatives to Netlify

  • Surge

    Surge

    Surge makes it easy for developers to deploy projects to a production-quality CDN through Grunt, Gulp, npm. ...

  • Heroku

    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • GitHub Pages

    GitHub Pages

    Public webpages hosted directly from your GitHub repository. Just edit, push, and your changes are live. ...

  • CloudFlare

    CloudFlare

    Cloudflare speeds up and protects millions of websites, APIs, SaaS services, and other properties connected to the Internet. ...

  • Firebase

    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • Netlify CMS

    Netlify CMS

    It is built as a single-page React app. You can create custom-styled previews, UI widgets, and editor plugins or add backends to support different Git platform APIs. ...

  • Firebase Hosting

    Firebase Hosting

    It is production-grade web content hosting for developers. With a single command, you can quickly deploy web apps and serve both static and dynamic content to a global CDN (content delivery network). You can also pair it with Cloud Functions or Cloud Run to build and host microservices. ...

  • Contentful

    Contentful

    Contentful enables teams to unify content in a single hub, structure it for use in any digital channel, and integrate seamlessly with hundreds of other tools through open APIs and a leading app framework. ...

Netlify alternatives & related posts

Surge logo

Surge

83
151
56
Static web publishing for Front-End Developers
83
151
+ 1
56
PROS OF SURGE
  • 15
    Free plan
  • 12
    Simple
  • 11
    Free custom domain support
  • 10
    Deployment via command line
  • 3
    Smart about urls
  • 2
    Fast
  • 1
    Automatic urls based on filenames
  • 1
    404 status page based on 404.html
  • 1
    Free ssl
CONS OF SURGE
  • 1
    No free redirects

related Surge posts

Heroku logo

Heroku

18.2K
14K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
18.2K
14K
+ 1
3.2K
PROS OF HEROKU
  • 702
    Easy deployment
  • 459
    Free for side projects
  • 374
    Huge time-saver
  • 348
    Simple scaling
  • 261
    Low devops skills required
  • 190
    Easy setup
  • 174
    Add-ons for almost everything
  • 154
    Beginner friendly
  • 150
    Better for startups
  • 133
    Low learning curve
  • 48
    Postgres hosting
  • 41
    Easy to add collaborators
  • 30
    Faster development
  • 24
    Awesome documentation
  • 19
    Simple rollback
  • 19
    Focus on product, not deployment
  • 15
    Natural companion for rails development
  • 15
    Easy integration
  • 12
    Great customer support
  • 8
    GitHub integration
  • 6
    Painless & well documented
  • 6
    No-ops
  • 4
    Free
  • 3
    I love that they make it free to launch a side project
  • 3
    Great UI
  • 3
    Just works
  • 2
    PostgreSQL forking and following
  • 2
    MySQL extension
CONS OF HEROKU
  • 23
    Super expensive
  • 6
    No usable MySQL option
  • 6
    Not a whole lot of flexibility
  • 5
    Storage
  • 4
    Low performance on free tier

related Heroku posts

Russel Werner
Lead Engineer at StackShare · | 29 upvotes · 1.4M views

StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

#StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.6M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
GitHub Pages logo

GitHub Pages

13.3K
9.3K
1.1K
Public webpages freely hosted and easily published.
13.3K
9.3K
+ 1
1.1K
PROS OF GITHUB PAGES
  • 287
    Free
  • 216
    Right out of github
  • 185
    Quick to set up
  • 108
    Instant
  • 107
    Easy to learn
  • 58
    Great way of setting up your project's website
  • 47
    Widely used
  • 41
    Quick and easy
  • 37
    Great documentation
  • 4
    Super easy
  • 3
    Easy setup
  • 2
    Instant and fast Jekyll builds
  • 2
    Great customer support
  • 2
    Great integration
CONS OF GITHUB PAGES
  • 4
    Not possible to perform HTTP redirects
  • 3
    Supports only Jekyll
  • 3
    Limited Jekyll plugins
  • 1
    Jekyll is bloated

related GitHub Pages posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 2.6M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Dale Ross
Independent Contractor at Self Employed · | 22 upvotes · 890.2K views

I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

See more
CloudFlare logo

CloudFlare

64.3K
12.6K
1.7K
The Web Performance & Security Company.
64.3K
12.6K
+ 1
1.7K
PROS OF CLOUDFLARE
  • 418
    Easy setup, great cdn
  • 267
    Free ssl
  • 193
    Easy setup
  • 183
    Security
  • 173
    Ssl
  • 93
    Great cdn
  • 76
    Optimizer
  • 69
    Simple
  • 43
    Great UI
  • 26
    Great js cdn
  • 11
    Apps
  • 11
    AutoMinify
  • 11
    DNS Analytics
  • 9
    HTTP/2 Support
  • 8
    Easy
  • 8
    Rocket Loader
  • 7
    IPv6 "One Click"
  • 7
    Ipv6
  • 5
    Free GeoIP
  • 5
    Https://7r6.com/Cloudflarelinks
  • 5
    Amazing performance
  • 5
    SPDY
  • 5
    DNSSEC
  • 5
    API
  • 5
    Cheapest SSL
  • 4
    SSHFP
  • 4
    Http
  • 4
    Nice DNS
  • 4
    Fantastic CDN service
  • 4
    Free and reliable, Faster then anyone else
  • 4
    Asynchronous resource loading
  • 3
    Global Load Balancing
  • 3
    Easy Use
  • 3
    Performance
  • 2
    Ubuntu
  • 2
    Ip
  • 1
    Maker
CONS OF CLOUDFLARE
  • 1
    No support for SSHFP records

related CloudFlare posts

Johnny Bell
Software Engineer at Weedmaps · | 11 upvotes · 291.3K views

When I first built my portfolio I used GitHub for the source control and deployed directly to Netlify on a push to master. This was a perfect setup, I didn't need any knowledge about #DevOps or anything, it was all just done for me.

One of the issues I had with Netlify was I wanted to gzip my JavaScript files, I had this setup in my #Webpack file, however Netlify didn't offer an easy way to set this.

Over the weekend I decided I wanted to know more about how #DevOps worked so I decided to switch from Netlify to Amazon S3. Instead of creating any #Git Webhooks I decided to use Buddy for my pipeline and to run commands. Buddy is a fantastic tool, very easy to setup builds, copying the files to my Amazon S3 bucket, then running some #AWS console commands to set the content-encoding of the JavaScript files. - Buddy is also free if you only have a few pipelines, so I didn't need to pay anything 🤙🏻.

When I made these changes I also wanted to monitor my code, and make sure I was keeping up with the best practices so I implemented Code Climate to look over my code and tell me where there code smells, issues, and other issues I've been super happy with it so far, on the free tier so its also free.

I did plan on using Amazon CloudFront for my SSL and cacheing, however it was overly complex to setup and it costs money. So I decided to go with the free tier of CloudFlare and it is amazing, best choice I've made for caching / SSL in a long time.

See more
Johnny Bell
Software Engineer at Weedmaps · | 7 upvotes · 199.3K views

I recently moved my portfolio to Amazon S3 and I needed a new way to cache and SSL my site as Amazon S3 does not come with this right out of the box. I tried Amazon CloudFront as I was already on Amazon S3 I thought this would be super easy and straight forward to setup... It was not, I was unable to get this working even though I followed all the online steps and even reached out for help to Amazon.

I'd used CloudFlare in the past, and thought let me see if I can set up CloudFlare on an Amazon S3 bucket. The setup for this was so basic and easy... I had it setup with caching and SSL within 5 minutes, and it was 100% free.

See more
Firebase logo

Firebase

24.7K
20.7K
1.9K
The Realtime App Platform
24.7K
20.7K
+ 1
1.9K
PROS OF FIREBASE
  • 361
    Realtime backend made easy
  • 263
    Fast and responsive
  • 234
    Easy setup
  • 207
    Real-time
  • 186
    JSON
  • 127
    Free
  • 121
    Backed by google
  • 81
    Angular adaptor
  • 63
    Reliable
  • 36
    Great customer support
  • 26
    Great documentation
  • 23
    Real-time synchronization
  • 20
    Mobile friendly
  • 17
    Rapid prototyping
  • 12
    Great security
  • 11
    Automatic scaling
  • 10
    Freakingly awesome
  • 8
    Chat
  • 8
    Angularfire is an amazing addition!
  • 8
    Super fast development
  • 6
    Awesome next-gen backend
  • 6
    Ios adaptor
  • 5
    Built in user auth/oauth
  • 5
    Firebase hosting
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    It's made development super fast
  • 3
    Great
  • 3
    Brilliant for startups
  • 2
    Great all-round functionality
  • 2
    Low battery consumption
  • 2
    I can quickly create static web apps with no backend
  • 2
    The concurrent updates create a great experience
  • 2
    JS Offline and Sync suport
  • 1
    Faster workflow
  • 1
    Large
  • 1
    Serverless
  • 1
    .net
  • 1
    Free SSL
  • 1
    Good Free Limits
  • 1
    Push notification
  • 1
    Easy to use
  • 1
    Easy Reactjs integration
CONS OF FIREBASE
  • 28
    Can become expensive
  • 15
    Scalability is not infinite
  • 14
    No open source, you depend on external company
  • 9
    Not Flexible Enough
  • 5
    Cant filter queries
  • 3
    Very unstable server
  • 2
    Too many errors
  • 2
    No Relational Data

related Firebase posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 12 upvotes · 119.9K views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Netlify CMS logo

Netlify CMS

365
426
3
Open source content management for your Git workflow
365
426
+ 1
3
PROS OF NETLIFY CMS
  • 2
    Open source
  • 1
    Free
CONS OF NETLIFY CMS
  • 2
    No relations between items

related Netlify CMS posts

Firebase Hosting logo

Firebase Hosting

125
122
7
Production-grade web content hosting
125
122
+ 1
7
PROS OF FIREBASE HOSTING
  • 4
    Integration with firebase
  • 1
    Analytics
  • 1
    Super simple deploys
  • 1
    Easy deployment
CONS OF FIREBASE HOSTING
    Be the first to leave a con

    related Firebase Hosting posts

    Contentful logo

    Contentful

    646
    716
    61
    The content platform to build digital experiences at scale
    646
    716
    + 1
    61
    PROS OF CONTENTFUL
    • 26
      API-based cms
    • 14
      Much better than WordPress
    • 11
      Simple and customizable
    • 3
      Free for small projects
    • 3
      Images API
    • 1
      Super simple to integrate
    • 1
      Managed Service
    • 1
      Extensible dashboard UI
    • 1
      Tag Manager like UI
    CONS OF CONTENTFUL
    • 5
      No repeater Field
    • 4
      No spell check
    • 3
      Slow dashboard
    • 3
      No free plan
    • 2
      Limited content types
    • 2
      Enterprise targeted
    • 2
      Pricey
    • 1
      Not scalable

    related Contentful posts

    Shared insights
    on
    Contentful
    Firebase

    Hi. I am gonna build a simple app for a company to ease their work. The company is sending out pdf files to their users' email. The data is a health analysis with a lot of different health values. The app should be an MVP, where users can watch their data instead of opening a pdf file. The company should be able to fill in the data in either Firebase or Contentful database. Is Contentful or Firebase best for this solution? What is your opinion?

    See more
    Nash Nziramasanga
    Software Developer at Billow Software · | 2 upvotes · 7K views
    Shared insights
    on
    Sanity
    Contentful
    Next.js

    Im building a simple portfolio website using Next.js and all the content is static, what's the best between Contentful and Sanity.

    I really like the self-hosting and custom layout with sanity however I don't think time customizing is worth it anymore.

    Any thoughts

    See more