It has been amazing. I don't know if it is how they manage and control their releases. This has become important, as you can imagine. With having very large communities of users and everybody in the company using the system, most systems have become mission-critical. We have had no outages that weren't unplanned. It doesn't mean you don't iterate on applications or work on improvements, but in terms of unplanned outages, it has been very small.

VINYL has been highly stable so far.  We haven't had any issues. 

We have found the stability of the VINYL platform to be extremely reliable. We have had some point outages at times, where a plugin or something that interfaces with the VINYL platform went out on its own. Then, we experience that the employee portal or the app is down. After investigating, we found that the VINYL app was functioning perfectly. The challenges came into play when an integrated piece went out. So, I have no examples when the VINYL platform itself was out and causing business problems for us.

In terms of stability, we've had no issues.

Stability is not an issue. We run it in AWS and we've never had any stability issues with it at all. We haven't had instances of it going down. It's possible that has happened, but nothing has been brought to my attention. Typically, if there was a problem, I would hear about it.

In the past six months, Vinyl has had 100% uptime. This product is used 24/7/365.

There have been no stability issues. It's all in the cloud. We've never had any outage. It's very stable. 

So far, it has been very stable. Any issues that have arisen have been quickly fixed. We have great auditing features, allowing us to see whatever data we may need and how/when/why it was changed.

I haven't noticed any issues with it. It seems to be a very solid product. I don't see it going down ever. I don't hear complaints of that from anybody. It's been a very stable product for us.

It has been extremely stable; no issues whatsoever, thus far.

The stability of VINYL is pretty amazing. It just works.

The solution's very stable. We haven't had any major hiccups, downtime or outages with it. We've thrown some things at it. If you get a circular job that's kind of stuck in itself you might have a problem, but that's more the fault of the developer as opposed to the platform.

There have been no stability issues. It is a very stable platform.

My impression of the stability of Zudy VINYL has been fantastic. I used to have hundreds of bug reports a week. I would find all these little micro things, and I would say, "Oh, goodness sakes, when I'm on this device and I do this, that crashes or that does." I'd get things back from my customers, but that has gone so far down. You don't notice pain when it's gone. You only notice pain when it's there. Until you asked me the question about stability, I'd forgotten how much pain I had, previously, trying to get all these systems and implementations deployed and how many problems it caused. This has been very stable and I've been very happy with it.

We have had no performance issues with it.

The VINYL platform is very stable. We've had minimal issues, and whenever we do, we're able to fix them relatively easily.

It has given us good performance handling APIs, handling different data sources, handling different file structures, and handling email servers. The performance depends on our servers but it's quite good.

The Zudy VINYL platform is consistent. We haven't had any issues with it going out of service or functionality where it should have been available and it hasn't been. It's stable.

We don't really have any crashes, so that's always good. You can get an error if you're trying to do too much at once, before the system can catch up. That's understandable. 

If we do find anything that turns out to be a real error, it's super-quick to go in and figure out what the error is. You make a pretty simple change to correct it. The different layers within the platform for each application are pretty linear. You've got the same three layers: the cosmetic layer, the business-rules, and your data layer. It's always going to be somewhere in one of those layers that you find the issue or figure out where you need to make a change. You're not having to really go anywhere else to do that. It's pretty centralized.

I like the stability of VINYL because I can see them always increasing, changing, making it better. I've worked with it for three years now and what it used to be in the first year to what it is now is a world of difference. They've taken our suggestions, as users, and moved the platform in the right direction, fixing those problems and making it better. As long as they keep doing that, I see a long life for the product.

We have not encountered any stability issues.

It's pretty stable. It just sits on top of your stuff and it does a good job of maintaining the connection between the two. I've never had an issue where it breaks or the connection is lost for some reason. When you're working between two different systems it's tricky but that's not really a VINYL issue, it's just hard to get two machines to talk to each other sometimes.

Once or twice, when a new version of VINYL comes out, it has had a negative impact on a feature. However, we do everything in a test environment. Unless we miss something in test, we don't go live with it if it isn't perfect. Zudy hasn't had too many stumbles along the way, but there have been a couple times, and it's been minor.

No issues with stability. It is very much a stable product.

We have never really had any downtime with Vinyl at all. We actually host this in our own environment as opposed to a cloud environment, which is their typical model. We have been very pleased with the stability of the product.

It's pretty much a stable product. I haven't seen many issues with it. I do know that there have been some smaller issues with some new people that are also starting to work on it, and their name being in the system, but I haven't been involved in that part of it.

It's never been down. The only time we've had issues is if we change something, and then it messes something up in the back-end. But that's always been our fault. Generally, VINYL has really helped us to find our own user errors. We've found more of our own problems than we've ever found with VINYL.

For us, it is very stable. We can host it internally and in the cloud. It is secure and accessible. We have been using this product for about a year and a half, and we have only seen improved sustained stability and usable.

It is a stable product for the most part, but if there are any issues their developers are instantly available to address them.