
Unqork: The Leading Codeless as a Service Platform
Comprehensive features in one platform improve project management
What is our primary use case?
When I started working in Unqork, it was just entering the market. This is why we did not have proper predefined use cases in Unqork, and even now they are not fully available, only small snippets. We used these snippets, and from academic training and boot camp, we started developing small POCs before joining real-time projects. We developed cases based on experience and learned extensively. Based on our experiences, Unqork has also evolved significantly. Since 2021, there have been numerous changes in Unqork, including the designer portal, canvas, securities, and other features. We have implemented all new functionalities and features delivered by Unqork in quarterly patches.
Currently, I am working with a client where there is an agreement between the client and Unqork itself. Unqork provides software to the client under this agreement, and simultaneously, the Unqork product team uses this client environment as an early access environment. We are maintaining six projects - three completed and three in progress. They conduct experiments on live servers where applications are being used by different region users. The version I am using (71680) is not yet available in the market, as we have early access approximately six to seven months ahead.
What is most valuable?
The drag-and-drop functionalities in Unqork's developer portal are comprehensive. In the Unqork canvas, all components such as notepads, text areas, text fields, radio buttons, checkboxes, and drop-downs are provided without requiring code. Unqork provides default styling options, and if a project requires additional styling, it only needs minimal customization. Configurators do not need to write code for simple predefined elements in Unqork. This feature is similar to Pega, which I worked with in the past, but Unqork appears more advanced.
What needs improvement?
Case management functionality is not currently available. Regarding versioning, while it is available to the market, it is not optimal. If versioning is deployed on any application, rolling back is not possible. When multiple people work on the same module in different versions or branches, merging can overwrite changes. The merging technology needs improvement in Unqork.
Connecting to the database is straightforward, but querying MongoDB and getting results requires additional effort. Case management is still unavailable to the general market. We attempted to implement it but had to step back as it did not meet all business functionalities. The Vega versioning also presents development challenges despite business interest.
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the scalability of the solution?
On a scale, scalability rates at 8 or 8.5, with room for improvement of 1 to 1.5 points. The platform still needs to incorporate AI, voice technology, and service request technology. For customer care applications, call integration directly into the application rather than phone systems would be beneficial.
How are customer service and support?
What other advice do I have?
Unqork includes multiple tools within its UDLC toolkit portal. It provides a release management application where users can select modules, data collections, applications, and workflows for promotion. The promotion process is straightforward and easy to learn.
Infosys, my current company, provides support and development for Unqork. Some companies partner directly with Unqork for product-related support. When product issues arise, service requests can be handled either by direct Unqork team members or partner companies.
In Unqork terminology, the term 'configurator' is used instead of 'developer'. Configurators do not need to write code for predefined elements in Unqork. While this feature is similar to Pega, Unqork offers more advanced capabilities.
Developers benefit from easy integration and UI development but face challenges with data manipulation and complex workflows
What is our primary use case?
I mostly work with Unqork to develop internal applications, and right now, I'm working with JPMorgan in a department called Asset Wealth Management. We try to automate processes that were previously done manually through emails, SharePoint, and Excel, which can be error-prone and time-consuming. We aim to serve internal employees rather than client-facing applications.
Only one application I have developed is client-facing, but the traffic for that application is very low.
What is most valuable?
With Unqork, you can develop user interfaces easily, and it's mostly beneficial for developers and firms rather than at the client level. The drag-and-drop feature makes it very easy and fast to develop, which drastically reduces costs compared to regular coding technologies that require database purchases and maintenance. With Unqork, everything comes in a package, so there's no need to worry about databases, provided your firm is okay with the security standards they follow.
Unqork makes data integration very easy, especially in how you make API calls and retrieve data from external APIs. They simplify the process to the point where even a business person can learn to integrate with other systems using the integration system in the administration tab. As a business person, I just need to use the applications and integrations already provided in Unqork.
What needs improvement?
The areas of Unqork that need improvement include the UI, as data-driven applications in banks require displaying data effectively on forms and dashboards. When working with JPMorgan, the data structures stored in APIs present challenges in retrieving and displaying data. It is tough to understand the data workflows in Unqork and manipulate them, especially for someone without experience. The functionality for data manipulation is not straightforward, and the transforms component requires additional coding, which complicates API responsiveness and impacts user experience due to latency issues.
For how long have I used the solution?
I have been using Unqork for nearly more than 1 1/2 years, with a break in between. Before this, I used it for 8 months, and now again, I am using the tool for around 6-7 months.
What do I think about the stability of the solution?
I would rate Unqork's stability as an 8, because whatever they promise is consistent and reliable until production. I do not see any instabilities regarding the features they promised.
What do I think about the scalability of the solution?
I rate Unqork's scalability as a 3 or 4; it is not highly scalable. For applications facing around 1 lakh customers, it's better to avoid using Unqork due to significant data latency issues and limited control over optimizations for API calls.
How are customer service and support?
I would rate the technical support for Unqork as a 9. We have a community where we can ask questions and usually receive support within 3-4 hours from other developers who can assist us.
Which solution did I use previously and why did I switch?
I have worked with Core AI, another low-code platform, recently, about 3 months ago, alongside Unqork.
How was the initial setup?
I would rate my experience with the initial setup of Unqork as a 10, because it is a cloud-based application. You can directly access it via any browser by entering the URL and land in the development environment without needing to download or set anything up.
What other advice do I have?
Unqork is assisting with AI-driven projects for my customers through Gen AI developments, but to be frank, I have never used that technology with AI. They are developing it, but it's not fully complete or widely used yet. We typically use our in-house AI to integrate by making API calls and then sending and receiving data.
As of now, with Persistent, I had one customer for whom we developed two applications, but unfortunately, they are not using either due to performance issues. This dates back to around 2021.
Now, I'm working with JPMorgan, where we have multiple in-house applications that everyone is using because they are not complex applications. We're using Unqork for systems such as ticketing, but I am also working on a more complex application that is still in the development phase.
I rate the pricing for Unqork as a 7. They should consider making their pricing more flexible, particularly for small applications where customers may only want to test if it works before committing further. In those cases, they shouldn't charge as much as they do for standard applications.
For JPMorgan, we have the license for approximately 2-3 crores per year, but I am not 100% sure since I haven't been involved in enterprise meetings for first-hand information.
Overall, I would rate Unqork 6.5 to 7 out of 10.
Enables rapid project delivery through dynamic functionality
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
How was the initial setup?
What other advice do I have?
Fast UI creation and responsive support improve project efficiency
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
How was the initial setup?
Which other solutions did I evaluate?
What other advice do I have?
No-code environment enables seamless application creation and modernizes systems
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
Which solution did I use previously and why did I switch?
How was the initial setup?
What about the implementation team?
What other advice do I have?
Enables faster development cycles with no-code cloud solutions
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
How was the initial setup?
What about the implementation team?
What was our ROI?
What's my experience with pricing, setup cost, and licensing?
Which other solutions did I evaluate?
What other advice do I have?
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Optimized data collection fosters user validation but faces challenges in UI-driven applications
What is our primary use case?
What is most valuable?
What needs improvement?
For how long have I used the solution?
What was my experience with deployment of the solution?
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and support?
How would you rate customer service and support?
Neutral