Google App Engine is Google Cloud's platform-as-a-service offering. It features pay-per-use pricing and support for a broad array of programming languages.
$0.05
Per Hour Per Instance
Microsoft Power Automate
Score 8.3 out of 10
N/A
Microsoft Power Automate is an advanced automation platform offering a range of features, including AI-powered automation, robotic process automation (RPA), business process automation (BPA), digital process automation (DPA), and process/task mining. The platform aims to empower organizations to securely automate their operations at scale by leveraging low-code and AI technologies.
$15
per month per user
Pricing
Google App Engine
Microsoft Power Automate
Editions & Modules
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Power Automate Premium
$15
per month per user
Power Automate Process
$150
per month per bot
Hosted RPA add-on
$215
per month per bot
Process Mining add-on
$5,000
per month per tenant
Offerings
Pricing Offerings
Google App Engine
Microsoft Power Automate
Free Trial
No
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Google App Engine
Microsoft Power Automate
Considered Both Products
Google App Engine
Verified User
Anonymous
Chose Google App Engine
For our organization, we selected Google App Engine which provides a reliable and efficient way to create and deploy apps moreover it supports a lot of languages and provides automatic debugging of code which enables us to deploy code to production as soon as development is …
If you have a small team which is also responsible for development of the product then surely go for it. And if you have a larger team with dedicated person to take care of deployments. Go for cheaper options such as compute engine or AWS (be sure to do your research on pricing …
It's the manageability of the Google App Engine which made it a better option in our case. It's quite straightforward to deploy on App-Engine. No worries for monitoring setup
You can create and scale Kubernetes clusters quickly, but you have to keep an eye on that cluster. In-App Engine, you don't have to worry about infrastructure, but in some scenarios, Kubernetes fits better.
Google App Engine is the first product we picked up to store the mass data. Later we came to know that, firebase database is also similar to Google App Engine. But still, we didn't step into it. We will try it later.
Azure App Service is in par with Google App Engine although you may want to use Azure App Service if you are integrating with other Microsoft IT components, for example SQL Server. Google App Engine is great when in long run, you will be using Google cloud components, for …
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if …
Google App Engine is very easy to use and mostly up to date makes it compatible with all old and new devices. The applications are very interactive and the prices are accessible for most users. The prices tend to get slightly expensive as we head on towards higher …
The two giants are Google and Amazon. Both are very similar however Google App Engine allows you to deploy your web applications through platforms like Python where as if you're using AWS, you have full control on the operating system services. Google is good because you pay as …
We were on another much smaller cloud provider and decided to make the switch for several reasons - stability, breadth of services, and security. In reviewing options, GCP provided the best mixtures of meeting our needs while also balancing the overall cost of the service as …
We commonly decide between App Service, Elastic Beanstalk, and App Engine. Normally, we do not have a strong preference for the services, it really comes down to whether or not there are other factors drawing us toward a particular platform. In the case of App Engine, it is a …
I think that Microsoft and Amazon are simply investing more in their offerings, and there are a bunch of cool PaaS solutions out there as well. Google App Engine is solid, and is probably the right choice for some projects. But ultimately one should evaluate each platform …
Google Apps is great for environments where the need for a more robust platform is not necessary if you are looking to have email and cloud collaboration enablement of your working staff. From the stand point of using both, I can see the value of both but it really depends on …
AWS and Heroku are both great, and I use them both extensively for different projects. Google App Engine was chosen because it is much more innovative than AWS, and because Heroku specializes in Ruby on Rails. Even though Heroku supports Java and other services, we feel Google …
With GAE it's a matter of "code your app and deploy it". You don't care on what servers or on how many servers it runs. System administration is done for you. With AWS you still have to be a system administrator with good knowledge and undestanding of load balancers, database …
You can spawn up your own cluster using Kubernetes or Container Engine which will scale automatically when configured properly, but you have to keep an eye on that cluster. In App Engine you don't have to worry about it at all, just ship your code and it will run.
We chose Google App Engine because it supplies the most infrastructure per dollar spent. It's much more expensive to use Amazon EC2 to scale to over a million users. Also, the engine's narrow language support system, while somewhat limiting, makes getting started quickly much …
We left Lotus Notes for the (more versatile) Google Apps. We could never recommend the closed architecture of Lotus Notes. We have evaluated Office 365 and believe the product is compelling. So compelling, that we may consider a platform change…
Google App Engine stands out since it offers everything as being a platform as a service. The other options I used before, such as classical development with servers available either in house or in the cloud still require a lot of management and the software frameworks …
In our experience, Microsoft Power Automate fails with throttling and became unusable to meet our client deadlines. Nintex did not experience throttling issues for us.
Firstly, it came with organizational license, so it was available to everyone, for some of the automations that we're not able to do so when we took license for other tools it was more difficult and tedious to do hence, we had to shift back to Microsoft Power Automate. License …
Microsoft Power Automate is worlds ahead of Zapier in so many ways. The looping, DOM access, and flow controls are much better. I feel that accessing different data within previous connectors used in a flow is much easier in Microsoft Power Automate as well.
The Microsoft Power Automate have the browser based access which doesn't require any tool installation separately. Whereas for the Uipath, many dependencies are needed for the flows. We need to purchase the separate License for the UiPath but in case of the Power Automate, it …
I have only used Microsoft Power Automate as our organization is using microsoft ecosystem and i can access its features easily. With new features it is sufficient enough for my use as if now. I would recommend it for those who are in microsoft ecosystem to use it is capable …
I have many years of experience with Nintex applications and it stands up very well against Microsoft Power Automate. I hope Microsoft Power Automate can become the better workflow application. With the Integrated AI builder and continuous updates I expect they can become the …
Power Automate beats UiPath basically from a costing perspective. I prefer Power Automate over UiPath because of its different costing segments that make it way cheaper than UiPath.
SmartSheet provides a number of functions when it comes to dealing with and showcasing tabular …
User Interface and Ease of Use, Integration Capabilities, Bot Development, Cognitive Services and AI Integration, Scalability, Pricing, Community and Support. The most thing that Power Automate stands out from others is the Pricing models as it is way more cheap than Automation …
UIPath allows for automation of saving email attachments but the time required to create this automation is a great deal longer than Microsoft Power Automate.
Microsoft Power Automate is a Low-Code,No-Code approach making it easy for a beginner to learn and understand. The integration with microsoft ecosystem is an advantage. The cost is less when compared to uipath. There are pre built templates available and the AI integration is …
Microsoft Power Automate is the platform we can say very user friendly You need not to know the coding and programme you just need to enter the flow you wanted and you are set . You no need lengthy program and eventually no time is required. Very productive tool we are using …
Power Automate is a no-code/low-code solution tailored for workflow automation, data integration, and AI integration, making it an excellent choice for Microsoft-centric organizations. OutSystems, on the other hand, is a comprehensive application development platform, offering …
Power Automate is very well integrated with Microsoft office 365 suit, Teams channel and SharePoint online. The workflow UI is very user-friendly and the users from non-technical background can easily understand the tool and start automating any simple and complex workflows. …
Power Automate is much more powerful than IFTTT or Zapier, and the cost is included in our current license. IFTTT is sometimes too simple in their API capabilities, and Zapier charges per process which means the high frequency tasks that we most want to automate quickly get …
Both have their use cases. Nintex Automation Cloud allows external users to submit forms, which Microsoft PowerAutomate or PowerApps doesn't allow. (Power Pages is very costly)
Google App Engine is especially well suited for situations where there is a variable workload during the day, e.g. inbound task processing with task queues. In this situation queues can be setup with parameters governing the process speed/scaling which allows you to easily balance performance with cost and meet a good balance.
We replaced all the classic SharePoint and Nintex-based workflows with Power Automate. This saved extra licensing costs and getaways from managing legacy workflows. Power Automate Designer is very user-friendly and requires no additional learning curve. We also use it to replace RPA solutions created with other platforms using the Power Automate Desktop application.
Building an application that uses Google's Authentication, means users no longer need to remember an different user id and password. Once they are logged into to Google, they can seamlessly access your application hosted on Google App Engine.
Google App Engine automatically scales up and down. SO if your application receives a spike in user traffic, App Engine automatically launches additional instances of your application to cater for the increased traffic. Once App Engine detects that the spike is usage is over, it automatically scales down to handle the current traffic.
Google App Engine can be easily integrated with Google Cloud SQL, Google Compute Engine, Google Cloud Storage etc, so that you can build out a full application using one or more of Google's Cloud Platform products.
App Engine is a solid choice for deployments to Google Cloud Platform that do not want to move entirely to a Kubernetes-based container architecture using a different Google product. For rapid prototyping of new applications and fairly straightforward web application deployments, we'll continue to leverage the capabilities that App Engine affords us.
Power Automate is a great product that has a vast array of options on how to use it. Your imagination is the only hurdle with using Power Automate as there is no limit to what can be done with the system. It has brought a lot of value to our business through the use of custom systems, connectors, and streamlining processes.
Google App Engine is very intuitive. It has the common programming language most would use. Google is a dependable name and I have not had issues with their servers being down....ever. You can safely use their service and store your data on their servers without worrying about downtime or loss of data.
For most tasks WinAutomation is great and easy to use. You just set up tasks on a step by step basis and you can even tell the program what to do when there is an error (such as continue with job). Sometimes with complicated web extraction jobs it would be good to be able to easily extract data from the web page source.
Good amount of documentation available for Google App Engine and in general there is large developer community around Google App Engine and other products it interacts with. Lastly, Google support is great in general. No issues so far with them.
both Community support and Microsoft official support typically respond to (and resolve) reported issues in a VERY expedient manner, usually going above and beyond for education and bugfixing. I have been thoroughly impressed with the level of support I had been provided in the past.
after reviewing the main features of Power Automate, the Microsoft trainer focused on some of our real life use cases implementation, from simple to more advanced.
although it was productive, it is more difficult to stay focused and in a 7 hours a day online training (including screen share issues and the fact that the trainer just can't precisely show the exact location of your mistake)
I had to migrate from Robocorp to Power Automate. The automation was using API and sharepoint. So it was better to use Power Automate instead of Robocorp so we did the migration. in some areas the migration was easy but creating flows and making it smaller codes was difficult. Debugging the code was tough so we took lots of time.
App Engine is a much more streamlined system than EC2. There is a fundamental difference between them, but they are used for basically the same thing as far a I could tell -- to serve applications EC2 is certainly more complicated, but if offers more machine-level control if that's what you need. It can tend to cost more as well. App Engine is far more straightforward but there are limitations if you need to change the environment. But even then, Google Compute Engine also compares to EC2 and stays within GCP.
Power Automate can do many things that most platforms can't do as a 'citizen-developer' with no access to coding tools and deployment. It allows you to develop and deploy low/no-cost automation flows quickly. The blocks in Powert Automate do the API work for you, where you only need to connect the key data points and actions taken.