Alternatives to Laravel Forge logo

Alternatives to Laravel Forge

Envoyer, Runcloud, ServerPilot, Vapor, and Docker are the most popular alternatives and competitors to Laravel Forge.
186
214
+ 1
4

What is Laravel Forge and what are its top alternatives?

Provision, host, and deploy PHP applications on AWS, DigitalOcean, and Linode.
Laravel Forge is a tool in the Deployment as a Service category of a tech stack.
Laravel Forge is an open source tool with GitHub stars and GitHub forks. Here’s a link to Laravel Forge's open source repository on GitHub

Top Alternatives to Laravel Forge

  • Envoyer

    Envoyer

    Envoyer deploys your PHP applications with zero downtime. Just push your code, and let Envoyer deliver your application to one or many servers without interrupting a single customer. In this series, we'll discuss each feature of Envoyer, demonstrating how to use them with a sample project. ...

  • Runcloud

    Runcloud

    SaaS based PHP cloud server control panel. Support Digital Ocean, Linode, AWS, Vultr, Azure and other custom VPS. GIT deployment webhook and easiest control panel to manage Laravel, Cake, Symphony or WordPress. ...

  • ServerPilot

    ServerPilot

    It is a SaaS platform for hosting PHP websites on Ubuntu servers. You can think of it as a modern, centralized hosting control panel. Manage all servers and sites through a single control panel or automate using our API. ...

  • Vapor

    Vapor

    Vapor is the first true web framework for Swift. It provides a beautifully expressive foundation for your app without tying you to any single server implementation. ...

  • Docker

    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • 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. ...

  • DigitalOcean

    DigitalOcean

    We take the complexities out of cloud hosting by offering blazing fast, on-demand SSD cloud servers, straightforward pricing, a simple API, and an easy-to-use control panel. ...

  • AWS CodeDeploy

    AWS CodeDeploy

    AWS CodeDeploy is a service that automates code deployments to Amazon EC2 instances. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during deployment, and handles the complexity of updating your applications. ...

Laravel Forge alternatives & related posts

Envoyer logo

Envoyer

55
65
3
A brand new way to deploy PHP and Laravel applications with zero downtime
55
65
+ 1
3
PROS OF ENVOYER
  • 3
    Easy to use
CONS OF ENVOYER
    Be the first to leave a con

    related Envoyer posts

    Runcloud logo

    Runcloud

    19
    57
    0
    PHP web application & server management panel
    19
    57
    + 1
    0
    PROS OF RUNCLOUD
      Be the first to leave a pro
      CONS OF RUNCLOUD
        Be the first to leave a con

        related Runcloud posts

        ServerPilot logo

        ServerPilot

        19
        29
        0
        The best way to run WordPress and PHP sites
        19
        29
        + 1
        0
        PROS OF SERVERPILOT
          Be the first to leave a pro
          CONS OF SERVERPILOT
            Be the first to leave a con

            related ServerPilot posts

            Vapor logo

            Vapor

            90
            158
            58
            A type-safe web framework for Swift
            90
            158
            + 1
            58
            PROS OF VAPOR
            • 12
              Fast
            • 10
              Swift
            • 9
              Type-safe
            • 5
              Great for apis
            • 5
              Readable
            • 5
              Good Abstraction
            • 5
              Asynchronous
            • 4
              Compiled to machine code
            • 3
              Maintainable
            CONS OF VAPOR
            • 1
              Server side swift is still in its infancy
            • 1
              Not as much support available.

            related Vapor posts

            Docker logo

            Docker

            115.9K
            92.3K
            3.8K
            Enterprise Container Platform for High-Velocity Innovation.
            115.9K
            92.3K
            + 1
            3.8K
            PROS OF DOCKER
            • 821
              Rapid integration and build up
            • 688
              Isolation
            • 517
              Open source
            • 505
              Testa­bil­i­ty and re­pro­ducibil­i­ty
            • 459
              Lightweight
            • 217
              Standardization
            • 182
              Scalable
            • 105
              Upgrading / down­grad­ing / ap­pli­ca­tion versions
            • 86
              Security
            • 84
              Private paas environments
            • 33
              Portability
            • 25
              Limit resource usage
            • 15
              I love the way docker has changed virtualization
            • 15
              Game changer
            • 12
              Fast
            • 11
              Concurrency
            • 7
              Docker's Compose tools
            • 4
              Fast and Portable
            • 4
              Easy setup
            • 4
              Because its fun
            • 3
              Makes shipping to production very simple
            • 2
              It's dope
            • 1
              Highly useful
            • 1
              MacOS support FAKE
            • 1
              Its cool
            • 1
              Docker hub for the FTW
            • 1
              Very easy to setup integrate and build
            • 1
              Package the environment with the application
            • 1
              Does a nice job hogging memory
            • 1
              Open source and highly configurable
            • 1
              Simplicity, isolation, resource effective
            CONS OF DOCKER
            • 7
              New versions == broken features
            • 5
              Documentation not always in sync
            • 5
              Unreliable networking
            • 3
              Moves quickly
            • 2
              Not Secure

            related Docker posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M 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
            Tymoteusz Paul
            Devops guy at X20X Development LTD · | 23 upvotes · 4.7M views

            Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

            It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

            I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

            We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

            If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

            The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

            Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

            See more
            Heroku logo

            Heroku

            20.1K
            15.7K
            3.2K
            Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
            20.1K
            15.7K
            + 1
            3.2K
            PROS OF HEROKU
            • 704
              Easy deployment
            • 460
              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
              Focus on product, not deployment
            • 19
              Simple rollback
            • 15
              Natural companion for rails development
            • 15
              Easy integration
            • 12
              Great customer support
            • 8
              GitHub integration
            • 6
              No-ops
            • 6
              Painless & well documented
            • 4
              Free
            • 4
              I love that they make it free to launch a side project
            • 3
              Just works
            • 3
              Great UI
            • 2
              PostgreSQL forking and following
            • 2
              MySQL extension
            • 1
              Able to host stuff good like Discord Bot
            • 0
              Sec
            • 0
              Security
            CONS OF HEROKU
            • 23
              Super expensive
            • 6
              Not a whole lot of flexibility
            • 5
              No usable MySQL option
            • 5
              Storage
            • 4
              Low performance on free tier
            • 1
              24/7 support is $1,000 per month

            related Heroku posts

            Russel Werner
            Lead Engineer at StackShare · | 30 upvotes · 1.5M 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 · 3.3M 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
            DigitalOcean logo

            DigitalOcean

            14.1K
            10K
            2.6K
            Deploy an SSD cloud server in less than 55 seconds with a dedicated IP and root access.
            14.1K
            10K
            + 1
            2.6K
            PROS OF DIGITALOCEAN
            • 559
              Great value for money
            • 363
              Simple dashboard
            • 360
              Good pricing
            • 300
              Ssds
            • 248
              Nice ui
            • 192
              Easy configuration
            • 155
              Great documentation
            • 137
              Ssh access
            • 134
              Great community
            • 24
              Ubuntu
            • 13
              Docker
            • 12
              IPv6 support
            • 10
              Private networking
            • 7
              99.99% uptime SLA
            • 7
              Great tutorials
            • 7
              Simple API
            • 6
              55 Second Provisioning
            • 5
              One Click Applications
            • 4
              CoreOS
            • 4
              Dokku
            • 4
              Node.js
            • 4
              Debian
            • 4
              LAMP
            • 3
              Ghost
            • 3
              1Gb/sec Servers
            • 3
              Simple Control Panel
            • 3
              LEMP
            • 3
              Word Press
            • 2
              Runs CoreOS
            • 2
              Mean
            • 2
              Speed
            • 2
              GitLab
            • 2
              Django
            • 2
              Quick and no nonsense service
            • 2
              Good Tutorials
            • 2
              Ruby on Rails
            • 2
              Hex Core machines with dedicated ECC Ram and RAID SSD s
            • 1
              Spaces
            • 1
              My go to server provider
            • 1
              Ease and simplicity
            • 1
              Nice
            • 1
              Find it superfitting with my requirements (SSD, ssh.
            • 1
              Easy Setup
            • 1
              Transfer Globally
            • 1
              Drupal
            • 1
              FreeBSD Amp
            • 1
              Amazing Hardware
            • 1
              Magento
            • 1
              KVM Virtualization
            • 1
              ownCloud
            • 1
              RedMine
            • 1
              CentOS
            • 1
              Fedora
            • 1
              FreeBSD
            • 1
              Cheap
            • 1
              Static IP
            • 1
              It's the easiest to get started for small projects
            • 1
              Automatic Backup
            • 1
              Great support
            • 1
              Quick and easy to set up
            • 1
              Servers on demand - literally
            • 1
              Reliability
            • 0
              Variety of services
            • 0
              Managed Kubernetes
            CONS OF DIGITALOCEAN
            • 3
              Pricing
            • 3
              No live support chat

            related DigitalOcean posts

            Hello, I'm currently writing an e-commerce website with Laravel and Laravel Nova (as an admin panel). I want to start deploying the app and created a DigitalOcean account. After some searches about the deployment process, I saw that the setup via DigitalOcean (using Droplets) isn't very easy for beginners. Now I'm not sure how to deploy my app. I am in between Laravel Forge and DigitalOcean (?Apps Platform or Droplets?). I've read that Heroku and Laravel Vapor are a bit expensive. That's why I didn't consider them yet. I'd be happy to read your opinions on that topic!

            See more

            Hi, I'm a beginner at using MySQL, I currently deployed my crud app on Heroku using the ClearDB add-on. I didn't see that coming, but the increased value of the primary key instead of being 1 is set to 10, and I cannot find a way to change it. Now I`m considering switching and deploying the full app and MySql to DigitalOcean any advice on that? Will I get the same issue? Thanks in advance!

            See more
            AWS CodeDeploy logo

            AWS CodeDeploy

            350
            502
            38
            Coordinate application deployments to Amazon EC2 instances
            350
            502
            + 1
            38
            PROS OF AWS CODEDEPLOY
            • 17
              Automates code deployments
            • 9
              Backed by Amazon
            • 7
              Adds autoscaling lifecycle hooks
            • 5
              Git integration
            CONS OF AWS CODEDEPLOY
              Be the first to leave a con

              related AWS CodeDeploy posts

              Chris McFadden
              VP, Engineering at SparkPost · | 9 upvotes · 133.1K views

              The recent move of our CI/CD tooling to AWS CodeBuild / AWS CodeDeploy (with GitHub ) as well as moving to Amazon EC2 Container Service / AWS Lambda for our deployment architecture for most of our services has helped us significantly reduce our deployment times while improving both feature velocity and overall reliability. In one extreme case, we got one service down from 90 minutes to a very reasonable 15 minutes. Container-based build and deployments have made so many things simpler and easier and the integration between the tools has been helpful. There is still some work to do on our service mesh & API proxy approach to further simplify our environment.

              See more
              Sathish Raju
              Founder/CTO at Kloudio · | 5 upvotes · 65.9K views

              At Kloud.io we use Node.js for our backend Microservices and Angular 2 for the frontend. We also use React for a couple of our internal applications. Writing services in Node.js in TypeScript improved developer productivity and we could capture bugs way before they can occur in the production. The use of Angular 2 in our production environment reduced the time to release any new features. At the same time, we are also exploring React by using it in our internal tools. So far we enjoyed what React has to offer. We are an enterprise SAAS product and also offer an on-premise or hybrid cloud version of #kloudio. We heavily use Docker for shipping our on-premise version. We also use Docker internally for automated testing. Using Docker reduced the install time errors in customer environments. Our cloud version is deployed in #AWS. We use AWS CodePipeline and AWS CodeDeploy for our CI/CD. We also use AWS Lambda for automation jobs.

              See more