OutSystems Reviews

Our clients mainly use the solution for business process automation, workflow automation, and application development. They also use the tool to build a layer between their existing ERPs, like SAP and Salesforce, and the applications they use for business functions, like finance and HR. It is a bridging solution between the ERP and other applications.

The time to market is quite good. We can quickly develop an application using the tool. OutSystems is developed using .NET and Java. We can easily find technical resources who have worked on .NET and Java and leverage their previous knowledge to develop OutSystems applications. It can also be used for application development. If an end-user does not want to use the solution after two to three years, OutSystems sends the source code and the applications to the end-user. There is no dependency. It’s one of the major factors I found quite good in OutSystems.

The installation is a bit tedious.

We have been partners with the product for the last two years. We are dealing with the latest version of the solution.

The tool is very stable. I rate the stability a nine to nine and a half out of ten.

We have around 60 clients in India. We have more than 35 people, including 20 developers, three to four senior developers, and one or two architects in our technical team. I rate the scalability a nine out of ten. The tool is very scalable.

The technical support team is responsive and helpful.

The installation is a bit tedious, but it can be done. If we use the cloud solution, we can immediately leverage AWS and use it. Customizing the product according to a customer’s server requirements could take five to six working days.

The customers have to pay for licensing and application development. Once they buy the product, they must also engage a technical team to develop applications until their internal team is certified and can develop applications on its own. OutSystems takes care of the maintenance. It is included in the licensing agreement. The solution is expensive. I rate the product’s cost a two or three out of ten. Not everyone can afford OutSystems.

We have evaluated Mendix as an alternative to OutSystems.

I recommend the product to others. Overall, I rate the tool a nine out of ten.

The main use case is that it is a platform as a service based on .NET. We can build any type of enterprise application, but not reporting tools. It supports multi-channel development for websites and mobile applications. We can create a single mobile application and generate iOS for the App Store and Android APK files for the Google Play Store. No recoding is required for conversion, only generation of iOS or APK files as needed.

I have mainly worked on financial and banking domains, and this platform supports all types of use cases. Additionally, with generative AI, OutSystems has started supporting it.

By using a backend database to store data brainstorming and consuming AWS APIs, our customers support the predictive AI mechanism. We can also go with generative AI because most of the tools are available in the market. OutSystems has a feature, IPP (Intellectual Property Protection), that allows for architectural property. 

If someone wants to develop a website or web application in two to three months, they can develop that application in OutSystems. If they don't want to continue with OutSystems as a platform, they can convert the OutSystems source code into normal .NET code. 

There is no extra cost required, and the application will work as a .NET source code base.

This is a possibility that the user or company can adapt this tool for development, and later, if they want to save costs, they can convert it to .NET. This is not possible with other tools.

OutSystems has integrated AI.  We can improve the application tool. For example, if a user is creating a ticket, by using generative AI technology, we can create user interaction inputs. Users can input case IDs and their contacts. Based on that, the large language model (LLM) connects with the OutSystems vector databases and is capable of analyzing and understanding what you want in natural language.

So, some sort of predictive analysis. Based on that, the program can accept the outputs.

There is room for improvement in support. They maintain a two-day SLA for everything. 48 hours is very high.

Scalability is supported by default by OutSystems on the cloud. Let's say we are buying 10 GB or 20 GB of hardware, and our database is near failure. We can request them to increase the sizes from the backend. The OutSystems cloud platform is based on AWS and installed on AWS. So whatever AWS supports is supported by OutSystems.

If we need any extra features, like using S3, OutSystems can integrate with it, but extra licensing costs are required. From the scalability and security point of view, everything is supported by OutSystems, and it is a managed service. Based on that, they are charging.

If I face any problem during application development, I can create tickets based on the category by logging into my account. There is an SLA of two to three days based on the ticket's priority, and the team responds accordingly.

Most of the time, they resolve all issues. To speed up the process, they call if there is a high-priority ticket. We connect with them and fix the issue collaboratively via phone.

I will not rate it ten, though, because they are maintaining a two-day SLA for everything. 48 hours is very high.

Positive

I did not spend my time on any other platform. For the last ten years, I have only been involved with OutSystems.

The initial setup is not difficult because everything is based on integration. A set of databases, like vector databases, and things like that require extra hardware and software configuration. But integrating with OutSystems is very easy.

There is ROI. To be specific, it's purely for the developers. It's reducing the cost of development. There is a 100% guarantee the platform is promoting code on the server with accuracy. Logical errors are a different thing, but the source code generated is secure. Anyone can understand the source code easily. We are providing security as a visual development tool. 

By using the visual development tool, there is no need to remember the syntax. Everything is available as drag and drop. It just depends on remembering how and when we need to use a node for development purposes. Let's assume a project in .NET, native .NET, or Java takes around 12 months. In OutSystems, we can build that application in four to five months.

So, twice or even more. This is the area where we can improve and save money. But definitely, this is a highly in-demand tool, and the cost is very high. It's completely dependent on the vendor. Some companies are going with the cloud environment, and some organizations are using the on-premises environment. In the cloud environment, everything is managed by OutSystems. They provide some credentials, and the company can start developing multiple applications on the same cloud license.

The cost is high. I saw on the website that the minimum license is around $4,000  per month.

Overall, I would rate it a ten out of ten. I would definitely recommend this tool.

We used OutSystems to develop different applications, especially those concerning environmental and sustainability governance.

OutSystems has streamlined or optimized our application development process.

The primary benefit of using OutSystems was our ability to deploy rapidly. We could deploy changes to our applications every two weeks.

Mostly, it was web applications that we created, utilizing the responsive aspect of OutSystems for traditional web applications.

It was easy to learn. OutSystems provides different tutorials depending on the user's expertise, so even beginners can quickly get up to speed.

Moreover, OutSystems integration with our database and internal systems was easy.

I would like to see improvements in versioning. It can be challenging to keep track of what changes should be committed, especially when many developers are working in one environment.

So, I would like to see support for different version models especially when multiple developers are working on the same module, it can be confusing to know which changes need to be deployed when comparing and merging codes.

In future releases, A built-in chart feature would be useful. We had to use Google Charts plugin for dashboards. Native support for charts, like bar and pie charts, would be beneficial.

With OutSystems, my company started working with it in 2017.

I would rate the stability an eight out of ten. It is pretty stable. 

I would rate the scalability a nine out of ten. 

There were around 20 end users using this solution in my company. 

Another team in my company used to contact OutSystems for support.

It was another team that handled the deployment process.

We used the cloud-based version, hosted in AWS.

OutSystems' low-cost approach has positively impacted our productivity, because we were able to develop faster with OutSystems, enabling us to implement many changes during our sprint.

It is very high price. 

Overall, I would rate the solution an eight out of ten. 

We have been actively following the below strategy for our application development:

• Core applications and systems (SaaS-based external products)
• Bespoke Applications (using Microsoft Azure and Dotnet Application development technologies and tools)
• Quick turnaround applications for web and mobile (Outsystems)
• Portal knowledge and corporate portals (WordPress, SharePoint, DocuWare)
• Cloud Platform (Azure and AWS)
• Support within two hours on the community portal
• Access to native functionalities (camera, geolocation, QR code reader, and access to file systems, address book, and device calendar)
• Supports custom branding
• Supports custom plugins
• Silk UI response framework
• Big focus on performance
• Best practice for CSS and JS
• Tested on several modern browsers and devices
• Support and community (52000+ members, 500+ projects, and two-hour response time)

The OutSystems platform has improved the quick turnaround for application development and deployment.

It provides for faster development and better software releases.

The solution helps reduce costs and gives us an efficient budget.

The ease of management is great.

The product has good reliability and has improved business continuity with increased resilience.

We have a lot of choices through open-source standards.

The product gives us better customer experiences.

There is access to native functionalities (including the camera, geolocation, QR code reader, and access file systems, address books, and device calendars).

It supports custom branding and custom plugins and has a Silk UI Response Framework.

There is a big focus on performance.

The product has best practices for CSS and JS.

It has been tested on several modern browsers and devices.

There is support and a good community (52000+ members across 500+ projects and a two-hour response time).

Below are the solution's most valuable features: 

• Device support (Android 4.0+, iOS 7+, Windows 8.1+)
• Access to native functionalities (camera, geolocation, QR code reader, access to file systems, address books, and device calendars)
• Custom branding
• Custom plugins 
• Silk UI Response Framework
• Performance
• Best practices for CSS and JS
• Tested on several modern browsers and devices
• Great support and strong community (52000+ members, 500+ projects, and a two-hour response time)
• Online developer training
• Integration Studio
• Service Studio
• Service Center
• Deployment services
• Faster development and better software releases
• Reduce costs/improves budget
• Ease of management
• Reliability/improved business continuity with resilience
• Choice through open-source standards
• Better customer experiences

Areas of improvement include:

• Offering workflow solutions
• Adding event-driven architecture
• Usage of PWA, Responsive, and SPA architecture for front-ends.
• Better documentation and deployment tools. The packaging features need to be standardized using DevOps.
  
• Vertical Tabs (there is a Vertical Tabs problem: Entities.Orientation)
• Data Grid improvements and UI improvements
• There are performance issues in table data using React
• They need to make improvements in various UI assets. 
• There should be automation of logs
• We have performance issues while fetching bulk data
• Need integration with core systems and integration with Outlook email

This is a no-code platform solution. We have been using this for the past five years. We've used it for building solutions for web applications and mobile applications. There is a quick turnaround for applications that need to be implemented and deployed for business.

The solution offers good stability.

There are good scalability options. However, scalability can improve.

The solution offers excellent customer support and responses can be expected within two hours from the community forum to help with resolution.

Positive

This is the first time we are using a no-code solution end-to-end.

The initial setup is straightforward. The process is good enough and elaborate documentation and help in community forums can help the process.

This was an in-house implementation from the development team.

ROI and TCO are great.

With the pressure to deliver new customer and employee digital experiences and having to adjust existing enterprise systems to cope with the market changes, 75% of app development would use low-code platforms. Outsystems has the highest ROI.

The setup cost, pricing, and licensing costs are competitive.

We have not evaluated any other options.

I use the solution since it is a low-code platform. I am more into the BFSI domain. Most of the projects that have dealt with revolve around the banking sector. I have used the product for web development and mobile applications. My company has worked on a mobile app for a bank's core processes. My company took care of the website part of the bank with the help of OutSystems. My company also operates with other clients who operate in the banking sector. My company has also dealt with the insurance domain and mutual funds.

The product's high price is an area of concern, where improvements are required. OutSystems should play around with the market or with its competitors. A lot of the clients feel that the license cost of OutSystems is way too high than the prices of its competitors.

In the future, I want OutSystems to offer support for which they should not charge any money from users. If a client is new to OutSystems and has taken a license for two or three years, I believe that the solution should provide free support for a year.

I have been using OutSystems for four years.

Stability-wise, I rate the solution an eight or nine out of ten.

When it comes to the scalability part and its impact on our organization's growth, I can say that the development and implementation timelines are minimalistic, which is something that is good. It is pretty easy to implement anything that a specific client wants with the help of OutSystems. It doesn't take years to implement something with OutSystems since such areas can be dealt with quickly.

From migration to adding internal applications is easy with the product. The platform is very adjustable based on the requirements. The customization levels offered by the product are good. It is possible to distribute the loads in OutSystems.

My company deals with around ten customers who use the product.

I have experience with high-code platforms like Java and Clutter.

The product's setup is more of a PnP procedure, making it an easy process. I feel that the setup process can be a bit complex at an architectural level.

The solution is deployed on an on-premises model.

The number of people required for the deployment and maintenance of the product depends on the product that is used. If a business entity has multiple business units, it takes a longer time to implement the product. In general, my company has a team of around 15 to 20 people to take care of the implementation process.

The clients who use OutSystems feel that it is a bit expensive.

There is a need to make yearly payments towards the licensing costs attached to OutSystems. It is an expensive product.

I don't see any differences between Java and Clutter or OutSystems since I use different products depending on the requirements of our company's clients. I don't get the clients to choose a particular platform, but my company recommends OutSystems. Not all of our company's clients prefer OutSystems.

The product's scalability is very good. The tool offers easy integration with multiple platforms.

The product's features and speeding up the application development process stem from the fact that the capabilities provided by the tool are not limited. The whole platform, user experience, and implementation time are good.

The interface of OutSystems has impacted our company's development workflow since it is very user-friendly. I rate the product's interface a four out of five.

Though OutSystems is an expensive product. If an organization wants better dynamics when it comes to a particular platform, I would recommend OutSystems to such companies.

In terms of user support and community engagement, I rate the tool a ten out of ten.

The value and positive impact experience from the use of the solution stems from the fact that it works very well when it comes to load balancing. The product is also easily configurable.

I rate the overall tool a nine out of ten.

OutSystems has use cases in the health care, accounting, banking, insurance, and automotive industries.

The most valuable features of OutSystems are the user interface, the flexibility to quickly integrate with almost anything in the system, and the ability to connect with databases.

The solution's testing framework needs to be improved, and the workflow should be slightly more mature. The solution should use generative AI capabilities.

I have been using OutSystems for nine years.

We haven’t faced any issues with the solution’s stability.

OutSystems is a scalable solution. The solution is auto-scalable regarding the number of users or the volume of data.

I have created an application which is being used by almost 2,00,000 users. That was done for some kind of enterprise wide application where it is being used across the globe. That's the maximum number of users I have created an application for.

The solution's technical support is quite useful, but it takes a good amount of time to get a solution from them. The technical support is not so quick and could be faster.

The solution’s initial setup is straightforward.

We implemented the solution through an in-house team. Depending on the size of the application, the solution's deployment hardly takes a few minutes.

With the solution, I have seen around 80% to 90% increase in the return on investment.

OutSystems is a very expensive solution, and it has to be cheaper. Users have to pay a yearly licensing fee for the solution.

I have used the solution for both web and mobile application development. In the healthcare domain, we used the solution to create a mobile application related to patient care. We also used the solution to create web applications, including banking and in-house enterprise applications.

It hardly takes around six resources, including developers, for a typical project which goes for around six months. I would recommend the solution to other users. I rate the solution a nine out of ten for user support and community engagement.

Since I've worked with the solution for nine years, I'm well aware of its visibility. I will promote the solution if the business needs align with what can be achieved with OutSystems.

Overall, I rate OutSystems an eight out of ten.

Wherever there's a mobile platform in use, there tends to be a fair amount of application activity as well. In these situations, we've observed that it's straightforward for us to integrate our systems, and this process is also highly consultative.

To illustrate a case, the customer initially had a private cloud, essentially a data center hosted within it. They needed a disaster recovery solution, which would involve using a public cloud. This situation led to some deployment challenges due to the hybrid nature of their setup.

However, once we implemented the solution for them, they were extremely satisfied. The process was not only effective but also quite speedy. To be more precise, we completed it in around 100 days, even though they initially requested it to be done in four months. They were very pleased with the efficiency of the implementation.

I'm genuinely content with the fact that all my goals and objectives have been successfully achieved in everything we've undertaken. As I mentioned previously, we found this especially valuable in terms of engagement for mobile apps. Surprisingly, we didn't encounter any notable challenges or areas where implementation was problematic. As a sales professional, I also received minimal customer feedback regarding any issues during meetings, which led me to believe that everything was going smoothly from a technical perspective. However, the initial setup can be made a little easier. 

I have been using OutSystems for the past four years.

It is stable.

Scalability proved to be an exceptionally beneficial feature. In one instance, we needed to transition from a single-tenant setup to a multi-tenant one, and we accomplished this seamlessly. The customers were also delighted with the outcome, as we successfully executed the shift from a single-tenant to a multi-tenant configuration.

I would rate it a nine out of ten.

It was outstanding. 

Positive

All options are equally commendable, but our system is notably budget-friendly. As a result, many customers are now making the switch to our platform. There are three key reasons behind this shift: our user-friendly interface, the stability of our solution, and its competitive pricing.

The initial setup is a little difficult.

Some of my clients come from government backgrounds, so they prefer on-premises deployment for their systems. However, in cases where there's no sensitive data involved, they are open to using cloud-based solutions. It's worth noting that the cloud adoption trend is still in progress, and we're gradually transitioning from on-premises to cloud-based systems. Looking ahead, I believe that in the next three to five years, cloud providers like AWS and other hyper-scale cloud platforms will play a significant role. They offer tremendous scalability and various features that make them highly valuable compared to other solutions. The deployment process takes almost ten to nine weeks for smaller applications to approximately not more than three months. Our current situation involves a mix of both on-premises and cloud deployments.

I would rate it five to six out of ten.

Two of my clients have implemented SpamTitan in their marketing and sales departments. They operate through a distribution channel, and this is where they utilize SpamTitan. They are exceptionally pleased with the results. Essentially, they deal with the delivery of products like milk, where customers place orders, and the products are delivered to their doorstep the next morning. Customers can easily place orders through their website, which is highly user-friendly. Interestingly, approximately eighty percent of transactions are now conducted through mobile devices, underscoring the system's convenience and efficiency. 

I would rate the solution a 10 out of 10. 

It is kind of used for reactive and web applications. We're also working on the mobile applications as well. I use it in a banking environment. 

I've been onboarded there and then I'm just doing the activities for both internet banking as well as mobile banking, handling both servers as well as the front end.

Currently, this banking application can consist of both mobile as well as internet banking. We have it for eight different countries. For mobile, we have eight different applications, and for internet banking, it is a single application, however, it'll support eight entities in eight countries including Bahrain, the UK, Iraq, et cetera.

Normally we use it in a banking setup. Usually, transfer payment and then the benefits pay gateway, are those kinds of integrations we are doing currently for mobile. The onboarding process we do, the login for that process, et cetera, offer good features. 

We have one feature called multiple payments where we're able to select multiple beneficiaries and we're able to create ad hoc beneficiaries. Ad hoc beneficiaries mean there's no need to add the benefits directly. We can enter the beneficiary upon the number and we can do the payment. We can add multiple beneficiaries in a single go and then we will do the validation. 

We have a back office application as well where we can configure based upon the user as well as based upon the segment. We can configure per day.

We're able to do transformations. We can do the validation before calling the API. Once validation is done, we will show the set of validation. Either it can be the OTP validation or it can be a token validation. Once that is done, we can call the final API, which calls the code banking system for doing the payments.

We've acquired a new bank and would like to integrate e-services into the offering. We'd like to be able to have an option for doing an activation directly from the internet banking area so that there is no need to contact the bank directly. Having e-services capabilities would be ideal. 

There are a lot of enhancements and new features coming.

Currently, in mobile applications, we don't have push notifications. We're hoping that will come in the new release. 

I've been using the solution for 3.5 years. 

It's stable enough. There are no bugs or glitches. It doesn't crash or freeze. 

The solution is scalable. If I want to do any changes or anything, it has a one-click publish. There's no need to re-upload anything. We make changes, we expand, and it is a one-click deployment.

Currently, in Bahrain alone, there are 40,000 users on the app. We have the same for other countries as well. We have deployed more production for three entities - Bahrain, Egypt, and the UK. Currently, for the other three entities, it is in progress. We are planning to move those changes at the end of September.

We can add users as necessary. In LifeTime, we're able to handle user management. We're able to create a set of users and we can assign roles. It can be an admin role, like full control where it's able to do publishing, feedbacking, everything. We can receive a set of users and control access to certain areas. 

Technical support is very good. If there is any production issue or anything, we can raise the ticket and they're immediately helping. If there are any deployment changes that get affected, it means we have control of all directions also. Therefore, we can manage everything properly, without any effect, actually. Everything is completely handed down to OutSystems and it is more stable. If any deployment causes us an issue we can revert back to the older version and it'll work fine.

Before that, I used a server platform called Forti. It is similar to the OutSystems Platform. We were able to use mobile and web publications and able to create using that.

I worked on an AD platform as well. 

Comparatively, I'm able to see OutSystems is very easy to maintain and easily fulfills the business requirements. 

The deployment and process depends upon the model we are selecting. Normally consider if we are selecting big models, it'll take around 30 to 40 minutes for making a deployment to set up 15 applications. For example, if it is a mobile application, it means if we can select only the application, it will take a maximum of five to ten minutes for creating the solution and deploying in the UIT of production. For internet banking, we use Windows authentication, ID logins. For mobile banking, we used third-party APIs. We used common plugins for the camera location and everything. We integrated with Apple, Google, and Apple Wallet also.

Everything is completely handled in OutSystems, so we have a LifeTime available in OutSystems. Previously, we don't have LifeTime so we manually exported the solution and we deployed it in the UIT. With the help of LifeTime, we're able to see the versions and the differences. We can select the proper particular application and we can do the deployment. It is easy to maintain and easy to deploy as well.

For doing the deployments, any changes, are completely handled on our side.

I'm not sure how the licensing is set up. I don't handle that aspect.

However, I am able to see it s very costly as compared to other platforms. That said, we see the benefit of paying so much. They provide a lot of options. 

While we use version 11.10.20 for service, the service center for LifeTime is 11.0. Currently, we need to upgrade that. The upgrade plan is in progress. We have had to start recently.

I'd recommend the solution to others. 

I would rate it eight out of ten.