Agility CMS is a cloud-based content management system from the company of the same name in Toronto, Ontario.
$1,249
per month
Drupal
Score 7.0 out of 10
N/A
Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
OpenText Web CMS
Score 5.0 out of 10
N/A
OpenText
Web CMS (TeamSite) accelerates and simplifies the end-to-end digital content and campaign
lifecycle, from content creation and rich media management to omnichannel
publication, optimization, automation, commerce, and community. According to the vendor, with
TeamSite, users can:
Capture diverse digital
audiences with amazing brand experiences – Give customers and prospects consistent, high-quality brand
experiences across devices and channels, and foster closer…
N/A
Pricing
Agility CMS
Drupal
OpenText Web CMS
Editions & Modules
Starter
$1,249
Pro
$2,499
Enterprise
Custom
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Agility CMS
Drupal
OpenText Web CMS
Free Trial
Yes
No
No
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
Yes
No
No
Entry-level Setup Fee
Optional
No setup fee
No setup fee
Additional Details
33% discount on annual plans
20% off for non-profit
All plan include Unlimited Content Models + Types, Unlimited Locales, Unlimited API calls
All plans include full Page/URL Management, Page/Module composing, Sitemap management
—
—
More Pricing Information
Community Pulse
Agility CMS
Drupal
OpenText Web CMS
Considered Multiple Products
Agility CMS
Verified User
Administrator
Chose Agility CMS
Agility offers a balance of simplicity and capability that other platforms don't offer. User-friendly platforms like Word Press do not offer our company the ability to fully customize our site based on our goals, but more adaptable programs like Drupal do not offer the support …
1.- Agility can use for not expert people 2.- Agility have more bugs than Adobe or Drupal 3.- Slower than Adobe for certain functions 4.- Drupal is a very code tool 5.- Drupal has more features and security than Agility 6.- Drupal have a better community in where solve problems.
Agility is well suited for companies that want a balance of control and support. For major global site updates, these can be handled by Agility's support team, while minimal changes and updates can be performed autonomously by the company's own staff with ease. For companies that are interested in flexibility to reconstruct site structure or major global facelifts, Agility is less ideal because these changes must be handled and paid for through Agility support.
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
OpenText TeamSite is well-suited to large, enterprise-wide implementations where customization, content governance, and dynamic content distribution is needed or prioritized. It is probably not ideal for smaller sites with simple architecture and few resources to manage custom implementation.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
Overall, it's a solid package with the potential to offer much functionality with appropriate resources applied. There are a few issues with the authoring interface that OpenText should address before its a top shelf authoring experience.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
Support is always available and responsive when we email, responding right away that they are on the case, even if they are unable to solve the issue right away. Support will usually find the issue of our problem quickly and require minimal hand-holding, direction, or re-explanation from our team. They are knowledgeable about the platform and our instance and are able to run diagnostics with minimal information from us. When issues are resolved they always request confirmation that things are working as expected before closing out our tickets.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
Our technical resources engage with OpenText TeamSite so I don't have direct experience. However, critical issues that we need help with seem to get the attention they deserve without issue. However, training and user resources for business owner roles are a bit lacking and some annoying issues with the authoring interface should be addressed sooner.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
A few reasons to go with Agility CMS Product Capabilities Value for money Product functionality and performance Product roadmap Better Pre-sales experience
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
It offers more content editing features at a relatively low cost thus overall deployment is lower in cost. It has great customer support who are always there to support and answer to our needs thus making the process of deployment seamless at every stage and offering training for working with their product.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
We integrated with google analytics, now we have the proper comprehension of our audience data reception and behaviors - we've greatly improved on personalized marketing.
Quick publication of content across the main digital channels.
We run our digital campaigns swiftly.
We've maintained our brand consistency for three years.