ClickUp is a productivity platform that brings together work apps, data, and workflows. Also presented as a Converged AI Workspace, ClickUp eliminates work sprawl to provide context and a single place for humans and agents to work together. The platform currently boasts over 20 million users worldwide.
$0
per month per seat
Google App Engine
Score 8.2 out of 10
N/A
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 Azure
Score 8.4 out of 10
N/A
Microsoft Azure is a cloud computing platform and infrastructure for building, deploying, and managing applications and services through a global network of Microsoft-managed datacenters.
$29
per month
Pricing
ClickUp
Google App Engine
Microsoft Azure
Editions & Modules
Unlimited
$10
per month per user
Business
$19
per month per user
Enterprise
Custom
Starting Price
$0.05
Per Hour Per Instance
Max Price
$0.30
Per Hour Per Instance
Developer
$29
per month
Standard
$100
per month
Professional Direct
$1000
per month
Basic
Free
per month
Offerings
Pricing Offerings
ClickUp
Google App Engine
Microsoft Azure
Free Trial
Yes
No
Yes
Free/Freemium Version
Yes
Yes
Yes
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
Discount available for annual billing.
—
The free tier lets users have access to a variety of services free for 12 months with limited usage after making an Azure account.
I personally like Azure more but my current team does not do any development work ourselves and thus we thought it would be inappropriate. I find Jira to be a bit less flexible than ClickUp, though both require a certain level of learning. People moving from Jira or Azure to …
Compared with Microsoft Azure, Google App Engine requires a more complicated development environment setup. It's not as simple as using Visual Studio 2015 with Azure SDK. There are multiple IDE on the market to choose from for developing apps for Google App Engine. JetBrains …
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 …
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 …
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 …
We have settled with Microsoft Azure considered its effective administration and the ability to data visualization and analysis, together with the top-notch security/stability.
ClickUp is well suited to organize projects and communicate internally with teams members and externally with clients or vendors. If you need to track emails, any emails responded to from an email sent within ClickUp is automatically tracked within the task where it originated. It also works great for storing document files within projects and tasks and tracking multiple versions of documents created or copied within ClickUp
App Engine is such a good resource for our team both internally and externally. You have complete control over your app, how it runs, when it runs, and more while Google handles the back-end, scaling, orchestration, and so on. If you are serving a tool, system, or web page, it's perfect. If you are serving something back-end, like an automation or ETL workflow, you should be a little considerate or careful with how you are structuring that job. For instance, the Standard environment in Google App Engine will present you with a resource limit for your server calls. If your operations are known to take longer than, say, 10 minutes or so, you may be better off moving to the Flexible environment (which may be a little more expensive but certainly a little more powerful and a little less limited) or even moving that workflow to something like Google Compute Engine or another managed service.
Azure is particularly well suited for enterprise environments with existing Microsoft investments, those that require robust compliance features, and organizations that need hybrid cloud capabilities that bridge on-premises and cloud infrastructure. In my opinion, Azure is less appropriate for cost-sensitive startups or small businesses without dedicated cloud expertise and scenarios requiring edge computing use cases with limited connectivity. Azure offers comprehensive solutions for most business needs but can feel like there is a higher learning curve than other cloud-based providers, depending on the product and use case.
Customization is huge for us! We do not have the aspects of standard project management, so having the ability to customize basically everything in ClickUp is amazing.
An outstanding free version of the software! We are a small nonprofit organization that cannot afford the robust levels of other software, so having access to SO MUCH for free is incredible.
The layout and organization of tasks, Spaces, folders, etc. is perfect. I love how I can see which task all of my subtasks belong to on my dashboard. And the option to change colors and icons for everything also really appeals to my obsessive brain.
Microsoft Azure is highly scalable and flexible. You can quickly scale up or down additional resources and computing power.
You have no longer upfront investments for hardware. You only pay for the use of your computing power, storage space, or services.
The uptime that can be achieved and guaranteed is very important for our company. This includes the rapid maintenance for security updates that are mostly carried out by Microsoft.
The wide range of capabilities of services that are possible in Microsoft Azure. You can practically put or create anything in Microsoft Azure.
There is a slight learning curve to getting used to code on Google App Engine.
Google Cloud Datastore is Google's NoSQL database in the cloud that your applications can use. NoSQL databases, by design, cannot give handle complex queries on the data. This means that sometimes you need to think carefully about your data structures - so that you can get the results you need in your code.
Setting up billing is a little annoying. It does not seem to save billing information to your account so you can re-use the same information across different Cloud projects. Each project requires you to re-enter all your billing information (if required)
The cost of resources is difficult to determine, technical documentation is frequently out of date, and documentation and mapping capabilities are lacking.
The documentation needs to be improved, and some advanced configuration options require research and experimentation.
Microsoft's licensing scheme is too complex for the average user, and Azure SQL syntax is too different from traditional SQL.
It has been a game-changer in terms of project tracking, as animation is a demanding product that requires multiple layers of analysis, revisions, tracking, scheduling, etc. ClickUp simplifies many approvals as anyone can easily add items, and you can tag the people who need to look at them.
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.
Moving to Azure was and still is an organizational strategy and not simply changing vendors. Our product roadmap revolved around Azure as we are in the business of humanitarian relief and Azure and Microsoft play an important part in quickly and efficiently serving all of the world. Migration and investment in Azure should be considered as an overall strategy of an organization and communicated companywide.
Because for me, working with teams, ClickUp has provided a service that we longed for. Something that is non-complicated and easy to maneuver. We understand the learning curve can be steep, but we are willing to give the software a chance because it is everything we hoped it would be. However, leadership found the project works for our organization at this time. Moreover, we can customize to our needs.
I had to revisit the UI after a year of just setting up and forgetting. The UI got some improvements but the amount of navigation we have to go through to setup a new app has increased but also got easier to setup. Gemini now is integrated and make getting answers faster
As Microsoft Azure is [doing a] really good with PaaS. The need of a market is to have [a] combo of PaaS and IaaS. While AWS is making [an] exceptionally well blend of both of them, Azure needs to work more on DevOps and Automation stuff. Apart from that, I would recommend Azure as a great platform for cloud services as scale.
For over a year ClickUp was unavailable to us just twice for a couple of hours. I would say for a system this big and working globally that was a minor issue. They managed to fix all the issues within a couple hours and then it was back up and running perfectly fine.
The speed of ClickUp is average to be honest. This is one of the biggest flaws of the system, sometimes it's also lagging a little bit but we also have a lot of documents, lists etc. on our workspace. However, with the next version of ClickUp I've seen they are planning to increase the speed by almost 500%, probably by changing the technology, so I am more than looking forward to it.
I started using ClickUp when it was what most would consider a baby company. There were the occasional bugs that made working in ClickUp a little bit of a headache, but the support feature allowed me to chat with a real persona and communicate my issues. I would always get prompt support and someone willing to really help me, not just point me to FAQ pages. Not feeling like a number really makes a difference.
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.
We were running Windows Server and Active Directory, so [Microsoft] Azure was a seamless transition. We ran into a few, if any support issues, however, the availability of Microsoft Azure's support team was more than willing and able to guide us through the process. They even proposed solutions to issues we had not even thought of!
There are multiple guides on literally all of the functions you can find within the system, therefore it's easy to learn anything you'd really like to use, starting from project and people management, down to Gantts, mind maps, time tracking, inviting Clients as guests to work with you on the projects and so much more.
Start small. Don’t try to build the most elaborate plans first. Resist the urge to get into Gantt charts if no one is used to them. Just get work written, add dates and assignees, and start getting used to it. If you did not use a work management tool before, you need to be gracious with yourself about the fact that you likely do not have the muscle memory for working this way yet. But you will get there.
And leverage people who know it if possible. Look for ClickUp experts and vendors. They can really supercharge your effectiveness at building the tool out and speed up the process.
As I have mentioned before the issue with my Oracle Mismatch Version issues that have put a delay on moving one of my platforms will justify my 7 rating.
I used Salesforce at my last job and would recommend ClickUp if utilizing the product for more than just sales. My last company tried using Salesforce for a number of other actions, such as department project tracking, client documentation, and outbound communication which did not work well. ClickUp is far better at managing multiple levels of organization within a company.
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 compared to the other major players in Azure and AWS.
As I continue to evaluate the "big three" cloud providers for our clients, I make the following distinctions, though this gap continues to close. AWS is more granular, and inherently powerful in the configuration options compared to [Microsoft] Azure. It is a "developer" platform for cloud. However, Azure PowerShell is helping close this gap. Google Cloud is the leading containerization platform, largely thanks to it building kubernetes from the ground up. Azure containerization is getting better at having the same storage/deployment options.
Scaling with ClickUp is superb. If you create a workflow best suited for your organization then it's all about creating new accounts and teaching the new employees the workflow you're using. It's that simple. There is no black magic when it comes to Clickup.
Effective integration to other java based frameworks.
Time to market is very quick. Build, test, deploy and use.
The GAE Whitelist for java is an important resource to know what works and what does not. So use it. It would also be nice for Google to expand on items that are allowed on GAE platform.
For about 2 years we didn't have to do anything with our production VMs, the system ran without a hitch, which meant our engineers could focus on features rather than infrastructure.
DNS management was very easy in Azure, which made it easy to upgrade our cluster with zero downtime.
Azure Web UI was easy to work with and navigate, which meant our senior engineers and DevOps team could work with Azure without formal training.
