OutSystems Reviews

I have been involved in the development of applications, whether web applications or mobile applications for multiple clients, and we have adopted OutSystems platform for the rapid application development of our applications at enterprise level.

I have several examples to share. I would start with e-commerce and banking applications. In the initial phase when we adopted OutSystems in one of my initial companies or organizations, we worked upon a couple of banking applications for our onsite clients where we developed end-to-end banking solutions for the citizens into their state. We also developed some government-based applications for child birth registration, citizens enrollment, and new establishments enrollment. After that, coming into the pharmaceutical domain, I got much more exposure building multiple applications into OutSystems. A couple of them are we developed the tender solution, which is for the pharmaceutical industry where different, either the private or the government sectors, send out the tenders for manufacturing of the drugs and medicines. Various medical or pharmaceutical clients can bid on those tenders and check what kind of therapeutic area, the dosage, they can particularly work upon and whether the probability of their winning or getting loose for the tender. Different perspectives or aspects are there. For example, we have the overview, planning, then tendering solution, the tender calendar, how soon it is going to come, what will be the duration, the end date, tenure, all of those things. Then even in the patient services, we did develop a lot of applications into OutSystems. Starting from making different medical solutions for the client, whether it could be copay card solutions, their insurance finders, claim submissions, and so on. These are a couple of good examples, and a lot of different domains which we have worked so far into OutSystems.

There are a couple of applications or projects where we worked which reduced the duration from six months down to approximately two months. The duration of six months can be reduced to two months and even less than that depending upon the complexity and the resources allocation into the team. We have worked upon some e-governance applications, banking applications, as well as patient services applications where we have saved an enormous amount of time and were able to give an initial MVP product for the demo purpose and a production release as well in a shorter amount of time.

All of these did save money, not to a very great level, but up to a significant level. It is reducing your resource consumption or allocation hours. You may probably need few team members with skilled capabilities into OutSystems so that your go-to-market time frame almost reduced to more than 50% as compared to other technical platforms. These are a couple of good positive aspects.

There are many valuable features. I would say if someone is looking for developing an application at a faster rate and having different integrations with a cross-functional team, OutSystems is one of the good platforms to adopt and get your application kickstarted so that it can be delivered on time. It can handle your multiple scenarios where you need to connect with different integrations perspective or connect with your internal or external databases, lazy load solution. If you want to scroll different types of huge data, you can implement some scrolling features or on-demand loading. OutSystems is very useful for that purpose.

OutSystems is purposely targeted for the rapid application development, whether it is the web or mobile application development. You can easily build if you have skilled developers into your zone and deployed at the right area. It is a market, ready-to-market kind of platform tool, then very much scalable for the enterprise-grade applications. You can get different in-built and customizable templates which are ready to use as per your needs and requirement. Cross-platform deployment is pretty much easy here. Maintenance and reusability are benefits as well.

Regarding the maintenance and the reusability aspect, I would say OutSystems is pretty much good to handle if you have quite good skilled and experienced developers into your team. From the maintenance point of view, if everything has been designed in an architectural side in a nice way, things have been put in a right space and being monitored properly. Maintenance is not a challenging task into OutSystems. Regarding the reusability, OutSystems does provide the Web Blocks or the widgets, wherein you can design some reusable components and can deploy them into a separate module. Those modules or reusable components can be utilized into multiple applications depending upon your needs. This gives a good example for the reusability.

Regarding the scalability point of view, it is designed to scale for the enterprise needs. Depending upon your needs, you can increase the CPU memory consumption and your memory storage there. Depending upon how huge the application is or how small the application is, you can easily manage your enterprise IT level architecture things as well.

Every platform or low-code platform tool is quite good in its own area, but there is always space to groom or enhance or improve. The same is with OutSystems as well. A couple of things from the integration point of view can be enhanced. If your application or the enterprise organization is tackling a huge data application where you have bulk amounts of data, it becomes a challenge for all the technologies and the same with OutSystems. You have to design your architecture in a very magnificent and decent way so that how you process your data so that load can be easily balanced. Data handling and huge data handling is a kind of challenge you may need to face.

Then we have some vendor lock-in. If you are trying to migrate your application from OutSystems, then you probably get into this vendor lock-in system. Some organization may face challenges if some organization is on a small scale size. The small scale businesses may find OutSystems costly because of its high cost and pricing due to the licensing cost. Apart from that, OutSystems really plays well, and it needs a learning curve. If a traditional application or programming is there which your developers are skilled into and they are directly deployed into OutSystems, it may take some significant amount of time for them to get comfortable with OutSystems. There is a learning curve.

OutSystems community is already in place, but it can more be enhanced regarding some aspects. They did organize lots of bootcamps and other user groups as well, but those can also be improved from the documentation point of view and having some integration guidebook as well.

A couple of things which can be improved into OutSystems include the licensing cost, the vendor lock-in side, the learning curve, couple of integration aspects and customizations.

It has been almost more than eight years that I have been involved into the IT industry in various domains.

I would say it has been around almost six plus years that I have been involved into OutSystems.

The customer support is pretty much good. They do have the customer support ticketing system where you can raise the ticket, decide the priority, and depending upon your priority and urgency, they are going to resolve your problem.

Positive

I started with OutSystems itself. My first organization was also parallelly working on the Appian and they did start OutSystems parallelly as well. Later on with OutSystems, we had a couple of other low-code platform tools in the organization including Mendix and Power Apps. Different organizations have their own way of developing the application to different platforms and they can work upon multiple platforms as well. These are a couple of platforms which our organization was parallelly working on.

These are basically the leadership decisions regarding which platform they may want to go with. Higher leadership made the plan, then later on, we were involved into decisions. I think they did check out the Jongkyan or the Power Apps and the Appian, but they found OutSystems pretty much good at the initial level.

I would highlight two points here. One is the faster development, it is a ready-to-market application, rapid application development, definitely. Secondly, time efficiency. Your team can be deployed to work on different modules parallelly and you can really save time up to an enormous level. If a legacy or a traditional application is taking five to six months, those can easily be designed into OutSystems in less than two months.

Regarding the cross-platform deployment, I would say you can build your applications and deploy as per your need because OutSystems does provide different kind of architectural deployment into your organization once you are planning to adopt it. You can reach out to OutSystems and can ask them to have it on-premise so that your IT team will be having the controllability on that. You can ask them to have it cloud published so that everything will be on the cloud and OutSystems will be managing on your behalf. Or it can be in the hybrid mode, which means when you are deploying the applications, you can host in whatever the server you wish to. Even for the mobile application, you can build Android and iOS and deploy it into the different platforms. Regarding the templates, for quicker start, OutSystems does provide a couple of templates already existing into its service studio, wherein you can check out and see if those are useful, you can use them, otherwise, you can build your own templates from scratch as well.

Initially, when we adopted OutSystems, it was pretty much good because the organization was having a huge number of projects into the pipeline. The cost was pretty much comfortable because every organization has their own business budget. It depends upon if you have a large business budget organization, OutSystems is good to go. Similarly, for small scale business, it could be a challenging one. Everyone has their own perspective on that. Our way was we were initially good, but later on, the organization did face that the licensing has been increased to a much higher extent.

OutSystems is a really good platform to work upon. If any of the organizations are looking forward to working with OutSystems or adopt OutSystems platform, they can definitely go with it if they have a good budgeting with them. They just need to check out the right resources allocation. If they have skilled and trained developers who are already trained or it may take a significant amount of time as a learning curve, they should note that OutSystems does have good training documentation available. I give my very good wishes for all those business partners or organizations who are going to adopt OutSystems. The overall review rating for OutSystems is 8.5 out of 10.

The main use cases for OutSystems involve being part of a COE in my company where we explore multiple low-code technologies. I have been part of three projects in OutSystems and have done lots of PO fees, and currently, apart from my project, my colleagues in the COE team are also working on different OutSystems projects. We have a good number of OutSystems-certified developers in training, and we mostly have enough projects and continue to work on OutSystems projects while I have also been working in the Power Platform for the past year.

What I find valuable about OutSystems is that it has a very good learning curve for developers. Within two weeks, we can gain knowledge in OutSystems, and it is very easy to learn. With my background being .NET, OutSystems is straightforward to learn, which is beneficial. Developing applications in OutSystems is good, and the flexibility allowed by OutSystems for application development is excellent compared to my experiences with other low-code technologies, where I've faced some challenges. The clean separation of concerns in the architecture provided by OutSystems is a key benefit compared to other platforms.

OutSystems integrates with our existing tech infrastructure and provides flexible integration. If we want to integrate with third-party services, OutSystems has SOAP and RESTful services that allow us to consume external services, integrate with external databases such as SQL or Oracle, and includes integration studio for writing custom .NET code. After developing a .NET component, we can reference it in service studio, creating a reference file that makes integration easy. OutSystems officially supports various integrations and also includes an API discovery tool for consuming and exposing services, providing a lot of information about incoming URLs, similar to how we use Postman.

From a development perspective, everything in OutSystems is fine, but we must be very careful about the architecture when creating any new modules. It is crucial to be aware of which module corresponds to which application in real-time projects, as there are multiple applications. OutSystems does support tools to help categorize components across different layers, but enhancing features related to architecture would be beneficial for accommodating new changes more easily in our existing applications.

I have been using OutSystems products since 2021, and we have established a partnership with OutSystems because some of our company's clients want to know more about it. We were supposed to get some projects, but unfortunately, we didn't secure any with OutSystems. I got trained in OutSystems and became certified, but I didn't get a chance to work on OutSystems projects initially. I have good experience with OutSystems since I have known it from 2016, got certified, and since joining Entity Data in 2019, I have been working with OutSystems for four to five years.

OutSystems provides a lifetime environment which includes development, QA, and production environments based on the license type chosen. For deployment, once applications are done, everything is taken care of automatically by OutSystems, handling dependencies and modules efficiently when publishing to respective environments. The reliability of OutSystems is good as it continuously checks health statuses and points out any issues that arise, which allows us to take actions accordingly. So far, I haven't encountered any performance or deployment issues. If we decide to publish in the cloud, options such as Amazon, GCP, or Azure are available.

OutSystems applications are scalable. They can be deployed vertically and horizontally, supporting as many deployments as needed. If we want to scale by adding new frontend servers, OutSystems provides those features due to its cloud-based nature. If additional environments are required, we can easily contact OutSystems to procure more servers, and increasing the number of end users and internal users is also possible, albeit at additional costs.

I haven't faced significant challenges or complexities while scaling applications with OutSystems. Based on the license we have chosen, I've leveraged all the available environments without encountering difficulties. There may be complexities if scaling is attempted beyond our current environments, but I haven't personally experienced any issues as we are very specific in how we utilize our license.

I evaluate OutSystems tech support as not specifically dedicated but rather abundant in resources. Many helpful videos and documentation are available on the OutSystems site, making it relatively easy to learn the platform. If someone encounters issues, OutSystems has a community where questions can be posted, and many developers and resources can provide guidance and assistance.

Positive

Setting up the OutSystems environment is straightforward once you obtain the license. You only need to download one file, which is the integrated development environment, Service Studio, and afterward, provide your environment name, user ID, and credentials given by OutSystems. After logging in, you can easily use OutSystems. However, if you want to install the lifetime server, it requires careful setup and can be tedious, needing a well-configured server.

In the project I am working on, we have three developers in India, all acting as senior developers, with a total of six environments including one development, one QA, one UAT, and three for production. In Spain, we have about five to six architects and other personnel involved, while the main team, located in the US, includes over 12 to 15 people in total.

Using OutSystems for application development leads to significant time-saving, cost-saving, and resource-saving benefits. For instance, developing a project in traditional technologies such as .NET might take about eight months and require ten resources. In comparison, developing that same project in OutSystems can be completed in around 40 to 50% less time, requiring only six resources.

I'm not completely certain about OutSystems pricing, but they provide trials and various standard and premium packages. The initial license may allow for only one development and one production environment with limits on internal and external users. Subsequent users can be added at an additional cost per user; exact pricing details can be found on the OutSystems site.

The pros of OutSystems compared to competitors include its ability to develop applications quickly, allowing us to bring them to market in a shorter timeframe. We can take a concept and develop it within one week or a few days. Even citizen developers can create components, although some technical background is required. The cons involve delays in project timelines primarily due to the time taken in requirements refinement and challenges faced when adding new features, making it somewhat complex to manage and maintain applications as they grow in scale.

I received a message from LinkedIn regarding PeerSpot with notifications about wanting to know details about how exactly the low-code platform works. I highly recommend OutSystems because it is a robust and rapid application development platform with a less steep learning curve. Developing applications from scratch is easy, and while other low-code technologies are good for smaller applications, OutSystems is particularly effective for enterprise-level applications. I rate OutSystems 9 out of 10.

I am working as a consultant for African companies that are considering all kinds of plans to reach European export readiness, and in that case, I have used some source information to inform them. I'm not looking for a platform solution myself, but I have spread the suggestions to look at this to approximately 20 companies.

I've recommended looking into the phenomenon of low-code solutions, and that's what they are considering. There are a few coding companies, and they see that they are losing traction because of the lack of speed that they have compared to other faster solutions. That's why I suggested to them to have a look at the options of no-code and low-code solutions, and that's what I used your report for.

I have recommended OutSystems for startups that were looking for an MVP solution, and also, I have recommended it in situations where very rigid enterprise structures are blocking them from being agile. I advised OutSystems to be used in flexibilizing the current application landscape.

What I would like to see is more servicing business analysts in the next release of OutSystems. The direction of the business analyst could be improved.

I have been familiar with OutSystems for 10 years now.

I have experience working with Mendix. OutSystems also, and Betty Blocks is another Dutch no-code platform.

I've seen some differences between OutSystems and Mendix, and I see OutSystems is more convenient for developers who have been coding. They will appreciate OutSystems more than Mendix, which really has a very business-savvy angle.

There's no exit strategy in OutSystems. If you start working with OutSystems—but that's not the sole problem of OutSystems; it's, in fact, the case for every low-code and no-code solution. If you want to leave it or want to go to another technology, you're kind of stuck, and it will cost you a huge investment to get rid of that.

I am mainly consulting.

I have been working in this field for 28 years now. I have been working as a Senior ITI consultant for CBI, also for IPD in Germany, Sequa, GIZ, and Mastercard Foundation.

I find the pricing of OutSystems reasonable in any way. If I look at the infrastructure investments that companies are doing in the enterprise, compare it to SAP, for instance, then I really think the pricing of OutSystems, but also of Mendix and other platforms, is making a lot of sense at this moment.

I do not have any partnership with them or am I a reseller at the moment. I stay away from that because I don't have the time for it and it doesn't pay me.

On a scale of one to ten, I rate OutSystems an eight.

OutSystems is used for application development, both internal and external systems. We are currently using OutSystems as our platform for semi-development. We are a client with OutSystems, though we are aware of other products such as Pega Platform, ServiceNow, and Microsoft that we are not using at this time.

OutSystems has no issues so far. The drag and drop environment is quite dynamic, and we can create our own UI on top of it. The UI in OutSystems is a strong part and can be customized. We tend to use AI tools such as Cursor in OutSystems. We use integration extensively in OutSystems, which allows us to connect our own internal systems to our newly created system applications. The pre-built templates and components in OutSystems work well, and we can customize them as needed for our intended use.

In the future with OutSystems, improvements could be made on the costing side rather than the feature side. If the cost could be lower, that would be beneficial.

We have been using OutSystems for approximately one year.

There are no stability issues with OutSystems. We have not experienced any downtime.

We have not yet gone through long-term scalability testing with OutSystems since we have only been using it for one year.

We occasionally receive support from OutSystems. There have been no issues with support, and they can respond within as late as 24 hours.

Positive

We previously built our own systems manually and traditionally. Due to the fast pace of business, we moved to faster development with OutSystems.

I have not used any similar tools to OutSystems from other vendors.

Price is the biggest concern with OutSystems. I am not aware of negative aspects of OutSystems. I am satisfied with the technical capabilities of OutSystems. I purchased OutSystems from a reseller. If you want something to be changed in OutSystems, you can do it manually, or add or remove information as needed. Overall, I would rate this review as an 8 out of 10.

We use the solution to automate some of our internal processes and to integrate with platforms like SAP and ServiceNow. We use it mainly for internal toolsets, streamlining repetitive tasks, and process automation.

The product could benefit from improved connectors to integrate with outside platforms.

I have been working with OutSystems for approximately one year.

I rate the product scalability an eight. 

The customer support services are good. They are quick to respond and provide effective assistance with technical issues.

The deployment process has been easy. It takes less than five minutes to complete.

I handled the installation process myself.

The OutSystems' most effective features for speeding up development cycles are the process orchestration and the drag-and-drop updating of business processes.

I would recommend it to a friend or colleague, especially if they are looking for a solution that is easy to deploy and helps streamline internal processes.

I rate it a six out of ten. 

I use OutSystems with many of my customers, especially in the banking and insurance sectors, to manage internal business processes in a more efficient way.

One of the valuable features of OutSystems is the very small lead time for the delivery of projects. OutSystems offers a lot of reusable components and solutions that I can simply drag and drop and use, which has a significant impact on project delivery time. 

The integration capabilities have benefited my customers by providing many connectors out of the box, allowing for the integration of external applications or business applications.

I would like to see more integration between the use of artificial intelligence to speed up the process delivery time.

I have been working with OutSystems for one year.

The initial setup of OutSystems is not easy. It is a very heavy application that requires a lot of hardware and software resources. I would rate it as a seven out of ten due to the need for huge machines to use OutSystems.

I rate the overall solution as a nine out of ten.

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.

Positive

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. 

I am a consultant for another organization. We've been using OutSystems to develop in-house applications and a convention-type application.

The solution is all-encompassing and very easy to use with its drag-and-drop feature. OutSystems has a Forge feature that allows me to drag and use predeveloped components into the platform so that I don't have to develop everything from scratch.

I'd like to see AI features integrated into the solution.

I have been using OutSystems for two years.

We've very rarely encountered an issue with the solution crashing.

I rate the solution’s stability a nine and a half out of ten.

OutSystems is a very scalable solution. We developed an app, and we've had no problem at all with having 200 people at the convention and, in other cases, 1,000 people at the convention. We use the solution daily in our organization.

There have been times when the solution's technical support took a while to respond. This happens mostly because their technical support is not in North America but Portugal.

Neutral

I also extensively use another product called Apex. It's an excellent product, but it's not the same as OutSystems. With OutSystems, I can develop phone applications. I cannot do that with Apex because it's built more for a back office.

Using OutSystems to develop applications in-house as opposed to using third-party solutions has probably saved our clients a lot of money in the long run. They're not paying the licensing fees over and over again to the other platforms.

The solution's integration is very good. We've integrated the tool into some other SQL areas we have at the client, and it's no problem integrating at all. The solution is deployed on the cloud.

OutSystems is an excellent platform for development and would be an excellent tool for any small, medium, or enterprise business. However, depending on the price, which I don't know, it may be out of range for small and medium businesses.

Overall, I rate the solution a nine out of ten.