Alternatives to TestFlight logo

Alternatives to TestFlight

HockeyApp, TestFairy, Crashlytics, Fabric, and Buddybuild are the most popular alternatives and competitors to TestFlight.
1.1K
163

What is TestFlight and what are its top alternatives?

TestFlight is a beta testing platform owned by Apple that allows developers to distribute and test their iOS apps before release. Key features include easy app distribution, in-app feedback, crash reporting, and integration with Xcode. However, TestFlight is limited to iOS apps only and requires an Apple Developer account for full functionality.

  1. Firebase App Distribution: Firebase App Distribution is a mobile app distribution platform by Google that offers seamless distribution of iOS and Android apps. Key features include easy distribution to testers, crash reporting, and integration with Firebase services. Pros include support for both iOS and Android apps, while a con is limited support for in-app feedback compared to TestFlight.

  2. HockeyApp: HockeyApp, now integrated into Azure DevOps, is a distribution platform for iOS, Android, and Windows apps. Key features include app distribution, crash reporting, and user metrics. Pros include cross-platform support, but a con is that it is now part of Azure DevOps, so may have different pricing and integration.

  3. Installr: Installr is a platform for distributing ad-hoc builds of iOS apps for testing. Key features include easy distribution to testers, in-app analytics, and integration with popular development tools. Pros include simplicity and ease of use, but a con is limited support for Android apps.

  4. Visual Studio App Center: Visual Studio App Center by Microsoft is a platform for building, testing, and deploying iOS, Android, and Windows apps. Key features include app distribution, crash reporting, and continuous integration. Pros include multi-platform support, but a con is that it may be more complex compared to TestFlight for simple beta testing.

  5. Bitrise: Bitrise is a continuous integration and delivery platform for mobile apps, including support for iOS and Android. Key features include automated build processes, app distribution, and integrations with popular tools. Pros include robust CI/CD capabilities, while a con is that it may be more geared towards development teams rather than beta testers.

  6. Play Console: Play Console by Google is a platform for distributing Android apps to testers and production. Key features include app distribution, user feedback, and performance insights. Pros include seamless integration with Google services, but a con is that it is limited to Android apps.

  7. TestFairy: TestFairy is a platform for app distribution, monitoring, and user feedback for iOS and Android apps. Key features include video recordings of user sessions, crash reporting, and in-app feedback. Pros include comprehensive user feedback tools, while a con is that it may have a steeper learning curve compared to TestFlight.

  8. AWS Device Farm: AWS Device Farm is a mobile app testing service that allows for testing on real devices in the AWS cloud. Key features include automated testing, compatibility testing, and device logs. Pros include integration with other AWS services, but a con is that it may be more focused on testing rather than beta distribution.

  9. Ghost Inspector: Ghost Inspector is a platform for automated browser testing that can also be used for mobile app testing. Key features include test automation, visual regression testing, and test scheduling. Pros include cross-platform support, but a con is that it may not be as specialized for mobile app testing as other platforms.

  10. AWS Amplify: AWS Amplify is a development platform for building mobile and web apps with a focus on full-stack serverless development. Key features include app hosting, CI/CD, and analytics. Pros include robust development tools, but a con is that it may require more setup compared to TestFlight for beta testing.

Top Alternatives to TestFlight

  • HockeyApp
    HockeyApp

    HockeyApp is the best way to collect live crash reports, get feedback from your users, distribute your betas, and analyze your test coverage. ...

  • TestFairy
    TestFairy

    When testing apps in the crowd, you never know what exactly was done, and what went wrong on the client side. TestFairy shows you a video of the exact test that was done, including CPU, memory, GPS, network and a lot more. ...

  • Crashlytics
    Crashlytics

    Instead of just showing you the stack trace, Crashlytics performs deep analysis of each and every thread. We de-prioritize lines that don't matter while highlighting the interesting ones. This makes reading stack traces easier, faster, and far more useful! Crashlytics' intelligent grouping can take 50,000 crashes, distill them down to 20 unique issues, and then tell you which 3 are the most important to fix. ...

  • Fabric
    Fabric

    Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution. ...

  • Buddybuild
    Buddybuild

    Buddybuild ties together continuous integration, continuous delivery and an iterative feedback solution into a single, seamless platform. ...

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

  • Git
    Git

    Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. ...

  • GitHub
    GitHub

    GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together. ...

TestFlight alternatives & related posts

HockeyApp logo

HockeyApp

168
158
38
Manage your betas and collect live crash reports for iOS, Android, Windows Phone, and OS X apps.
168
158
+ 1
38
PROS OF HOCKEYAPP
  • 17
    Crash analytics
  • 11
    Cross-platform
  • 5
    Mobile application distribution
  • 2
    JIRA Integration
  • 2
    Open source
  • 1
    GitHub Integration
CONS OF HOCKEYAPP
    Be the first to leave a con

    related HockeyApp posts

    TestFairy logo

    TestFairy

    41
    76
    29
    Painless Beta Testing
    41
    76
    + 1
    29
    PROS OF TESTFAIRY
    • 8
      Get video rec of the user on your app
    • 4
      Landing Page
    • 4
      Better design
    • 3
      JIRA Integration
    • 2
      Cross-platform
    • 2
      Supports Enterprise IPA's (TestFlight doesn't/didn't)
    • 2
      GitHub Integration
    • 1
      Application full Log information
    • 1
      App Distribution
    • 1
      Single Sign-On
    • 1
      In-App Feedback
    CONS OF TESTFAIRY
      Be the first to leave a con

      related TestFairy posts

      Crashlytics logo

      Crashlytics

      1K
      614
      340
      The world's most powerful, yet lightest weight crash reporting solution. Free for everybody.
      1K
      614
      + 1
      340
      PROS OF CRASHLYTICS
      • 78
        Crash tracking
      • 56
        Mobile exception tracking
      • 53
        Free
      • 37
        Easy deployment
      • 25
        Ios
      • 15
        Great ui
      • 11
        Great reports
      • 10
        Android
      • 8
        Advanced Logging
      • 7
        Monitor Tester Lifecycle
      • 3
        Mac APP and IDE Plugins
      • 3
        Great User Experience
      • 3
        In Real-Time
      • 3
        iOS SDK
      • 3
        Security
      • 3
        Android SDK
      • 2
        The UI is simple and it just works
      • 2
        Best UI
      • 2
        Light
      • 2
        Real-time
      • 2
        Seamless
      • 2
        Painless App Distribution
      • 2
        Crash Reporting
      • 2
        Beta distribution
      • 2
        Mobile Analytics
      • 2
        Deep Workflow Integration
      • 1
        IOS QA Deploy and tracking
      • 1
        Easy iOS Integration
      CONS OF CRASHLYTICS
        Be the first to leave a con

        related Crashlytics posts

        Алексей Нестерчук
        Shared insights
        on
        AWS ConfigAWS ConfigCrashlyticsCrashlytics

        From firebase Crashlytics, everything is simple, we install SDK and configs, and then we can see all the crashes. With AWS, it is not clear to me which service to use for the same purpose as configuring it. Correctly I understand that for automatic sending of all crashes, you need to use AWS Config?

        See more
        Fabric logo

        Fabric

        451
        307
        75
        Simple, Pythonic remote execution and deployment
        451
        307
        + 1
        75
        PROS OF FABRIC
        • 23
          Python
        • 21
          Simple
        • 5
          Low learning curve, from bash script to Python power
        • 5
          Installation feedback for Twitter App Cards
        • 3
          Easy on maintainance
        • 3
          Single config file
        • 3
          Installation? pip install fabric... Boom
        • 3
          Easy to add any type of job
        • 3
          Agentless
        • 2
          Easily automate any set system automation
        • 1
          Flexible
        • 1
          Crash Analytics
        • 1
          Backward compatibility
        • 1
          Remote sudo execution
        CONS OF FABRIC
          Be the first to leave a con

          related Fabric posts

          Buddybuild logo

          Buddybuild

          47
          61
          41
          A continuous integration, continuous deployment and user feedback platform for iOS and Android development teams
          47
          61
          + 1
          41
          PROS OF BUDDYBUILD
          • 12
            Easy setup
          • 8
            Beta testing
          • 8
            Crazy easy
          • 7
            GitHub Integration
          • 3
            Crash reporting
          • 2
            Cause it's just great
          • 1
            Good support team
          CONS OF BUDDYBUILD
            Be the first to leave a con

            related Buddybuild posts

            Firebase logo

            Firebase

            41K
            35.1K
            2K
            The Realtime App Platform
            41K
            35.1K
            + 1
            2K
            PROS OF FIREBASE
            • 371
              Realtime backend made easy
            • 270
              Fast and responsive
            • 242
              Easy setup
            • 215
              Real-time
            • 191
              JSON
            • 134
              Free
            • 128
              Backed by google
            • 83
              Angular adaptor
            • 68
              Reliable
            • 36
              Great customer support
            • 32
              Great documentation
            • 25
              Real-time synchronization
            • 21
              Mobile friendly
            • 19
              Rapid prototyping
            • 14
              Great security
            • 12
              Automatic scaling
            • 11
              Freakingly awesome
            • 8
              Super fast development
            • 8
              Angularfire is an amazing addition!
            • 8
              Chat
            • 6
              Firebase hosting
            • 6
              Built in user auth/oauth
            • 6
              Awesome next-gen backend
            • 6
              Ios adaptor
            • 4
              Speed of light
            • 4
              Very easy to use
            • 3
              Great
            • 3
              It's made development super fast
            • 3
              Brilliant for startups
            • 2
              Free hosting
            • 2
              Cloud functions
            • 2
              JS Offline and Sync suport
            • 2
              Low battery consumption
            • 2
              .net
            • 2
              The concurrent updates create a great experience
            • 2
              Push notification
            • 2
              I can quickly create static web apps with no backend
            • 2
              Great all-round functionality
            • 2
              Free authentication solution
            • 1
              Easy Reactjs integration
            • 1
              Google's support
            • 1
              Free SSL
            • 1
              CDN & cache out of the box
            • 1
              Easy to use
            • 1
              Large
            • 1
              Faster workflow
            • 1
              Serverless
            • 1
              Good Free Limits
            • 1
              Simple and easy
            CONS OF FIREBASE
            • 31
              Can become expensive
            • 16
              No open source, you depend on external company
            • 15
              Scalability is not infinite
            • 9
              Not Flexible Enough
            • 7
              Cant filter queries
            • 3
              Very unstable server
            • 3
              No Relational Data
            • 2
              Too many errors
            • 2
              No offline sync

            related Firebase posts

            Stephen Gheysens
            Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.8M 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
            Eugene Cheah

            For inboxkitten.com, an opensource disposable email service;

            We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.

            If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...

            1. <5ms CPU time limit
            2. Incompatible with express.js
            3. one script limitation per domain

            Limitations our workload is able to conform with (YMMV)

            For hosting of static files, we migrated from Firebase to CommonsHost

            More details on the trade-off in between both serverless providers is in the article

            See more
            Git logo

            Git

            297.1K
            178.4K
            6.6K
            Fast, scalable, distributed revision control system
            297.1K
            178.4K
            + 1
            6.6K
            PROS OF GIT
            • 1.4K
              Distributed version control system
            • 1.1K
              Efficient branching and merging
            • 959
              Fast
            • 845
              Open source
            • 726
              Better than svn
            • 368
              Great command-line application
            • 306
              Simple
            • 291
              Free
            • 232
              Easy to use
            • 222
              Does not require server
            • 27
              Distributed
            • 22
              Small & Fast
            • 18
              Feature based workflow
            • 15
              Staging Area
            • 13
              Most wide-spread VSC
            • 11
              Role-based codelines
            • 11
              Disposable Experimentation
            • 7
              Frictionless Context Switching
            • 6
              Data Assurance
            • 5
              Efficient
            • 4
              Just awesome
            • 3
              Github integration
            • 3
              Easy branching and merging
            • 2
              Compatible
            • 2
              Flexible
            • 2
              Possible to lose history and commits
            • 1
              Rebase supported natively; reflog; access to plumbing
            • 1
              Light
            • 1
              Team Integration
            • 1
              Fast, scalable, distributed revision control system
            • 1
              Easy
            • 1
              Flexible, easy, Safe, and fast
            • 1
              CLI is great, but the GUI tools are awesome
            • 1
              It's what you do
            • 0
              Phinx
            CONS OF GIT
            • 16
              Hard to learn
            • 11
              Inconsistent command line interface
            • 9
              Easy to lose uncommitted work
            • 8
              Worst documentation ever possibly made
            • 5
              Awful merge handling
            • 3
              Unexistent preventive security flows
            • 3
              Rebase hell
            • 2
              Ironically even die-hard supporters screw up badly
            • 2
              When --force is disabled, cannot rebase
            • 1
              Doesn't scale for big data

            related Git posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 30 upvotes · 11.1M 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 · 9.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
            GitHub logo

            GitHub

            285.4K
            249.3K
            10.3K
            Powerful collaboration, review, and code management for open source and private development projects
            285.4K
            249.3K
            + 1
            10.3K
            PROS OF GITHUB
            • 1.8K
              Open source friendly
            • 1.5K
              Easy source control
            • 1.3K
              Nice UI
            • 1.1K
              Great for team collaboration
            • 867
              Easy setup
            • 504
              Issue tracker
            • 487
              Great community
            • 483
              Remote team collaboration
            • 449
              Great way to share
            • 442
              Pull request and features planning
            • 147
              Just works
            • 132
              Integrated in many tools
            • 122
              Free Public Repos
            • 116
              Github Gists
            • 113
              Github pages
            • 83
              Easy to find repos
            • 62
              Open source
            • 60
              Easy to find projects
            • 60
              It's free
            • 56
              Network effect
            • 49
              Extensive API
            • 43
              Organizations
            • 42
              Branching
            • 34
              Developer Profiles
            • 32
              Git Powered Wikis
            • 30
              Great for collaboration
            • 24
              It's fun
            • 23
              Clean interface and good integrations
            • 22
              Community SDK involvement
            • 20
              Learn from others source code
            • 16
              Because: Git
            • 14
              It integrates directly with Azure
            • 10
              Standard in Open Source collab
            • 10
              Newsfeed
            • 8
              Fast
            • 8
              Beautiful user experience
            • 8
              It integrates directly with Hipchat
            • 7
              Easy to discover new code libraries
            • 6
              Smooth integration
            • 6
              Integrations
            • 6
              Graphs
            • 6
              Nice API
            • 6
              It's awesome
            • 6
              Cloud SCM
            • 5
              Quick Onboarding
            • 5
              Remarkable uptime
            • 5
              CI Integration
            • 5
              Reliable
            • 5
              Hands down best online Git service available
            • 4
              Version Control
            • 4
              Unlimited Public Repos at no cost
            • 4
              Simple but powerful
            • 4
              Loved by developers
            • 4
              Free HTML hosting
            • 4
              Uses GIT
            • 4
              Security options
            • 4
              Easy to use and collaborate with others
            • 3
              Easy deployment via SSH
            • 3
              Ci
            • 3
              IAM
            • 3
              Nice to use
            • 2
              Easy and efficient maintainance of the projects
            • 2
              Beautiful
            • 2
              Self Hosted
            • 2
              Issues tracker
            • 2
              Easy source control and everything is backed up
            • 2
              Never dethroned
            • 2
              All in one development service
            • 2
              Good tools support
            • 2
              Free HTML hostings
            • 2
              IAM integration
            • 2
              Very Easy to Use
            • 2
              Easy to use
            • 2
              Leads the copycats
            • 2
              Free private repos
            • 1
              Profound
            • 1
              Dasf
            CONS OF GITHUB
            • 55
              Owned by micrcosoft
            • 38
              Expensive for lone developers that want private repos
            • 15
              Relatively slow product/feature release cadence
            • 10
              API scoping could be better
            • 9
              Only 3 collaborators for private repos
            • 4
              Limited featureset for issue management
            • 3
              Does not have a graph for showing history like git lens
            • 2
              GitHub Packages does not support SNAPSHOT versions
            • 1
              No multilingual interface
            • 1
              Takes a long time to commit
            • 1
              Expensive

            related GitHub posts

            Johnny Bell

            I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

            I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

            I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

            Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

            Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

            With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

            If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

            See more

            Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

            Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

            Check Out My Architecture: CLICK ME

            Check out the GitHub repo attached

            See more