OutSystems Reviews

One thing I like about OutSystems is that there's no lock-in. You can keep running your applications because it's on .NET and hosted centrally. That's one of the advantages I see there in terms of not having an IT strategy that has a dependency on a particular platform.

The integration points need to be increased. People have also started to adopt this solution for their regular needs. That means it's not only the big enterprises that are adopting this solution. There are also small and medium enterprises that are adopting it. 

I've read that where you have large deployments, OutSystems starts to crumble a bit. That is the idea that no customer would know at the beginning and would also not like to hit the wall there. When it is on the client, there are a lot of applications already on low-code, and then suddenly you realize that you want to do some big applications, and you face hurdles. This is the general feedback for all such platforms.

We have been there with OutSystems for two and a half years to three years now. 

Stability could be from multiple perspectives. From an enterprise perspective, it is the stability of the company. For example, most of the enterprise ERPs are SAP, so I don't have to check twice if a product is okay. 

It's the IT strategy a company is taking, which is effectively what they're going to do for the next five years. They're going to onboard a lot of applications onto this platform. So stability-wise, of course, the scale of the company is not so big, whereas large enterprises could say that it's stable as an organization.

Coming to the other part of the stability which is at the platform-stability level, I think that the features and the support that they provide are quite good, and because it is horizontally scalable, so it doesn't matter there.

It has good scalability in terms of the target platforms, multi-tenancy, or hosting on multiple clouds.

My team has been interacting with technical support and their feedback is good. Their training is good. I think OutSystems provides one of the best trainings out of all similar platforms.

The development environment is quite easy. You install it out of the box, and it works. It's a one-click install there. I have not been involved with Enterprise setup, so I do not have any comments on that.

We primarily suggest the IT and OutSystems work together for the setup.

If I talk about enterprise-level implementation, we work very closely with Siemens, which is where Mendix comes from. We are partners with Siemens, and that's where it helps us in developing applications on Mendix because we get good community support there. I'm not sure how things are otherwise. 

For OutSystems, it is more of community support and a kind of library they have, in terms of the reference implementation of libraries, which can be applied.

For the industrial and enterprise nature of work, that is, for B2B scenarios, Mendix fares well. OutSystems might have a slight advantage for B2C scenarios. I would say that they are equivalent in most of the aspects. There are certain features that Mendix provides which OutSystems does not provide. Similarly, there are areas where OutSystems fares good but Mendix does not. I would rate Mendix and OutSystems the same. 

The initial adoption of Microsoft PowerApps is a little bit of a hurdle. If that's overcome, then other things would be reliant. When we talk about PowerApps, we talk about the whole Microsoft ecosystem, that is, Microsoft Flow, Microsoft PowerApps, Microsoft Power Automate, which effectively brings a lot of power in terms of an ecosystem. 

If I have to go with applications related to Microsoft Office 365, I might go for PowerApps. If I need external integrations and things, where they provide premium APIs and things, it becomes a little bit of a challenge. 

Development-wise, PowerApps could provide a free version. They always have but it's quite restricted. If you download OutSystems or Mendix, you could do anything with the free version. That's where, in terms of acceptance, PowerApps gets a little restrictive because you need a license to evaluate it. If it is not restricted, there'll be more adoption. Of course, you can restrict deployment, the size, and all that, but development capabilities should not be restricted.

The value proposition is not clearly visible out of these platforms as yet. Your penetration level will be decided based on if you are able to reach small and medium enterprises. If I compare something like Zoho with OutSystems, Zoho is getting good traction by purely focusing on the small and medium enterprises. These kinds of things could be game-changers in the future. 

That's where the licensing model becomes a little cryptic. Of course, for enterprise, it makes sense at certain times, and it does not at certain times. The licensing models are one of the things that could be improved there and changed in terms of adaptability.

OutSystems is quite a mature platform. OutSystems provides a lot of capabilities as such. However, it's not a one-size-fits-all kind of solution. Based on the needs, the platform that would be the most suitable one should be decided. 

I would rate this solution an eight out of ten.

The solution helps to build mobile and web applications on SOAP and REST. You can integrate it with backend systems by submitting a code.

The tool needs to improve the efficiency of its widgets.

I have been working with the solution since 2017.

The tool is very stable due to its strong architecture. The solution’s downtime is also very less. We have hardly had any issues. The product is able to route the traffic to another place if there are any issues.

The tool is scalable. It can accommodate changes in business requirements. My company has around 1000 users for the tool.

The product’s deployment is simple. The tool is a cloud solution. You need to setup an account and access its packages. You just need to download and install it.

The tool’s licensing is based on the user’s usage.

I would rate the solution a ten out of ten.

I am using OutSystems in internal workflow processes for approving expenses.

The solution has helped us, but it's no longer a strategic choice for us. We are not investing anymore in this platform. We realized the value of using OutSystems if you have an internal development capability. We've been using the solution mostly in outsourcing for development tasks, and it doesn't make much sense to us, to pay the amount for the solution for the capital gains to go to the external provider we use for the development.

If I have a large team of developers, eventually using the solution would make sense. That's not the case. In my business model for IT, I do not have any internal development capability. I'd rather do it without a rapid development platform because the savings go to the provider. It doesn't go to me. I have to pay for the ticket and then I have to pay additional costs for the development. It doesn't make any sense. It is a good solution and technology, it only does not fit our use case.

The most valuable feature of OutSystems with discipline and the development processes. Instead of each developer doing tasks on their own with their own approach, et cetera, the solution would help bring some organization to the development process. 

I have been using OutSystems for approximately five years.

We did not experience a time when the solution did not perform, the solution is stable.

I rate the stability of OutSystems an eight out of ten.

The solution can scale. However, the catch is the pricing has become more and more expensive in the last few years. Consumption is increasing, and the price has increased a lot.

We have approximately 200 users using this solution in my company.

The support is not provided by OutSystems themselves. It's the service vendors, the integrators. There is a shortage of skilled workers that are knowledgeable of the tweaks of the platform and the shortcuts that can increase the productivity of using it.

We are using ServiceNow and it's depicted as a container for OutSystems. It's not the same, but it has the capability of doing some type of rapid development, and we are using it more and more.

The largest obstacle currently associated with OutSystems is its high cost and limited availability of skilled personnel. Despite being a rapid application development platform, having a highly skilled individual familiar with the platform can be much more beneficial than an inexperienced individual. Because there is a shortage of people with the necessary OutSystems skills, utilizing the platform can become expensive. This makes little sense, considering that a rapid application development platform should be accessible to the average person. However, having a highly skilled individual can greatly increase productivity, making the cost worthwhile.

I rate the initial setup of OutSystems a four out of ten.

I have not seen a return on investment using OutSystems.

OutSystems is expensive, and they changed the pricing model in the last couple of years.  It's changing too much and it's becoming unstable. They are constantly shifting their prices based on users, courses, and other factors.

To ensure that we will be able to benefit from leveraging internal development capability, I would suggest using a tool, such as OutSystems. With this solution, it is possible to increase the average productivity of the existing team of developers. Even a small increase of two to three percent can lead to significant gains. However, if there is a limited number of developers, it may be difficult to realize substantial productivity gains from using OutSystems.

I rate OutSystems a seven out of ten.

We use it to help our clients generate certificates. They needed an app to help them record and have data. It allows them to take the certificate number, check if it is authentic and if the equipment that the ticket number is issued against is working perfectly.

The drag-and-drop feature is very valuable.

The tutorials for the solution should be updated.

We have been using this solution for about a month and are currently using version 11.

The solution is stable and doesn't require many server resources, so I don't think there are stability issues. They have enterprise and have been around for a long time. Some of the tutorials we use were created in 2014, and we still use them.

The initial setup was straightforward. Once we registered, we installed it and were able to start work immediately. It took approximately 24 hours to set up.

I rate the solution an eight out of ten. The solution is good but can be improved by updating the tutorials available. I advise people considering the product to ensure they have their data somewhere to generate a certificate. Additionally, I advise them to do their own research. The application makes life easier.

OutSystems is easy to use. 

I have been using OutSystems for six months.

OutSystems support is okay. 

Setting up OutSystems is easy. It take one or two hours. 

The price is okay. OutSystems isn't expensive. It's a mid-range solution.

I rate OutSystems nine out of 10. I recommend evaluating it as a POC first. If everything is okay, you can start.

I use OutSystems' platform to build mobile apps for our customers as well as good old-fashioned web applications.

Before using Outsystems to develop a client's reporting systems, the process would take six months to complete a report. After using Outsystems, and building a custom application, report-building is one click away - and it only took us three months to build the custom application using OutSystems.

For me, the most valuable feature is the flexibility the tools give us to change as customer requirements change, on the fly, when we are in a meeting. I also like how easy it is to deploy the code between environments and how easy it is to integrate OutSystems with other systems.

The latest version of the app generation tools could be more user-friendly.

You can have your solution on the cloud or on-premise, it all depends how you develop your code. But from my 11 years experience, well-developed solutions don't have stability issues.

All platforms and languages have their limitations. If the solution is designed, from the beginning, to scale properly, there will be no problem at all with OutSystems. The way OutSytems works, it is not too hard to scale.

Technical support is good, always able to help.

Setup is not complex at all.

You should contact OutSystems for more details but my opinion is that it is not for small business budgets.

The conventional coding rules don't apply here. You need to have an open mind and let the platform take control from you at times.

The solution has helped our organization with the timely delivery of projects. We have seen more than a 100% increase in productivity across all the teams.

The solution's most valuable feature is its ability to organize the entire project view on one platform, including data, development, and processes.

The solution's ability to create and run automated tasks could be better. They should include data extracting and handling tools in the next release.

We have been using the solution for six years.

I rate the solution's stability a nine out of ten.

I rate the solution's scalability a ten out of ten.

The solution's initial setup process is easy for the cloud version. However, it is complicated for the on-premises version.

Our clients have seen a return on investment for the solution.

The solution is too expensive for small companies. Whereas, for large companies, it is worth the investment.

I advise others to ensure they have a long-term strategy for multiple projects while opting for the solution. Otherwise, it would be challenging to receive a return on investment.

The solution is good. I rate it a nine out of ten.

We are a financial institution, and our primary credit solution is developed in OutSystems. We have several small apps, not for mobiles, but apps that are developed to support our core business, which is factoring and credit.

It is easy to use.

In my opinion, the support and the pricing could be better.

I have been working with OutSystems for seven or eight years.

OutSystems is a stable solution.

OutSystems is scalable.

In terms of the solution, we went through some minor escalations. It was simple to manage. We have also added some redundancy to our app server, which was simple to set up.

Our company is still small, with a staff of about 50 people. I believe ten of them are developers. They develop, operate, administrate all systems platforms and deployed applications. The remainder, are business units.

The SLA should be improved. The response time could be improved.

I can't say for certain that it was simple. It was simple for us. Because I have an experienced manager who manages our team, it was simple for him to set that up.

It took some time because we were building a core banking service system from scratch. What we did in OutSystems, aside from setting up all of the licenses and the platform itself, was that we had help because it was the early days of the company. OutSystems in Portugal assisted us with this. However, because the solution was created from scratch, it takes a long time to deploy it with the business solution.

I manage a development team that develops and maintains DevOps. Within that team of developers, I add one who leads the team that also handles all of the tool's administration.

I believe they are very strict with their pricing platforms, or the pricing policies, and it changes. They have changed it from software units to application objects in recent years, and now it's all free, but you pay for the users. 

I believe they should have a better scheme for companies like ours, which are small and could benefit from the platform without paying too much.

The fees are approximately €150,000, €170,000 per year, which is excessive for a company of our size.

We don't have any additional costs, but we did have, within this price we had some, I believe we have some agreements regarding accelerator, to be honest, I don't know off the top of my head.

They should have OutSystems support with the setup and structuring of the best pricing for the goal that they want to assign to the solutions. Because of the pricing, if you want to use OutSystems for self or internal solutions, it would be very different, but it could be very expensive if you want to develop things for the outside, which would require users and business management. I believe they should receive support directly from OutSystems or through a vendor. I'm not sure which is preferable. However, OutSystems support is required for installation.

I would rate OutSystems a seven out of ten.