I like that OutSystems makes it easier to create appealing UIs without complex coding, especially compared to plain ASP.NET or React. The deployment through a DTAP process with Lifetime is extremely easy and useful. I also appreciate the ability to retrieve data easily through aggregates and use advanced SQL when needed. The capability to create extensions to integrate with external environments is very beneficial. My experience with technical support is positive, with fast responses and quick solutions or workarounds. Integration with the outside environment, especially using REST services and connecting to Workday via SOAP, is well supported, with perfect help from support to convert WSDL files for Service Studio import. The initial setup was very easy, taking just a couple of days. Review collected by and hosted on G2.com.

What I miss is conditional breakpoints which are standard in Microsoft Visual Studio for over 20 years. Review collected by and hosted on G2.com.

What I like best about OutSystems is its ability to accelerate application development through a visual low-code approach while still allowing developers to add custom code when needed. It significantly reduces development time, simplifies maintenance, and enables faster delivery of business solutions. I also appreciate its strong integration capabilities, built-in deployment tools, and enterprise-grade scalability, which make it suitable for developing complex applications efficiently. Additionally, the platform’s AI-powered features and reusable components help improve productivity and collaboration between business and technical teams. Review collected by and hosted on G2.com.

One aspect of OutSystems that I find challenging is that highly customized or very complex requirements can sometimes be more difficult to implement compared to traditional coding approaches. While the platform provides great flexibility, developers may occasionally need to work around platform constraints or use custom extensions. Additionally, licensing and infrastructure costs can be a consideration for some organizations. However, these trade-offs are often outweighed by the speed of development, ease of maintenance, and overall productivity gains that OutSystems provides. Review collected by and hosted on G2.com.

What I value most about OutSystems is how quickly it can take you from concept to a production-grade application without sacrificing architectural control. In real delivery projects, the visual development model compresses what would normally be weeks of boilerplate—data models, CRUD logic, and screen scaffolding—into hours, which frees the team to focus on the business logic and the edge cases that actually matter.

The platform’s push into agentic and AI-assisted development is where it becomes genuinely compelling. Being able to delegate scaffolding, pattern generation, and repetitive integration work to AI agents inside the IDE meaningfully shortens the development lifecycle. Just as importantly, those agents operate within the guardrails of governed platform components, rather than generating free-form code that you then have to audit line by line. That balance of autonomy with enforced consistency is difficult to achieve with a traditional coding stack.

Finally, the built-in lifecycle management—environments, dependency tracking, and one-click deployment—helps those speed gains hold up at scale, instead of turning into technical debt once a project grows beyond the prototype stage. Review collected by and hosted on G2.com.

The proprietary model does imply a degree of platform commitment—reusing logic outside OutSystems isn’t always straightforward. In practice, though, this is manageable if you keep core business logic in clearly defined service layers and expose functionality through APIs. That approach keeps the architecture portable and makes the dependency a deliberate choice rather than an accident.

Licensing can also become a meaningful line item as you scale. The best way I’ve found to handle this is to be intentional about which applications truly belong on the platform—high-change, high-value apps—and to govern environment and user allocation so you’re paying for what genuinely benefits from low-code speed.

At times, highly customized requirements can stretch the visual paradigm. The platform’s extensibility (custom code, external libraries, forge components) addresses most of these cases well, and treating those extension points as a standard part of the toolkit—not merely a fallback—removes much of the friction.

On the agentic and AI tooling side, the direction looks promising and it’s improving quickly. It’s currently strongest for scaffolding and repetitive work; pairing it with clear human review for architecturally sensitive tasks lets you capture productivity gains now while the autonomy continues to mature. Review collected by and hosted on G2.com.

I use OutSystems as a developer to create web applications for our clients, and I really appreciate how straightforward it is. The platform makes it easy to develop quickly and efficiently, allowing us to produce good-looking front ends with solid workflow logic that we can promptly ship to our clients. I like that OutSystems doesn't require much boilerplate setup since it provides default code and themes that can be overridden when needed, which means you're never forced into one set standard. Additionally, the ease of setup was impressive. Review collected by and hosted on G2.com.

The one major thing I would like is a form of branching. The one click publish is good, however, when working with bigger teams this can get clunky. Having a bit more granularity of version control would help in this regard. Maybe an option to create your own version or branch of the application which you can merge to a main branch once the code is complete. Review collected by and hosted on G2.com.

I like how it enables me to be both creative and build whole new solutions while still remaining "one toe deep" into the business side of things. For me the low code platform merges a BA role with a developer role in a way that challenges me technically while still remaining part of the analysis pipeline as well. I would not want to only write code but also refine processes, something I went to college for. This tool allows for the perfect equilibrium.

Moreover what I love is the ease of integrating different programs/third party apps and how easy it is to do. Stuff like API integrations become a cakewalk with OutSystems and it really helps that API REST is currently the most used way to integrate external data into applications Review collected by and hosted on G2.com.

Sometimes it feels like when something isn't natively supported, it need custom code and that can be quite clunky. Especially when there is not a third party tool with API integration some solutions can feel very unrefined but you have no other choice because there is no native support for it. Review collected by and hosted on G2.com.

I love the implementation speed of OutSystems. When we first presented the built-in platform tools to the customer, they were really astonished by the out-of-the-box monitoring capabilities. These tools allow us to create dashboards, filter data, and track user movements, offering amazing insights. I find the cloud-hosted environment of OutSystems great because it does most of the heavy lifting and simplifies the setup process. The platform's ability to keep up with AI advancements and not lag behind in developments is impressive too. Review collected by and hosted on G2.com.

The bottleneck for us is in the database. Performance is impacted when lots of concurrent users are trying to query heavy tables or when we have to write stuff in real time. We do optimization sessions on our SQL queries, aggregates, and caching of the data, which improves things, but the downside for us personally might be the database part. Review collected by and hosted on G2.com.

I use OutSystems to deliver applications that our clients can use to track their processes. I appreciate that it handles all the technicalities of integrations to external systems and provides easy flow visualization. I like that the platform is understandable for people like me who don’t have deep informatics or programming knowledge. We use OutSystems 11, and I find Mentor Studio great, and the interface in Service Studio is pretty good. The initial setup was very easy, and OutSystems colleagues were very responsive and helpful throughout the process. Review collected by and hosted on G2.com.

Dependencies for deployment is always a topic and merge conflicts when publishing when 2 or more developers work at the same time on the same app. It would be great if it could better and faster recognize what parts I worked on compared with other users and automatically merge them. Review collected by and hosted on G2.com.

I like OutSystems for its user interface and integration aspects, which best suit all our business processing needs. I've worked with many workflow tools, but this one seems to be the best fit. The reusable block feature is particularly valuable as it can be used more generically across multiple applications or within the same application. Additionally, I found it very easy to set up, which made onboarding quite straightforward. Review collected by and hosted on G2.com.

I don't like the deployment process. Sometimes if there is a generic application, it needs a separate deployment plan, but the dependent applications also expect to be deployed together due to changes in existing blocks or components. This needs to change. Also, I have to open the dependent module separately while refreshing the dependency, which should be improved. Review collected by and hosted on G2.com.

I like OutSystems because they consistently release new features and possibilities, particularly through their agent tech AI every eight to nine months. This frequent introduction of new capabilities allows us to be among the first to utilize these features, which helps us enhance our systems and make them stronger. The agility that OutSystems offers with these updates matches our expectations, enabling us to create applications faster and make use of reusable tools to onboard employees, partners, and customers efficiently. Review collected by and hosted on G2.com.

Well, yes. Definitely, OutSystems has RBAC kind of a facility. We need attribute-based access control, ABAC, we call it. If that is possible, it will help us in creating access controls for different users on the same form. If that feature can be developed, it would be really helpful. Review collected by and hosted on G2.com.

I've been working with OutSystems since 2010 and I was able to witness the growth of this AMAZING platform. The ease of use, the number of features that are launched, the speed of development, the ease of integrating with whichever system, makes the development look effortless.

I use the platform on daily basis for 16 years now and I can't imagine myself working on another platform that's not OutSystems. Review collected by and hosted on G2.com.

The same way the platform makes it very easy to implement, it also opens the door for some performance issues that, unfortunately, people tend to think it's a platform issue and not a development quality issue. The pricing is also something that might affect Customers to get in into OutSystems ecosystem. Review collected by and hosted on G2.com.