Globalscape EFT Reviews

Our company uses the solution to manage integrations and file transfers for our customers. The solution can be integrated with any system such as Salesforce and can perform API calls. 

We keep track of all data via the built-in report option. For example, we can mention a job name and automatically pull records for the last six months. Details such as how many transactions succeeded or failed are included.

User groups are created to provide access levels and permissions. For example, developers are given access to development and testing but not production. We have a total of 25 team members that are split into groups across development, production, and support.  

Our customer had the on-premises solution in place but is now in the process of moving to the AWS cloud. We are part of the migration team so are moving on-premises jobs from the on-premises version and MOVEit to the cloud. 

The GUI base is handy because you don't have to run commands. 

The dual interface accommodates Windows or Linux installations. 

The API call feature is valuable because we can build jobs in the solution but run them via external triggers. Most other products do not allow this type of action. 

The solution is user friendly so anyone can learn it with some background knowledge of managed file transfers, encryption, types of protocols, configuration, and key items for authentication.

The advanced controls for security and compliance are important. Standard protocols are SFTP and FTP but compliance teams will not agree to FTP because any middleman can steal data with a user ID and password.  Banking companies prefer SSH keys with authentication and the solution includes this feature. For example, IBM shares their public key to JP Morgan Chase's system and then IBM uses their private key to make connection. PGP encryption is also used to convert plain text to encrypted data that cannot be hacked without the private PGP key. 

There is an automated process for receiving and processing daily files or regulatory documentation. 

The file synchronization option stands out from competitor products. The advanced workflow engine allows you to write code for file or folder synchronizations. For example, an Excel sheet has 14 tabs and it is saved into the local FSX. The solution reads the tabs, converts each to a separate CSE file, and sends all 14 files to the destination S3 bucket. 

A job skeleton can be used from test to production so you don't have to build jobs from scratch in production. Once created in the test environment, jobs can be exported in the .JSON format and imported to production with minimal changes to the source or definition files. This is a great feature and saves a lot of time. 

The solution lags a bit when you have thousands of jobs, multiple users, and multiple developers accessing it at the same time. A typical login should only take five seconds but IT is experiencing loading delays. Connection profiles for configuration changes should immediately apply and refresh. 

I have been using the solution for one year. 

The solution is stable but there are some lags when jobs or users increase to high levels. The database itself is very stable. A prior upgrade made some improvement to lag time. Once we upgrade again, stability should be aligned and good. 

The solution is scalable. A dedicated, cloud-based tool called ARCUS is available for scaling. The solution also allows storage in S3 buckets which is a unique feature. 

We troubleshoot errors ourselves so have not needed technical support. 

I started my career with Busy Link. It was used to transfer between different entities or within an organization. Very few companies still use it because there are so many products in the market. 

Our customer previously used the solution's on-premises version and MOVEit.

The setup is in the cloud and we focused on migrating from on-premises and other solutions. 

Creating jobs can seem difficult until you get used to it. If you have a basic understanding of MFT, then you can learn how to write event rules and other things within a few month's time. Once you build a few jobs, the solution is very easy to use. 

Our company handles migrations for our customer. For the use case mentioned, we migrated all Sterling Integrator and 300 MOVEit jobs and that took three to four months. Everything but the solution was decommissioned. Our client is very happy and has saved a lot of money on licenses or support for multiple systems.

Our customer has realized ROI because they no longer have to manually upload files, purchase licenses, or contract for support for multiple systems. 

The solution is reasonably priced in comparison to other products. 

There are so many tools in the market such as Current Direct or Sterling Integrator. Gartner chart for managed file transfers is a top four tool in the market. 

The solution is new so it grabbed our attention. It can be used for any company in the file or retail domain as a transferring tool. Two key points that attract customers to the solution are its user friendliness and reasonable pricing. 

Connect Direct is difficult to handle because it is installed on Unix, mainframes, and Windows so you have to be skilled in all three environments. You also need peer-to-peer transmission so the solution must be installed on both sender and receiver systems or it won't work. 

Sterling Integrator is a major, robust tool that is used by many companies. It can handle EDM mapping which is not available with the solution, so it is a bit of a different product. You can use the map editor to edit, build, and send files. 

Sterling Integrator can handle huge amounts of data but troubleshooting logs is cumbersome because you have to go to the business processes and read logs line by line. Whereas the solution handles troubleshooting logs better because it pushes an error notification, the failure location, and download or upload steps. Only very skilled people can work on Sterling Integrator. 

For our use case, we decommissioned file transfers for each and every interface that was running in Sterling Integrator and migrated them to the solution. We did the same for more than 300 jobs that were using MOVEit. 

The solution is easy to use and configure. Scalability or lag time can be improved across thousands of jobs to ensure the solution is available 24/7 at a moment's notice.

If you want EDI separate from MFT, then the solution is the best choice and I rate it a nine out of ten. 

We have lots of data coming in from or going to financial institutions like banks, including payments and different types of transactions. Any client can connect to GlobalSCAPE to retrieve their files and data. We also go to their servers and pick data. We have a lot of clients, vendors, and partners that share data for different applications. Most of the data goes through SFTP, which is a protected protocol.

Our main production server is on-prem. The version of Globalscape that we are testing right now, version 8, is on the cloud in Azure.

Our SFTP team uses this as the main platform to do file transfers. As a result, Globalscape helps with operations, maintenance, security, and advanced tasks that we accomplish through the platform.

We have also been able to move a lot of jobs from batch and PowerShell scripts, as well as C++ and some other programming languages. It has helped, to some degree, to remove dependency on other methods. The impact has been positive because things are more centralized and better organized.

The automation of file transfers has increased our efficiency and effectiveness a lot, as they would with any other MFT system. It enables you to automate any processes that you might otherwise have to do manually. That reduces workload. Otherwise, you would have to do things through scripts or manually. There are still some things being done manually by different business teams, but a lot of it has been automated. We also need fewer programming resources now.

We have about 300 jobs and I would estimate that Globalscape saves 40 hours per week, in total.

The most valuable feature is the automation engine because it allows you to script or program and it has lots of different features and options. It's something like an IDE for programmers, where they can add variables, arrays, loops, et cetera. It has much more functionality than the advanced rules component, which only has limited options. You can use automated scripts, such as those built with PowerShell, in GlobalSCAPE, as well as scripts that you build in Globalscape.

It's also very important that it is designed specifically for Windows because our servers are Windows and everything that we do is in Windows. Of course, we have a few Linux servers and even an SFTP server, but it's very important to be in the Windows space.

In addition, we use it to automate the submission of regulatory documentation and that is another very important functionality for us.

The solution’s centralized platform for the management of file transfer operations is good, although improvements could be made to it.

Another area for improvement is the ARM (Auditing and Reporting Module) database, in terms of accuracy and the data being logged. 

And when it comes to functionality, there could be more descriptive instructions for various functions or actions.

Finally, I would like to see more advanced features for the alerting.

I have been using Globalscape Managed File Transfer for almost three years.

The stability of the solution is medium. There could be some improvements.

It's scalable.

We have hundreds of internal staff members who rely on Globalscape to make those files available to them for their processes. We also have hundreds of external clients, vendors, and partners. It is definitely used extensively.

We used PowerShell scripts and batch scripts. We still have them, but we didn't have an MFT.

I was part of the deployment on the dev side for the cloud, but not for the main production instance. The part I was involved with was medium, between simple and complex. It took a few weeks.

The maintenance load is average. I take care of it. We have another engineer on the SFTP team but I am the one who mainly maintains and operates the SFTP environment.

For the deployment I was involved in we did it in-house, but we did ask some questions regarding the gateway server and the ARM database. We consulted with Globalscape support on a couple of questions we needed help with.

Our experience with them was good.

We do see a return on investment every single year. These are very critical processes. If a single file is missing, it could cause damage of $70,000, $80,000, or even $100,000. It's very important to have a robust system and that we can do advanced functions.

The on-prem licensing is very good. It's a perpetual license and I would advise others to purchase that license. That way, you don't have to pay yearly.

There are modules that you have to purchase, such as the ARM database module, and the security module, depending on what you need. Those modules increase the perpetual license's cost. There is also support which comes at an additional cost. If you purchase the perpetual license, that means you own that version, and if you want support or if you want to be able to update it, then you have to buy the premium support package, and there are a couple of tiers.

The way we secure sensitive data in Globalscape MFT is through Active Directory's RBAC, its role-based access control. But in part, we do it through Globalscape too, because we have supervisory accounts where internal people can access the data through SFTP accounts that go through Globalscape.

Overall, it is a good solution. Just make sure that it matches your auditing requirements.

I work for a local government, which is a pretty big organization as there are a lot of cities within the county. We do the file transfers for the county. It started off with SFTP only and then we managed to integrate our internal file transfers and everything else. From there, it has grown a lot more. We had one site originally, and now we're up to seven FTP sites.

We mostly use the software to interact with the outside world. Anything that comes in or goes out of our organization goes through our servers. Internally, because we have a lot of different systems, including mainframe, AIX, et cetera, and some systems don't speak to each other. For example, the mainframe doesn't have SFTP capabilities to communicate with AIX. We are the system in the middle that is involved in those transactions. For example, the mainframe will push out a file to us and then we will use or create a Globalscape script to push out that file to whichever server or file share it needs to go to.

The solution helps us a lot. If we didn't have it, and instead had a plain FTP solution, that would require a lot of other people to do extra tasks, including programming, to get files from point A to point B in a certain way. It results in huge time savings for our organization because a lot of the work is done by Globalscape, making it seamless to everybody else. If we didn't have the software, it would definitely require a lot of programmers to do a lot of work to create programs to get things done. Having a programmer write a program takes a long time. With Globalscape, all of that is managed in the background.

It also automates the submission of regulatory documentation. We have dozens of jobs that send out information on a weekly and monthly basis. It definitely makes it easy to send that data out to the people who require it at a specific time. It's really a set-it-and-forget-it, which is great. You set up a timed event or an ad hoc event that depends on when a file is uploaded. We set up a schedule and that was it. We don't have to tinker with it unless there's a change in a remote server or a server path.

It has reduced our workload. Unfortunately, during the pandemic, the quantity of data transfers has increased enormously mostly because we had to shift from in-office, paper delivery to an almost 100 percent online presence. Initially, there was a lot of work creating accounts and setting up a lot of new processes, but thankfully the software allowed us to do that. And it has been robust enough to handle the amount of data that we have needed to transfer on a daily basis. It does save us a lot of time.

Globalscape has a lot of good features. It's pretty easy to manage, once you understand the product and how it works.

The ability to map users to a virtual folder is excellent because server storage space is expensive compared to NAS or other types of storage solutions. Being able to map a user's home folder to a network location that is not in the home folder is a major advantage. There is a lot of data that we are not able to store on our servers because our servers are only transitory. The files do get deleted, as part of our rules, because otherwise we would run out of space.

The other thing is that the Advanced Workflow Engine it comes with is brilliant because it allows us to create scripts and perform behind-the-scenes jobs that would otherwise require a third-party solution. For example, somebody wanted a list of the emails of users who work for our organization. Using that tool, we were able to grab the information from Active Directory, process it, create a ZIP file, and then push it out to the person who needed it. That type of function generally does not exist in a plain FTP solution. You would have to create a special code on the outside to get all that other stuff done in the background. With Globalscape, we can get all of that done in one package.

In addition, the reporting is excellent. They keep on augmenting the software with more features for security and compliance when it comes to integration with third-party products, of course, but it also has the ability to scan files for viruses as they come in and go out, which is a great feature.

Globalscape also secures sensitive data inside our network so that only verified users have access. Whenever somebody asks for an account, we always find out what the data is for. Based on that, it's either stored locally on our servers or in a secure network location that is behind firewalls. Unless you have access, there's no way you can get access to those files. Because we are a local government, we also have to deal with police files and Corrections Department data. And of course, a lot of employee data goes through our servers, including Social Security numbers. That's very sensitive information and we make sure that data is delivered securely or kept in a secure location. Having the data secured inside our network is definitely important to us. That is why we host it internally. Although we're migrating stuff to the cloud, having this set up locally allows us to maintain security compliance.

Our security office is satisfied with the work that we do and the capabilities that we have for ensuring that all the data that gets transferred to us is clean. We cannot afford to have a virus come in and hit us randomly over the network.

Another nice feature is the centralized platform for the management of file transfer operations. It's very simple to use and everything is in one place. As long as you know what you're doing, it's pretty straightforward. Creating user accounts, virtual folders, and jobs are all very straightforward.

There is only one thing that they need to figure out, as of my last conversation with their engineers. There are two ways to install Globalscape: as a standalone server or as a high-availability server, either Active-Active or Active-Standby. We are currently using standalone servers. That means if we want to upgrade the software, I shut down one of the two back-end servers, upgrade the software, make sure everything is correct, and then turn traffic back on to that one. I then proceed to upgrade the second server. With their high-availability solution, that is not a possibility. Both servers have to be shut down to perform the upgrade. We're a 24/7 shop. We don't have a window where we can have downtime. If we have to shut down both servers, that shuts down FTP, period, and we're down. We cannot be down, at all.

Our solution is to have two primary active nodes and two nodes in standby. Our upgrade path is going to be going from two standalone to two high-availability servers, with two additional servers on the back end just sitting there doing nothing, so when the time comes that we have to upgrade, we will be able to shut down the main high-availability cluster, perform the upgrade, and then switch back. That's a pain. And that's the only thing that could be improved, because once we set up the high-availability version, it's going to be a little more tedious to do a software upgrade.

As time goes on, it's very important to keep the software as up-to-date as possible because there are enhancements for security protocols that they've included. The lack of ability to upgrade would be a showstopper for us if we were running in the minimal high-availability mode.

Having high availability is also important because it's cheaper for licenses and it's easier to manage those servers, versus two standalone servers. But that makes our upgrade path the only downside.

As an organization, we've been using Globalscape Managed File Transfer for longer than I've been managing it, and I've been managing it for over five years. 

It's very stable. We rarely have any issues with the software. We've had minor bumps only when performing upgrades. And those weren't the fault of Globalscape. They were the result of poor programming on our end. 

It's pretty self-sufficient and there isn't much we need to do to it, and that saves us a lot of time. We don't have to go in there every day and make sure everything is running or run reports to see if there are any jobs that have failed. That rarely happens.

We could scale it a lot more than we have. It is easy to add more servers. If our load were to increase, it would be pretty simple to add an additional server to the environment and have it handle the additional traffic. Scaling it is probably one of the easiest things to do. You just spin up another server, install the software, and have everything synchronized and you're up and running.

We have just about all of the modules that Globalscape offers and have used all of their features to their full potential.

We don't have any bottlenecks currently. If that did become an issue, we could easily add an additional server and be done.

Their technical support has been great. I've contacted them during business hours as well as after business hours when we have had a problem after-hours. They have been able to resolve the problems very quickly, for the most part.

Sometimes, there are problems that level-one support is not able to resolve and they will move it up quickly to the next level, without us having to wait for a long time. I can't complain about the support that they've provided to us.

There is a learning curve when it comes to using Globalscape Managed File Transfer, but when we have run into issues, their support team has been great in getting us the answers that we need. When we get a strange request that we are not sure how to do, they're able to fill in the gaps. They have all that knowledge and have worked with other companies that have had those issues before.

We had people logging in using a domain/username, but Globalscape doesn't require that. We had an issue with that and I contacted their support. They looked at the issue and they were able to provide a fix for it immediately.

Positive

I wasn't here for the initial setup of the solution, but I was here when we went from one server on one box to having two load-balanced servers. I did all that migration, moving that SFTP server to the new environment and collapsing our internal FTP.

Moving the first server, the SFTP, was easy, because it was a matter of moving one backup configuration and restoring it on a new box. We did hire them for consulting on the setup to make sure that we were able to do high-availability. 

Collapsing our internal FTP was interesting because that was running on Microsoft FTP. It was a "landfill." People dropped files and forgot that they were there and cleaning up that mess was a little bit of work, but that was just because of the way it was set up. I was able to manage the migration of all of that stuff over to the Globalscape infrastructure. Cleaning the data and making sure we kept the accounts we needed to keep was a task we had to do. Once we had it all set up, we were able to set up the site for our internal FTP, which is now both internal and external, and move everything over to the new server. It took a little while to clean up, but on the Globalscape side it was pretty straightforward.

As far as maintaining the solution goes, we currently have two people involved.

Globalscape is not cheap, but you get what you pay for. The cost is worth the value of the product. What you're getting is a good, stable solution that does a lot. We don't run the basic version, we run the full enterprise version of the software that has all the bells and whistles. It has all the features that we need and the pricing is fair, given what offers. I think it's a pretty good deal.

We could go with something cheaper, but then we might not get all the updates that we need or all the additional stuff that they're constantly innovating into the product. That's a lot of value added. The analogy would be if Windows stayed with Windows NT, for instance. That would not be good. Windows keeps on moving, progressing, and making things better, and so does Globalscape. Globalscape looks at what customers need and, based on that, they keep on adding features and functions that are useful and that make our jobs a lot easier and provide a lot more automation.

I believe our organization did evaluate other options. I think they chose Globalscape because of the automated features it has available. A lot of the other solutions are just plain FTP servers. Back then, they didn't do a lot of automation. A lot of them are now trying to add those features because they see them as necessary for a lot of businesses. Back then, Globalscape was one of the very few companies that had that type of integration.

On my own, I've demoed a few of them and they're not as straightforward as Globalscape. Of course, I'm used to Globalscape, but they don't have a lot of the bells and whistles that Globalscape has.

It's not that important that it's designed for Windows because we work with different systems. But it is nice that it is designed for Windows because it's easier to manage than using the command line or relying on different versions of Linux. Windows is a more standardized platform and we know it will operate in a certain fashion. With other OSs, it would be a lot more expensive or a lot more challenging. With Linux, there are so many variants out there that it's impossible to say they're all standard. It might work perfectly on one but not work on another one. Having Globalscape on Windows is great because it's used everywhere and easily manageable. It's a good pairing.

If it weren't for Globalscape's automations, it would be a lot more difficult to use. It has been a blessing to have those features available to us to make our jobs a lot easier.

It's our managed file transfer platform that we mainly run for the folder monitor event rules. We've got about 3,000 event rules and about 1,000 users.

We have regulatory information that flows through it. From a managed file transfer perspective, we move a lot of files and this is just another file transfer for us. But the reporting around compliance has been good for us to ensure that we're moving things securely.

By going with Globalscape, we have been able to decommission Sterling B2B Integrator, Connect Enterprise, MOVEit, and soon, ExaVault, and that has streamlined and standardized our processes, drastically, and has helped with cost savings.

The most valuable features are the scheduling and folder monitor capabilities. It fits well with our workflows, as we strive to be event-driven rather than scheduled. Event-driven fits well with folder monitoring.

The fact that it is Windows-based was a huge factor for us because most of our endpoints are Windows-based. And the ability to configure it means standardization is available with the product.

Also, the ARM (Auditing and Reporting Module) database has been a very important feature for us in terms of research and reporting. When a client asks us if their file has been transferred, it's very important that we have that reference. And from the compliance and records-management perspectives, it's great to have all of that information.

The solution’s centralized platform for the management of file transfer operations is also great. The administrative interface is locally installed and remotes to the servers and that is important for us.

There is also the fact that it allows us to use automated scripts. We were doing that in our other platforms as well, but Globalscape has the edge. PowerShell integrates naturally and it has an advanced workflow editor built-in. It has reduced workload to a certain extent, but that just comes down to standards more than anything, and how we implement transfers. I don't know how to put a number on the time saved, but hypothetically it would be about 20 percent.

I do have some complaints or concerns around the centralized platform for the management of file transfer operations, and I know that they're working towards a better solution there. At its core, it's a good feature, but needs some improvements. I would like to see a web interface so that there is universal support across versions, because we have test and production environments that aren't always in sync. It would be nice to have one administrative interface to access both.

The other aspect is not to be limited to the configuration of one server at a time, because we have multiple administrators. Someone might want to do work on one of the nodes in our cluster but isn't able to do that because other administrators are leveraging a different node.

Also, as a result of working on different versions of the product, I have found that some of the features that were in older versions have been forgotten in newer versions. One of them is how you copy and paste conditions within event rules, and how they're placed. In an older version, 7.4.13.15, you are able to copy a condition and paste it after the selected condition, but in version 8 and above, when you copy a condition, it has to go at the top of the rule.

The other thing that I can think of is key management. Within the PGP or SSH management console, when adding a key in older versions, that dialogue would refresh and put the new key at the bottom so it was easy to find. In new versions, it does not refresh. You have to exit out of the dialogue and re-enter it and it's not shown at the bottom, so you have to dig for it.

I've been using Globalscape Managed File Transfer for about five years.

We've had some issues in clustering and with the high-availability functionality, as far as file shares go, but I believe they have been resolved in newer versions.

As long as it's configured as an HA solution from the get-go, it's very easy to add nodes. If you start it as a standalone server and want to upgrade to a cluster, it is not really great, but that's also on the roadmap already and will hopefully be improved.

The solution has a pretty large footprint within our company, so any increased use would be based on company growth.

In the past, the tech support that we got from Globalscape was very good. As of late, it has been far less impressive in response time, the knowledge of tier-one agents, and the willingness to escalate to tier-two and three. Lately, it's been really disappointing.

Neutral

We had a few managed file transfer platforms before. One was Sterling B2B Integrator. The Globalscape interface is more user-friendly, but as with anything, once you're familiar with the less user-friendly solutions, they take about the same amount of time to use.

The initial setup was pretty straightforward, and I know that it has only gotten easier in newer versions.

We used Globalscape's Quick Start Service. It was a learning process, and it took about eight hours because we went through a lot of training as we were doing it.

In terms of an implementation strategy, we had some of our own standards for naming things within the product, but we went with the advice of HelpSystems when it came to resources and infrastructure to be applied.

For maintenance and operations, we have nine FTEs. Their responsibilities include implementing and configuring, troubleshooting and managing/upgrading.

The ROI from our early solution, Connect Enterprise, was great. But in comparison to the others, like IBM Sterling File Gateway and Sterling B2B Integrator, the return on investment from Globalscape is far higher. There is a much better return.

A large factor in our decision to go with Globalscape was the price. Obviously, that's everybody's first go-to.

We looked at a few options, but we already had an instance of Globalscape within the company, one that was used on a much smaller scale, and that's part of what sent us down this path.

The differences really came down to the user interface and scalability.

My advice would be to implement naming standards early for the policies you apply.

We have several use cases. We use it for exchanging files. We use it as a file or SFTP type of storage for B2B type of exchange with customers. 

We also use a lot of rules to transfer files from internal to external systems or from external to internal systems and archive the files. We use a lot of event rules. Our usage is heavy, and we have around 3,000 to 4,000 rules. We sometimes use it for PGP encryption. We also use it when zipping and unzipping files. These are all part of the rules.

In terms of deployment, it is on-prem. We have multi-region on-prem.

It is our primary managed file transfer capability. On an annual basis, we transfer terabytes of data through this. It has saved a lot of time. It is kind of a self-service, which saves time. Previously, IT involvement was required, which always took more time.

It secures sensitive data inside our internal networks so that only verified users have access. There is a module called the DMZ Gateway module that terminates any external connection so that we don't expose our data to the external network. It doesn't expose any of our data in the backend.

It provides a centralized platform for the management of file transfer operations. The data address is encrypted. So, the storage is only system-accessed. There is no way for people to access that storage. Everything is managed with user-based access and controls. We do have a lot of controls in place, and we have all the details of who is accessing the files.

It enabled us to decommission other solutions. We decommissioned Cyclone for several reasons. The main reasons were that Globalscape was cheaper, and we could cover all the use cases.

It allows us to use automated scripts. This functionality is very important for us because sometimes, we can't do with out-of-the-box functionality, and we need to do some custom scripting. The good thing is that they're allowing VBScript, Powershell, and I think they even allow us to use Amazon CLI.

Our operations have definitely become more efficient because of the automation. We can see a lot of alerting. We can see everything in one place in a dashboard. That has improved operational efficiency a lot. There is still a lot of scope for improvement, but as compared to previously, we have a significant improvement.

It connects to popular ICAP servers to perform antivirus and data loss prevention functions. We have SSL-based, certificate-based management, and we have user-based authentication. We only open the HTTPS port to the outside world. We don't open any other ports. From Globalscape, we connect to the outside or external connection through SFTP or Amazon S3. We have different policies.

It has enabled us to reassign resources who were writing custom file transfer scripts or compiling file transfer audit reports to other tasks. We are definitely able to reuse some bandwidth from this.

Its ease of use is most valuable. Especially for the configuration of the rules, we don't need to have any scripting knowledge. Previously, we used to have a lot of custom scripts to transfer these files. Now, it's all managed in one place, and it's like a self-service. It's saving a lot of time for us.

The auditing module is another valuable feature. We have subscribed to the auditing module, and it gives end-to-end information about who downloaded and who uploaded a file. It provides all that information about who is using a file.

Its security features are good enough. In case of any failures, there are a lot of out-of-the-box reports.

It is designed for Windows, which is important for us because we have a lot of use cases around LAN. They will also come with support for Linux.

We want to have some capability for cloud-based. They seem to have purchased a different company recently, and they seem to have a cloud-based option. 

We also need some capability for faster transfers and large file transfers. If we want to transfer a terabyte file, it is not capable of doing that right now. They say it is possible, but we are not able to do so with our environment.

I have been using this solution for almost 10 years.

Because of the on-prem deployment, we saw several hiccups here and there in terms of stability, but overall, it is okay. It also depends on the capacity and the bandwidth. There are also several other factors. From the cloud perspective, I think it is okay.

We can add more nodes. So, based on the type of load, we upgraded and added a couple of nodes in the EMEA region. Overall, it is scalable.

We have three regions. We manage 24/7 with five to six resources across the regions. From the solution perspective, we don't need to increase the size of the platforms, but we need to optimize overall operations. We are spending a lot of time on patching and upgrading. So, if we go for one instance of cloud, the effort will reduce.

Their technical support is good. There are two or three levels of support. Recently, they have assigned a Technical Account Manager (TAM). From the response perspective, overall, I'd rate them an eight out of 10.

We were using Cyclone. We switched because of two factors. One was the size. There were too many servers, and it was very less from the cost perspective. It also covered a lot of use cases, such as event rules.

It was straightforward. It was a simple installation. We had some internal validation processes for deployment. Otherwise, Its implementation takes a couple of days. If you have all the servers ready, it is quick to install.

We worked with Globalscape. Globalscape helped us, and their architect confirmed our deployment options. It was a simple process.

I don't have an exact number. We definitely pay one-tenth of the cost as compared to our previous solution. That's a significant difference, and it is covering all the bases.

We are paying around 30K per year.

We tried IBM Aspera. It is for big data use cases. We evaluated it for terabyte type of data, but we didn't move forward with that. I think we've got it for one year but in some other group.

Aspera's price was high. Globalscape was one solution covering all the use cases, and that was a key factor for us. From a support perspective, we didn't want multiple vendors for each use case. Globalscape already had a module for our use case. That was the reason for going with Globalscape.

I would definitely recommend this solution. Being in the middleware space, I work on several other technologies within our group. Oracle has an MFT, and Amazon is also planning to have the managed file transfer, but I recommend Globalscape. It is in the top quadrant from Gartner's Quadrant perspective, and they have recently acquired a lot of small companies in different areas. They are okay in terms of the product roadmap.

We don't use Globalscape to automate the submission of regulatory documentation, but there are connections to FDA and CFDA. We use this as a transport tool but not as a submission tool. We do have the FDA and email connections.

The automation of file transfers has reduced the workload but it depends on multiple factors. It also depends on the bandwidth part. There are a lot of features, but when we are transferring across our client base, it can be a little bit slow. It is based on the type of protocol. They have some modules, but we haven't yet used those UDP-based transfers.

Its connection to popular ICAP servers helps inspect content for sensitive information, such as credit cards, and it has some advanced security modules, but we never used them. It automatically does advanced checksum and several other redundancy checks.

As a solution, I would rate it a nine out of 10. There are a few areas they need to improve on. They recently came up with the cloud option and different deployment options, but we haven't used those yet. We need to use those options.

It is easy to set up, stable, and secure. They have good customer support.

Previously, we had multiple tools for file transfer. With GlobalSCAPE, we can meet all the business requirements. It has multiple options like folder monitoring and scheduled jobs that make it a real time file transfer solution.

It is great tool. GlobalSCAPE needs to provide training or seminars to show its capability to customers.

We have not had any stability problems until now. It is very stable.

We had no issues with scalability.

I would give technical support a rating of 10/10. They are very knowledgeable.

We have used many solutions, mostly scripts, which are hard to edit and debug.

The setup was very straightforward. Setting up basic file transfers is very easy. Customizing advanced workflows is complex and requires more experience.

They offer fair pricing with all the capabilities.

We did look at alternatives, but I cannot name them.

It is wonderful application which can take care of your file transfer load. There is no need to monitor it daily. It is very stable.