TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    ContentProtect

    Score3 out of 10
    N/AContentWatch in Salt Lake City, Utah offers ContentProtect, a web content filtering solution.N/A

    GoCD

    Score8 out of 10
    N/AGoCD, from ThoughtWorks in Chicago, is an application lifecycle management and development tool.N/A
    Pricing
    ContentProtectGoCD
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    ContentProtectGoCD
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Best Alternatives
    ContentProtectGoCD
    Small Businesses
    No answers on this topic
    Apache Maven
    Score9.1 out of 10
    Medium-sized Companies
    No answers on this topic
    Apache Maven
    Score9.1 out of 10
    Enterprises
    No answers on this topic
    Gradle Build Tool (Open Source)
    Score9 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    ContentProtectGoCD
    Likelihood to Recommend
    3.0
    (1 ratings)
    9.0
    (2 ratings)
    User Testimonials
    ContentProtectGoCD
    Likelihood to Recommend
    ContentWatch
    If you are looking for something relatively inexpensive to lock down specific computers, it would be a useful tool. If the computers themselves aren't too locked down, implementation and management shouldn't be too difficult.
    Incentivized
    Read full review
    ThoughtWorks
    Previously, our team used Jenkins. However, since it's a shared deployment resource we don't have admin access. We tried GoCD as it's open source and we really like. We set up our deployment pipeline to run whenever codes are merged to master, run the unit test and revert back if it doesn't pass. Once it's deployed to the staging environment, we can simply do 1-click to deploy the appropriate version to production. We use this to deploy to an on-prem server and also AWS. Some deployment pipelines use custom Powershell script for.Net application, some others use Bash script to execute the docker push and cloud formation template to build elastic beanstalk.
    Incentivized
    Read full review
    Pros
    ContentWatch
    • The client is relatively light weight and doesn't impact other applications.
    • The client isn't easily bypassed, so the user's are kept under restrictions.
    • The configuration is relatively simple and easy to deploy.
    Incentivized
    Read full review
    ThoughtWorks
    • Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
    • The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
    • Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
    Incentivized
    Read full review
    Cons
    ContentWatch
    • Our primary policy is a restricted list, so that does as advertised. We had one location that had blocks based on categories (adult, illegal, etc). We continually had issues with sites getting completely blocked due to unrelated content. For example, Yahoo had a beer ad on the page, alcohol was blocked, so Yahoo became blocked for the period of time that ad was displayed. We had this happen multiple times and eventually switched to a different solution at that location.
    • I've had issues with their cloud portal not working. I don't have to edit our configuration often, but on numerous occasions, i was unable to get the configuration page to load after login, sometimes for days. The platform just wasn't stable when I needed it to be.
    • We run many of our remote rooms as frozen (after logoff they reset to the image). This works fine most times, but when content protect needs a configuration change pushed down, someone needs to go 'thaw' the computers, download the updated configuration, and re-'freeze' the computer. It would be nice if that information was just dynamic from the cloud and didn't need to be pulled down.
    • The categorization used for policies is very limited and not flexible or easily customizable.
    • I could never get the usage reporting to work.
    Incentivized
    Read full review
    ThoughtWorks
    • UI can be improved
    • Location for settings can be re-arranged
    • API for setting up pipeline
    Incentivized
    Read full review
    Alternatives Considered
    ContentWatch
    At the time ContentProtect was selected, Forcepoint (Websense at the time) didn't have an inexpensive or cloud type product. The same can be said with Cisco, at that time. Recently, we have reevaluated and are going to be transitioning to Forcepoint's mobile client and removing ContentProtect from our environment. The cost is actually now less and we will be able to get both more dynamic control and also give us more detailed reporting on the traffic from clients.
    Incentivized
    Read full review
    ThoughtWorks
    GoCD is easier to setup, but harder to customize at runtime. There's no way to trigger a pipeline with custom parameters.
    Jenkins is more flexible at runtime. You can define multiple user-provided parameters so when user needs to trigger a build, there's a form for him/her to input the parameters.
    Incentivized
    Read full review
    Return on Investment
    ContentWatch
    • It was a relatively inexpensive and simple solution when we needed one relatively quickly, which is a positive. The inexpensive price has kept it in the environment.
    • The lack of reliable reporting has lead to the need for an alternate monitoring solution in a few cases. Network level reporting was used, which is a separate expense, configuration.
    • Time has been lost waiting on the portal and then troubleshooting support tickets when sites that shouldn't have been blocked have been blocked. It has resulted in changes for locations that needed dynamic category filtering as opposed to a finite list.
    • The blocking of sites based on add traffic or sub-sites (rather than just blocking that content like other solutions) has resulted in downtime during classes when those sites were listed in the lesson plan and had previously worked.
    Incentivized
    Read full review
    ThoughtWorks
    • ROI has been good since it's open source
    • Settings.xml need to be backed up periodically. It contains all the settings for your pipelines! We accidentally deleted before and we have to restore and re-create several missing pipelines
    • More straight forward use of API and allows filtering e.g., pull all pipelines triggered after this date
    Incentivized
    Read full review
    ScreenShots