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.

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.

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.

My company uses OutSystems for developing mobile applications and web applications.

The most valuable feature of the solution is that it is a low-code tool with which it becomes very fast for users to create something and to show the creation to the customer much faster than any other technology.

In OutSystems, cloud management is an area of concern where improvements are required. Searching through the logs is an area with certain shortcomings where improvements are required in OutSystems.

I have been using OutSystems for half a year. My company has a partnership with OutSystems, and we have a lot of certified engineers.

OutSystems has some issues with stability. When OutSystems is used as an enterprise solution or has millions of users, then there are some stability problems with your stability. When millions of users use your application, the management of the databases and caching systems is sometimes not that efficient in OutSystems.

It is a scalable solution.

My company deals with small and medium-sized businesses.

The solution's technical support is good, especially owing to its documentation part. I rate the technical support a ten out of ten.

The initial setup of OutSystems is easy.

The solution can be deployed in a few hours.

The solution is deployed on the cloud. A user gets access to the user interface and some applications that you can install on Windows, making it a process that one person can do.

OutSystems is an expensive product. My company has to make monthly payments towards the licensing costs attached to the solution. I am unsure about how much my company spends towards the solution's costs, but its cost runs into thousands of euros. There are some additional costs towards which certain payments are to be made, considering that one needs to pay for the end user who uses the solution.

I know about the competitors of OutSystems. I didn't choose any of the competitors of OutSystems since it was a product that already existed in my company.

A person is required to maintain the solution.

If someone needs to show their customers really fast results of the development phase of an application, OutSystems is a very good solution that is expensive at the same time.

I rate the overall tool an eight out of ten.