Alternatives to JHipster logo

Alternatives to JHipster

Spring Boot, Grails, Django, Yeoman, and CUBA Platform are the most popular alternatives and competitors to JHipster.
180
280
+ 1
0

What is JHipster and what are its top alternatives?

It is a free and open-source application generator used to quickly develop modern web applications and Microservices using Spring Boot + Angular / React / Vue.
JHipster is a tool in the Frameworks (Full Stack) category of a tech stack.
JHipster is an open source tool with 19.5K GitHub stars and 3.8K GitHub forks. Here’s a link to JHipster's open source repository on GitHub

Top Alternatives to JHipster

  • Spring Boot
    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

  • Grails
    Grails

    Grails is a framework used to build web applications with the Groovy programming language. The core framework is very extensible and there are numerous plugins available that provide easy integration of add-on features. ...

  • Django
    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • Yeoman
    Yeoman

    Yeoman is a robust and opinionated set of tools, libraries, and a workflow that can help developers quickly build beautiful, compelling web apps. It is comprised of yo - a scaffolding tool using our generator system, grunt - a task runner for your build process and bower for dependency management. ...

  • CUBA Platform
    CUBA Platform

    It is a high-level open-source Java web framework for the rapid development of enterprise applications. The platform abstracts developers from underlying technologies so they can focus on the business tasks, whilst retaining full flexibility by providing unrestricted access to low-level code. Applications are developed in Java, with the user interface declared in XML. A rich set of features covers most typical project requirements and development tools reduce boilerplate code and facilitate truly rapid development. ...

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • ASP.NET
    ASP.NET

    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

JHipster alternatives & related posts

Spring Boot logo

Spring Boot

19.2K
17.1K
923
Create Spring-powered, production-grade applications and services with absolute minimum fuss
19.2K
17.1K
+ 1
923
PROS OF SPRING BOOT
  • 136
    Powerful and handy
  • 128
    Easy setup
  • 119
    Java
  • 87
    Spring
  • 82
    Fast
  • 43
    Extensible
  • 34
    Lots of "off the shelf" functionalities
  • 29
    Cloud Solid
  • 23
    Caches well
  • 21
    Many receipes around for obscure features
  • 21
    Productive
  • 20
    Modular
  • 20
    Integrations with most other Java frameworks
  • 19
    Spring ecosystem is great
  • 18
    Auto-configuration
  • 18
    Fast Performance With Microservices
  • 16
    Community
  • 14
    Easy setup, Community Support, Solid for ERP apps
  • 13
    One-stop shop
  • 12
    Cross-platform
  • 12
    Easy to parallelize
  • 11
    Easy setup, good for build erp systems, well documented
  • 11
    Powerful 3rd party libraries and frameworks
  • 10
    Easy setup, Git Integration
  • 3
    It's so easier to start a project on spring
  • 3
    Kotlin
CONS OF SPRING BOOT
  • 20
    Heavy weight
  • 17
    Annotation ceremony
  • 10
    Many config files needed
  • 8
    Java
  • 5
    Reactive
  • 4
    Excellent tools for cloud hosting, since 5.x

related Spring Boot posts

Praveen Mooli
Engineering Manager at Taylor and Francis · | 17 upvotes · 2.2M views

We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

To build #Webapps we decided to use Angular 2 with RxJS

#Devops - GitHub , Travis CI , Terraform , Docker , Serverless

See more

Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

See more
Grails logo

Grails

364
336
328
An Open Source, full stack, web application framework for the JVM
364
336
+ 1
328
PROS OF GRAILS
  • 55
    Groovy
  • 39
    Jvm
  • 38
    Rapid development
  • 37
    Gorm
  • 29
    Web framework
  • 24
    Open source
  • 21
    Plugins
  • 17
    Extensible
  • 16
    Easy
  • 14
    Dynamic
  • 6
    Clean architecture (Dependency Injection)
  • 6
    Gradle
  • 5
    Clear what everything does, lots of options
  • 4
    RAD
  • 4
    Great documentation
  • 4
    Agile
  • 3
    Android
  • 3
    Spring
  • 2
    Easy setup
  • 1
    Java web apps with steroid
CONS OF GRAILS
  • 3
    Frequent breaking changes
  • 2
    Undocumented features

related Grails posts

Alex A

Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?

See more

Presently, a web-based ERP is developed in Groovy on Grails. Now the ERP is getting revamped with more functionalities. Is it advisable to continue with the same software and framework or try something new especially Node.js over ExpressJS?

See more
Django logo

Django

29.5K
26.3K
3.9K
The Web framework for perfectionists with deadlines
29.5K
26.3K
+ 1
3.9K
PROS OF DJANGO
  • 641
    Rapid development
  • 473
    Open source
  • 406
    Great community
  • 357
    Easy to learn
  • 266
    Mvc
  • 217
    Beautiful code
  • 212
    Elegant
  • 196
    Free
  • 194
    Great packages
  • 182
    Great libraries
  • 71
    Restful
  • 67
    Powerful
  • 67
    Comes with auth and crud admin panel
  • 64
    Great documentation
  • 61
    Great for web
  • 48
    Python
  • 38
    Great orm
  • 36
    Great for api
  • 27
    All included
  • 22
    Web Apps
  • 22
    Fast
  • 19
    Used by top startups
  • 17
    Clean
  • 16
    Easy setup
  • 16
    Sexy
  • 13
    Convention over configuration
  • 12
    ORM
  • 9
    Allows for very rapid development with great libraries
  • 9
    The Django community
  • 7
    Great MVC and templating engine
  • 7
    King of backend world
  • 7
    Its elegant and practical
  • 6
    Mvt
  • 6
    Full stack
  • 6
    Fast prototyping
  • 6
    Have not found anything that it can't do
  • 6
    Cross-Platform
  • 5
    Batteries included
  • 5
    Very quick to get something up and running
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Easy to develop end to end AI Models
  • 4
    Python community
  • 4
    Great peformance
  • 4
    Easy
  • 4
    Easy to use
  • 4
    Modular
  • 4
    Many libraries
  • 3
    Full-Text Search
  • 3
    Map
  • 3
    Zero code burden to change databases
  • 3
    Scaffold
  • 3
    Just the right level of abstraction
  • 2
    Easy to change database manager
  • 1
    Node js
  • 0
    Asdasd
  • 0
    Rails
  • 0
    Aaaa
  • 0
    Fastapi
CONS OF DJANGO
  • 25
    Underpowered templating
  • 21
    Autoreload restarts whole server
  • 20
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 7
    Configuration hell
  • 7
    Admin
  • 5
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Not typed
  • 3
    Python
  • 2
    Overwhelming folder structure
  • 2
    InEffective Multithreading

related Django posts

Dmitry Mukhin

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
Yeoman logo

Yeoman

1.6K
1.2K
396
A set of tools for automating development workflow
1.6K
1.2K
+ 1
396
PROS OF YEOMAN
  • 121
    Lightning-fast scaffolding
  • 83
    Automation
  • 78
    Great build process
  • 57
    Open source
  • 49
    Yo
  • 8
    Unit Testing
CONS OF YEOMAN
  • 1
    Even harder to debug than Javascript

related Yeoman posts

CUBA Platform logo

CUBA Platform

10
21
3
A full stack Java framework and components for business applications
10
21
+ 1
3
PROS OF CUBA PLATFORM
  • 1
    Lots out of the box
  • 1
    Java
  • 1
    Component based
CONS OF CUBA PLATFORM
    Be the first to leave a con

    related CUBA Platform posts

    Node.js logo

    Node.js

    140.5K
    117.7K
    8.4K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    140.5K
    117.7K
    + 1
    8.4K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 798
      Open source
    • 484
      Great for apis
    • 474
      Asynchronous
    • 420
      Great community
    • 390
      Great for realtime apps
    • 295
      Great for command line utilities
    • 81
      Node Modules
    • 80
      Websockets
    • 67
      Uber Simple
    • 58
      Great modularity
    • 56
      Allows us to reuse code in the frontend
    • 41
      Easy to start
    • 35
      Great for Data Streaming
    • 31
      Realtime
    • 27
      Awesome
    • 24
      Non blocking IO
    • 17
      Can be used as a proxy
    • 16
      High performance, open source, scalable
    • 15
      Non-blocking and modular
    • 14
      Easy and Fun
    • 13
      Easy and powerful
    • 12
      Future of BackEnd
    • 12
      Same lang as AngularJS
    • 11
      Fullstack
    • 10
      Fast
    • 9
      Cross platform
    • 9
      Scalability
    • 8
      Simple
    • 7
      Mean Stack
    • 6
      Great for webapps
    • 6
      Easy concurrency
    • 5
      Fast, simple code and async
    • 5
      Friendly
    • 5
      Typescript
    • 5
      React
    • 4
      Easy to use and fast and goes well with JSONdb's
    • 4
      Scalable
    • 4
      Great speed
    • 4
      Control everything
    • 4
      Fast development
    • 4
      Its amazingly fast and scalable
    • 3
      Isomorphic coolness
    • 3
      It's fast
    • 3
      Easy to use
    • 2
      Easy to learn
    • 2
      Easy
    • 2
      Javascript2
    • 2
      Great community
    • 2
      Not Python
    • 2
      Sooper easy for the Backend connectivity
    • 2
      TypeScript Support
    • 2
      Scales, fast, simple, great community, npm, express
    • 2
      One language, end-to-end
    • 2
      Less boilerplate code
    • 2
      Blazing fast
    • 2
      Performant and fast prototyping
    • 1
      Lovely
    • 1
      Event Driven
    • 1
      Npm i ape-updating
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 42
      New framework every day
    • 37
      Lots of terrible examples on the internet
    • 29
      Asynchronous programming is the worst
    • 23
      Callback
    • 18
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      Dependency hell
    • 10
      Low computational power
    • 7
      Can block whole server easily
    • 7
      Very very Slow
    • 6
      Callback functions may not fire on expected sequence
    • 3
      Unneeded over complication
    • 3
      Unstable
    • 3
      Breaking updates
    • 1
      No standard approach
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 1.9M views

    When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

    So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

    React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

    Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.8M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    ASP.NET logo

    ASP.NET

    22.9K
    8K
    18
    An open source web framework for building modern web apps and services with .NET
    22.9K
    8K
    + 1
    18
    PROS OF ASP.NET
    • 13
      Great mvc
    • 5
      Easy to learn
    CONS OF ASP.NET
    • 1
      Not highly flexible for advance Developers
    • 1
      Entity framework is very slow

    related ASP.NET posts

    Greg Neumann
    Indie, Solo, Developer · | 8 upvotes · 905K views

    Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

    This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

    But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

    I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

    Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

    See more

    Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

    We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

    We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

    ASP.NET / Node.js / Laravel. ......?

    Please guide us

    See more
    Laravel logo

    Laravel

    22.2K
    18.1K
    3.6K
    A PHP Framework For Web Artisans
    22.2K
    18.1K
    + 1
    3.6K
    PROS OF LARAVEL
    • 526
      Clean architecture
    • 379
      Growing community
    • 354
      Composer friendly
    • 328
      Open source
    • 307
      The only framework to consider for php
    • 208
      Mvc
    • 203
      Quickly develop
    • 161
      Dependency injection
    • 150
      Application architecture
    • 138
      Embraces good community packages
    • 67
      Write less, do more
    • 62
      Orm (eloquent)
    • 60
      Restful routing
    • 51
      Database migrations & seeds
    • 50
      Artisan scaffolding and migrations
    • 36
      Great documentation
    • 36
      Awesome
    • 27
      Awsome, Powerfull, Fast and Rapid
    • 25
      Build Apps faster, easier and better
    • 25
      Promotes elegant coding
    • 22
      Eloquent ORM
    • 22
      Modern PHP
    • 22
      JSON friendly
    • 22
      Easy to learn, scalability
    • 21
      Most easy for me
    • 20
      Beautiful
    • 20
      Test-Driven
    • 20
      Blade Template
    • 14
      Security
    • 13
      Based on SOLID
    • 12
      Clean Documentation
    • 12
      Cool
    • 11
      Simple
    • 11
      Convention over Configuration
    • 11
      Easy to attach Middleware
    • 10
      Easy Request Validatin
    • 9
      Fast
    • 9
      Simpler
    • 9
      Easy to use
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Its just wow
    • 8
      Friendly API
    • 8
      Get going quickly straight out of the box. BYOKDM
    • 7
      Simplistic , easy and faster
    • 7
      Super easy and powerful
    • 7
      Less dependencies
    • 6
      Great customer support
    • 6
      Its beautiful to code in
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 5
      Php7
    • 5
      Speed
    • 5
      Easy
    • 4
      Composer
    • 4
      Laravel Mix
    • 4
      Minimum system requirements
    • 4
      Easy views handling and great ORM
    • 4
      Eloquent
    • 4
      Laragon
    • 3
      Laravel Spark
    • 3
      Ease of use
    • 3
      Cashier with Braintree and Stripe
    • 3
      Laravel Forge and Envoy
    • 3
      Laravel Horizon and Telescope
    • 3
      Laravel Nova
    • 3
      Laravel casher
    • 3
      Laravel Passport
    • 3
      Intuitive usage
    • 2
      Heart touch
    • 2
      Rapid development
    • 2
      Laravel love live long
    • 2
      Like heart beat
    • 2
      Touch heart artisan
    • 2
      Scout
    • 1
      Deployment
    CONS OF LARAVEL
    • 44
      PHP
    • 30
      Too many dependency
    • 21
      Slower than the other two
    • 17
      A lot of static method calls for convenience
    • 14
      Too many include
    • 11
      Heavy
    • 7
      Bloated
    • 6
      Laravel
    • 5
      Confusing
    • 5
      Too underrated
    • 4
      Does not work well for file uploads in Shared Hosting
    • 2
      Not fast with MongoDB
    • 1
      Difficult to learn
    • 1
      Not using SOLID principles

    related Laravel posts

    I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

    Need help deciding technology stack. Thanks.

    See more
    Antonio Sanchez

    Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

    Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

    By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

    Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

    There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

    We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

    As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

    See more