The initial setup of OutSystem is very simple. I would rate the implementation a four out of five for ease of setup.

The initial setup is a little difficult.

Some of my clients come from government backgrounds, so they prefer on-premises deployment for their systems. However, in cases where there's no sensitive data involved, they are open to using cloud-based solutions. It's worth noting that the cloud adoption trend is still in progress, and we're gradually transitioning from on-premises to cloud-based systems. Looking ahead, I believe that in the next three to five years, cloud providers like AWS and other hyper-scale cloud platforms will play a significant role. They offer tremendous scalability and various features that make them highly valuable compared to other solutions. The deployment process takes almost ten to nine weeks for smaller applications to approximately not more than three months. Our current situation involves a mix of both on-premises and cloud deployments.

The product's setup is more of a PnP procedure, making it an easy process. I feel that the setup process can be a bit complex at an architectural level.

The solution is deployed on an on-premises model.

The number of people required for the deployment and maintenance of the product depends on the product that is used. If a business entity has multiple business units, it takes a longer time to implement the product. In general, my company has a team of around 15 to 20 people to take care of the implementation process.

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.

Setting up OutSystems is straightforward. 

The initial setup is straightforward. The process is good enough and elaborate documentation and help in community forums can help the process.

The initial setup was straightforward, however, initially getting my feet wet, and kicking it off, can be difficult. The documentation at that moment in time was lacking. It was a very basic, here's how you do a hello world kind of thing, and everything else that followed those instructions were based on the same simple idea. If they could just start making the documentation a bit more realistic with real-world situations, they'll definitely be helping their clients a lot.

There isn't a lot of maintenance needed. There only needs to be one person maintaining the product.

Deployment with OutSystems has generally been straightforward, although we've encountered some challenges with UI development.

I didn't do the setup myself. That was actually done by OutSystems. I can't speak to how easy or difficult the process is, or how long the deployment takes. I don't have any insights in that sense.

The initial setup is straightforward. Normally, the solution is cloud-based, but it depends on the clients. For the setup of the platform, we must have a contract and license from OutSystems. The setup takes one to three weeks.

Setting up OutSystems is straightforward, and even citizen developers can quickly learn and start building software with it. While complex applications may require professional expertise, OutSystems provides numerous prebuilt components and features, such as UI components for creating beautiful interfaces and easy database design tools, making it accessible even for those without extensive design or development experience. It is also user-friendly when it comes to handling logic, integrating with third-party services, and working with APIs. Overall, I find it to be a great and user-friendly platform for software development. The deployment process in OutSystems involves using a tool called Lifetime, which acts as a control console for managing different environments. When you purchase an OutSystems license, you typically receive three environments: development, QA, and production, along with a separate Lifetime environment. Lifetime keeps track of application versions and modules deployed on servers in each environment. It alerts you when an environment is outdated compared to a new version in development. Lifetime also checks references and other prerequisites before deploying releases from one environment to another, making the deployment process straightforward and well-managed.

I believe you would need someone who is already good in development or has a logical understanding of development. OutSystems has four layers: the timers and processes layer, the interface layer, the version layer, and the database layer. 

Sometimes, when you add a module from the first layer, it doesn't work because it needs to be compatible and supported by the OutSystems platform. Many components or modules from the first layer are often incomplete or non-functional when compared to the later layers. 

Therefore, you need to comprehend the logic and then integrate it. It's not always straightforward. There are challenges involved. 

If you don't have someone who is already skilled in development, most of the time, you won't succeed. I believe you need a certain level of intelligence to excel in OutSystems. You have to be intelligent, like in development. 

I've brought in many developers who weren't skilled in development and put them in our system. They excelled at all the traditional tasks but when I asked for any custom work, it took them around one month to finish.

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.

The product's initial setup phase was easy.

The solution can be deployed in a week or two.

The initial setup was straightforward. I would rate the ease of setup a ten out of ten. 

We have been using OutSystems since the middle of 2016. In the implementation phase of OutSystems, we had formal training and hired a third-party (Sispro S/A) with years of experience in the technology, for consulting and to design our environment correctly.

The setup itself was straightforward. Our company chose a local installation of the platform server in virtualized machines, instead of on the cloud (there were internal reasons for this choice, such as the need for prompt responses in production systems, which are not achievable over the WAN network). The setup was very simple, however, due to our very high-security scope, some difficulties with security policies had to be overcome. I would recommend choosing the cloud platform whenever possible, as it is much simpler to start with.

The product's setup is easy. One person is enough to handle its deployment. 

The deployment and process depends upon the model we are selecting. Normally consider if we are selecting big models, it'll take around 30 to 40 minutes for making a deployment to set up 15 applications. For example, if it is a mobile application, it means if we can select only the application, it will take a maximum of five to ten minutes for creating the solution and deploying in the UIT of production. For internet banking, we use Windows authentication, ID logins. For mobile banking, we used third-party APIs. We used common plugins for the camera location and everything. We integrated with Apple, Google, and Apple Wallet also.

Everything is completely handled in OutSystems, so we have a LifeTime available in OutSystems. Previously, we don't have LifeTime so we manually exported the solution and we deployed it in the UIT. With the help of LifeTime, we're able to see the versions and the differences. We can select the proper particular application and we can do the deployment. It is easy to maintain and easy to deploy as well.

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.

The solution’s initial setup is straightforward.

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.

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

The initial setup is super simple and you can do it from your desktop. That is if you only want to implement the platform, but if you have a more complex enterprise setting, then it will be a little more complex and you will have to do some configuration, and up-front think about what functionality you expect to need (particularly if you chose to run on a native AWS or Azure environment so that you can make full use of all the functionality of those 2 CLoud environments. If you do not know exactly how the platform works and what it can do, you can implement certain things and redo a few things. But that's not a deficit. More power comes with more responsibility, l always say. 

Setup was straightforward. I was not there at that time, but I know that it was very smooth. The developer at the time was trained by OutSystems and this helped with the first applications.

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.

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.

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

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

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

Setup is not complex at all.

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

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.

The initial setup was straightforward.

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.

The initial setup is straightforward.

They have pretty good documentation to set up the environment and you just need to follow the instructions.