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.

External reviews
External reviews are not included in the AWS star rating for the product.
OutSystems Hands-on experienced Review
Outsystems - A Leading Low Code Application
This approach significantly reduces the time and effort required to build applications, enabling faster delivery of solutions to meet business needs.
Developers can create applications that work across different operating systems and devices, including web and mobile platforms. This cross-platform capability ensures a wider reach and consistent user experience across various devices.
Developers can create applications that work across different operating systems and devices, including web and mobile platforms. This cross-platform capability ensures a wider reach and consistent user experience across various devices. so just one application can run of all devices, including responsiveness of application.
while the large budget project can only afford the OutSystems technology.
On the other hand, the support for developers is somewhat limited within the community itself. for the IOS application it is somehow lacking the completed development functionality.
OutSystems: A low code platform for building apps.
2. we dont even need prior coding experience to learn and work on outsystems.
3. Outsystems has friendly user interface and drag and drop feature makes it super easy to code and interactive .
4. we can quickly deploy apps as well.
2. There are some limitations for custom coding .
3. The new platform ODC of outsystems is not so stable and has so many issues.
4.It is very expensive for small business especially.
OutSystems facilitates rapid application development and effective project management
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
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.
What was my experience with deployment of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
How was the initial setup?
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.
What about the implementation team?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.