OutSystems Reviews

We have used OutSystems to develop a simple portal in the cloud. This portal is mainly for internal use and not for actual customers or external users.

It's generally not for daily usage, so there's only a small team that uses OutSystems as their primary tool in their day-to-day work, but because it's open for any and all kinds of developers, there are probably hundreds of users throughout our organization.

I like the mobile features the most, and there are also various features around the portal we created that I enjoy.

We're still pretty new to OutSystems, though it has become apparent to us that, even though it's a so-called low-code platform, there are still some things that require a programmer. For example, you don't really need a lot of programming skill to work with OutSystems, but if you want to do something that's a bit more 'feature-ish', then you still need some programming experience.

Since we first started using OutSystems, they switched their language support from Java and .NET to .NET only, which was a bit of a surprise. Their language support could be better in this sense, although on our resource side it is now a bit more flexible.

On the whole, most of the features that we've required are all there. But there are some upcoming features that we are looking forward to. For example, the AI modules. They also have third-party vendors that produce different connectors, but I am hoping that OutSystems itself will start to create more innovative connectors or complementary solutions that we will find of use.

We have been using OutSystems in our organization for about one and a half years now.

So far there have been no major issues so I would say it's pretty stable. 

We haven't yet reached the level that we need to seriously consider scaling, but from my experience it isn't so easy to scale any kind of closed platform where you start without the source. They may offer you the source later when migrating, but it's generally not so easy to queue up onto another platform or move to another vendor, so I expect that the scalability in this respect might be lower than we would like.

So far, most of our support is coming from internal sectors of our organization. I think it's easy enough to resolve all the issues we come across within the company.

We do use another similar product which isn't very well-known. It's a product from Germany and we use it mainly for internal use in the same way that we use OutSystems.

Comparatively, as a low-code kind of platform, OutSystems is the most intuitive to use, but if you have an experienced programmer in Java and .NET like myself, then the other platform is probably a bit more flexible.

It's basically a simple portal that we developed in-house.

The implementation details really depend on the project and the type of organization. For example, because we are quite a sizeable organization, there are other processes that we need to fulfill in order to maintain compliance before we push our projects to go live. Thus, for us, the full implementation took about six months. Thankfully, the maintenance is pretty low.

I think the pricing for OutSystems is comparable with similar solutions. I would place it somewhere in the middle. We pay for the bundle and don't pay anything extra in terms of licensing and other fees.

I recommend OutSystems, but I would also point out to others that they're not the only product out there that deserves attention.

I would rate OutSystems an eight out of ten.

We use the product for developing applications.

It improved our output, mostly in the reactive and mobile applications we developed. 

We used almost all of the features, themes, styling guide, and approach components. They are useful in our applications. 

Technical support could be better, and out-of-the-box performance could be improved. 

We have been using OutSystems for five years.

We had some lagging issues under high data loads, and the solution needed to be customised to improve this.

The solution is scalable.

Technical support would get a three out of five, as there is some wait time involved and some solutions were not adequate. This is an area for improvement. 

Neutral

We previously used Darknet but switched to OutSystems because it offered some more tools and features.

Setup was easy and there are a lot of forums to help, I would rate it five out of five in that respect. 

We had an in-house setup, requiring only one person.

It depends on the use case, but we found the solution to be pretty expensive.

Setup is easy, the solution is also easy to learn and there is a lot of community support on forums to help. Aside from the cost, OutSystems has been good for us. I would rate OutSystems a seven out of ten.

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.

We are a reseller and OutSystems is one of the products that we provide to our customers.

OutSystems allows you to do things really quickly.

This product requires very little maintenance, and it is easy to do as compared to traditional programming solutions.

The prices should be lower. It is a little bit too high for a small market.

I began working with OutSystems in 2014.

The stability of this product has been incredible. I would rate it a ten out of ten in this aspect.

We are in a small country and although this is a scalable product, that is not usually an issue for us.

The technical support is perfect.

I would rate the technical support a ten out of ten.

The pricing is an area that needs to be improved.

The subscription is billed on a yearly basis.

This is a product that I recommend for anybody who is digitalizing things. It's an incredible tool and you can do things very quickly. Certainly, you should look into it if you are going to implement any kind of application. Whether it is field service, internal applications, external websites, or something else that is related to the digitalization of processes, and where you have to interact with many systems for integration purposes, this is a good tool.

I would rate this solution a ten out of ten.

I was only testing OutSystems.

The most valuable feature of OutSystems is the drag and drop and toolchains in the small AI developing environment. Additionally, the documentation is helpful.

The dashboards in OutSystems could improve. There are a lot of tabs in the service center that can be confusing.

I have been using OutSystems for approximately one month.

OutSystems is stable.

The scalability of OutSystems is good.

I am the only one using this solution. I am a student at a university.

The support from OutSystems is good.

I rate the support from OutSystems a five out of five.

Positive

The initial setup of OutSystems is easy. You only need to sign up. It takes approximately 15 minutes.

I did the implementation of the solution by myself.

There is a free trial to use this solution and other options available, such as enterprise. There are different subscription plans.

The enterprise version of the solution is approximately $1,500 annually.

The maintenance of the solution can be done by one person.

I would recommend this solution to others. There is a portable version available for them to try.

I rate OutSystems a nine out of ten.

We use OutSystems to analyze disparate applications that are about to become obsolete.

As we currently can't afford it, we are still in the testing and evaluating phase.

You can use this solution to build applications very rapidly. It can also easily be deployed on mobile devices and applications as well.

The biggest challenge for us is the licensing model and the cost of OutSystems. The apps that we are interested in have a very large user-base and OutSystems drastically ramps those costs up.

I have dealt with this solution for roughly 18 months.

We have no complaints surrounding both the scalability and stability of this solution.

We use ServiceNow for CMDB and ITSM related needs; we don't use ServiceNow for application development, so for us, the two aren't comparable. I don't have any experience with SericveNow's capabilities in that space. 

Our team had no issues with the technical side of the initial setup. Ultimately, they were able to create prototypes and build apps really quickly. But I think where we failed was with the commercial side of it, in terms of the licenses and the costs surrounding deployment.

I believe our functional labs were up and running within a couple of days; however, we have not deployed it on a wider scale as we can't afford to.

Our in-house team of one or two people took care of everything.

OutSystems is a good solution, but it's not cheap. 

On a scale from one to ten, I would give this solution a rating of five. The technical features are good, but the actual commercialization is out of reach.

I'm using OutSystems to build an ERP system and a customer portal.

OutSystems' best feature is that you can build tests with the flow, so even the tests are made in the PDD framework in a low-code way.

The PDD framework can't be used for the behavioral-driven development way of working. They're working on improving that, but it's taking a long time. OutSystems also doesn't have branching, which means if there's a production issue, it's not so easy to fix.

I've been using OutSystems for a year and a half.

OutSystems is stable.

OutSystems is scalable.

We've had good contact with OutSystems' consultants.

The initial setup was straightforward.

We used a team of OutSystems developers.

I would advise anyone considering implementing this solution that you need a senior OutSystems developer to help your in-house developers because it can be quite hard to work with in the beginning. If you have a senior OutSystems developer who can help with best practices, then you're good to go. I would give OutSystems a rating of seven out of ten.

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.