AllyMatter VS CloudLinux

• Policy editor and version control
  A real editor built for policies: headings, lists, tables, images, callouts, and embedded PDFs and Word files, with auto-save and inline comments for reviewers. Every policy has one current, approved version. Version history shows every prior version, and Version Compare highlights each added and removed word with a count, so a reviewer sees exactly what changed. Restoring an old version goes back through approval before anyone else sees it.
• Multi-step approval flows
  Route each policy through the approvers you choose: up to five ordered steps, each with one or more approvers, in all-must-approve or any-one-approves mode. Approval is required for every document, so who wrote it and who approved it are always recorded. The document locks while a flow is running, rejections require a written reason, and a resubmission starts again from step one. Flows can be saved and reused, set on a folder, or overridden per document.
• Version-bound acknowledgments
  Send an approved policy to the people it covers and collect an acknowledgment that binds to that exact version, with the person's name, email, and the date and time. Every change goes back through approval and re-collects acknowledgment, so nobody is ever on record for a version they did not read. Completed acknowledgments are permanent: they survive the document changing and the person's account being deleted.
• Built-in E-Signature
  Some documents call for more than an acknowledgment. Mark a document for e-signature and collect signatures inside AllyMatter, with each signature bound to the exact approved version. Any change re-collects signatures, and the signed record lands on the same document log as everything else.
• Automatic Reminders
  When you send a document for acknowledgment, set a reminder cadence of one day, two days, three days, one week, three weeks, or a custom interval. AllyMatter chases the people who have not responded until they do, without anyone keeping a list.
• Review dates, expiry dates, and renewal
  Give any policy a review date, one-off or recurring every so many days, weeks, or months, so it comes back to its editor on schedule. Give documents that must not outlive their term an expiry date; when it passes, the document is hidden from its audience until it is renewed. Renewal without changes is a re-certification through the approval flow; renewal with changes takes the normal edit, approve, and re-acknowledge path.
• Tag-based access and visibility
  Every document is Private, Internal, or Public. Internal is the default, and tags decide who can see an Internal document: tag people and documents by site, department, role, or anything else, and access follows. Tags on a folder cascade to everything inside it. Admins manage who holds each tag, and people are notified when they gain access to a document.
• Public policy pages
  Publish any approved document to a public page from the same source as the internal version. One document, one current version, so the privacy policy or code of conduct on your website never drifts from the copy your staff acknowledged. Public pages live on your workspace address, or on your own domain on the Scale plan.
• Document log and audit trail
  Every document carries its own log: creation, versions, approvals with named approvers, rejections with their reasons, distributions, each acknowledgment and signature by name and time, tag and permission changes, folder moves, and comments. Admins also get a workspace-wide audit log. Both export as PDF or CSV, with filters respected.
• Packages: bring your own standard
  Build a package for each standard you are held to, whether SOC 2, ISO 27001, ISO 9001, HIPAA, GDPR, a state regulation, or an internal framework. List the requirements as line items, link the policies that satisfy each one, mark what does not apply with a reason, and see what is still missing. Export the package when the auditor asks. AllyMatter never supplies or maintains the content of any standard, and it never scores you.
• Consultant access with client ownership
  A standards consultant can run a client's policy program inside the client's own workspace. Their access is invited by the client, revocable at any time, and attributable in the log. The client keeps the account and the data throughout. Because only editors pay, a consultant seat costs the client one editor, and the client's reviewers and staff cost nothing.
• Notifications
  Approvals, rejections, acknowledgment requests, reminders, and new-access notices go out by email and appear in the in-app notification panel. Connect Slack on the Scale plan to receive the same notifications there.
• Roles and unlimited viewers
  Three roles: Admins run the workspace, Editors write and manage documents, Viewers read and acknowledge. Viewers are unlimited and free on every plan, so employees, contractors, and consultants who only need to read and acknowledge never add to the bill. Plans are sized by the number of Editors: up to 20 on Startup, unlimited on Scale.
• Working documents and embeds
  AllyMatter also holds the working documents around your policies: SOPs, procedures, and how-to documents. Embed Google Docs, Sheets, Slides, and Forms, Figma, Loom, Canva, Miro, Airtable, YouTube, Typeform, Calendly, Lucidchart, Draw.io, Excel Online, and CodePen with a slash command. Upload PDFs, Word files, and images directly into a document.
• Archive and deletion controls
  Choose whether your workspace archives documents or deletes them. In delete mode, a deleted document can be restored for 30 days before it is gone for good. Storage is 1 GB on Startup and 10 GB on Scale, expandable on request.

• Enhanced Server Stability
  CloudLinux uses its lightweight virtualization technology (LVE) to isolate each tenant on a shared hosting server, preventing any single user from consuming excessive resources and crashing the server for everyone else. This ensures consistent uptime and performance.
• Improved Security with HardenedPHP and KernelCare
  CloudLinux offers HardenedPHP, which patches old and unsupported PHP versions against known vulnerabilities, and KernelCare, which provides live kernel patching without requiring server reboots. These features significantly enhance server security posture.
• Resource Limit Management
  Administrators can set granular resource limits (CPU, memory, I/O, number of processes, etc.) per user account using LVE Manager. This makes it easy to manage shared hosting environments and ensure fair resource distribution among tenants.
• CageFS File System Virtualization
  CageFS creates a virtualized file system for each user, preventing them from seeing other users on the server, viewing sensitive configuration files, or exploiting server vulnerabilities. This adds an important layer of isolation and security.
• Wide Compatibility with Hosting Panels
  CloudLinux integrates seamlessly with popular hosting control panels such as cPanel, Plesk, and DirectAdmin, making it straightforward for hosting providers to adopt without overhauling their existing infrastructure or workflows.

Possible disadvantages

• Additional Licensing Cost
  CloudLinux requires a paid monthly or annual license on top of the base server cost. For smaller hosting providers or individual server owners, this additional expense can add up and may not always be justifiable compared to free alternatives.
• Limited to CentOS/RHEL-Based Systems
  CloudLinux is built on top of RHEL/CentOS and does not support other Linux distributions like Ubuntu or Debian. This limits its adoption for hosting providers who prefer or already run non-RHEL-based environments.
• Learning Curve for Configuration
  While CloudLinux provides powerful resource management tools, properly configuring LVE limits, CageFS, PHP Selector, and other features requires a solid understanding of the platform. Misconfiguration can lead to users being unnecessarily restricted or resources being poorly allocated.
• Potential Performance Overhead
  The additional layers of virtualization, resource monitoring, and file system isolation introduced by CloudLinux can impose a slight performance overhead on the server compared to running a bare, unmodified Linux distribution without these controls.
• Dependency on CloudLinux Ecosystem
  Adopting CloudLinux means relying on their ecosystem for kernel updates, PHP patches, and security fixes. If the company experiences delays in releasing patches or changes its pricing/licensing model, hosting providers may find themselves locked into a dependency that is difficult to migrate away from.

No AllyMatter videos yet. You could help us improve this page by suggesting one.

When To Use Cloudlinux On Your Virtual Private Server (VPS)

More videos