Zaizi Limited

Managed Open Source Website & Portal Service

Scalable open source website and portal service based on either Drupal or Crafter CMS. The service is configured for clients needs on either client hosted infrastructure of public cloud (AWS/Azure). Optional DevOps / DevSecOps service provides continual enhancement support and we provide integration services with other systems and services.


  • Highly configurable
  • Interoperability build in
  • Mobile ready and advanced HTML5 features
  • Web Services Built-In
  • Better Support For Accessibility
  • Industry Standards and Multilingual Ready and Open Source
  • Quick Edit and Easy Authoring
  • Manage Your Configuration
  • Loading Speed
  • JavaScript Automated Testing


  • Scalability
  • Drupal Community Support
  • Open Source Technology and Cost Saving
  • Wide range of out of the box features
  • Easy Integrations with 3rd Party Applications
  • Web Content and user management
  • Efficiency and Maintainability
  • Performance
  • Flexible Content delivery to any channels
  • Enhanced Security features


£1000 per instance per month

Service documents


G-Cloud 11

Service ID

7 3 4 8 0 7 1 5 4 5 8 4 6 6 7


Zaizi Limited

Andrew Hawkins

0203 582 8330

Service scope

Software add-on or extension
Yes, but can also be used as a standalone service
What software services is the service an extension to
Drupal and Crafter can be used as a standalone service. Due to its open source heritage both can be integrated with a number of 3rd party applications such a document management systems, ERP systems, EHR systems etc. They also offer Rest API interface allowing 3rd Party to integrate with ease.
Cloud deployment model
  • Public cloud
  • Private cloud
  • Hybrid cloud
Service constraints
Basic service provided during core office hours (09:00 - 17:00). Higher 
availability and resilience is available according to customer requirements.
Typically all maintenance schedules will be performed out of core office 
System requirements

User support

Email or online ticketing support
Email or online ticketing
Support response times
Zaizi offer Level 3 support service supporting the application, platform and infrastructure. We operate under an ITIL model incorporating a Continual Improvement and automated testing approach. Support is offered for: Core Business Hours 9:00 – 17:00 Extended Business hours (not weekends and Bank Holidays) Additional 2nd Level Support is provided at an extra cost with 24/7 Support Via UK and Overseas Support Desk. Zaizi prioritises all issues raised aiming to resolve within agreed response and resolution times, typical response times offered. P1: Response 1hr, target resolution 4hrs P2: Response 2hr, target resolution 24hrs P3: Response 4hrs, target 5 business days
User can manage status and priority of support tickets
Online ticketing support accessibility
WCAG 2.1 AA or EN 301 549
Phone support
Phone support availability
24 hours, 7 days a week
Web chat support
Onsite support
Yes, at extra cost
Support levels
Zaizi offer Level 2 and Level 3 support service supporting the application, platform and infrastructure as required. We operate under an ITIL model incorporating a Continual Improvement (CI) and automated testing approach. Support is offered for: Core Business Hours 9:00 – 17:00 Extended Business hours (not weekends and Bank Holidays),24/7 Support Via UK and Overseas Support Desk Zaizi prioritises all issues raised aiming to resolve within agreed response and resolution times, the table below provides the typical response times offered. P1: Response 1hr, target resolution 4hrs P2: Response 2hr, target resolution 24hrs P3: Response 4hrs, target 5 business days
Support available to third parties

Onboarding and offboarding

Getting started
Zaizi will provide a onsite training for the solution which will be chargeable at our standard SIFA rates. In addition we would usually recommend clients to undertake a number of the Drupal training programs that are a available online. Training requirements will be established at the outset of the on boarding process. Zaizi will provide user documentation for the service
Service documentation
Documentation formats
  • HTML
  • ODF
  • PDF
  • Other
Other documentation formats
Open Standards
End-of-contract data extraction
Zaizi will support the extract of user data through a T&M charged off-boarding process. The exact details will be determined by the quantity and security level of the data and other client specific requirements. We expect to start the process three months prior to contract end where extension is not anticipated (subject to client availability)
End-of-contract process
Off-boarding is standard part of our offer but is chargeable under our standard SFIA rate care and would be finalised once contract end and migration is confirmed with the client

Using the service

Web browser interface
Supported browsers
  • Internet Explorer 9
  • Internet Explorer 10
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
Application to install
Designed for use on mobile devices
Differences between the mobile and desktop service
The only difference on the mobile application is the User Interface is different.
Service interface
What users can and can't do using the API
A service endpoint can be up and running in a few minutes, by a few clicks - enabling few modules and selecting what resources to be exposed. The REST module supports both basic and cookie based authentication; it supports all safe HTTP requests & methods. Some of these methods are safe, they are read-only. Hence they can never cause harm to the stored data, because they can't manipulate it. The safe methods are HEAD, GET, OPTIONS and TRACE. All other methods are unsafe, because they perform writes, and can hence manipulate stored data.
API documentation
API documentation formats
  • Open API (also known as Swagger)
  • HTML
  • ODF
  • PDF
  • Other
API sandbox or test environment
Customisation available
Description of customisation
Both, Drupal and Crafter are open source technologies with widely available documentation which provides clients with the ability to customise their service. The extent of customisation would be available to the entire services provided by Drupal or Crafter. Users would be able to perform CRUD(Create, Retrieve, Update and Delete) operations.
For example on implementation if users found that only a limited amount of resources or actions were exposed, and they required more actions and resources , they would be able to to edit and select more resources and actions as and when required. A trained user or developer would be able to make customisations.


Independence of resources
The solutions that Zaizi provide are scalable based on demand. The solutions we provide scale to ensure high performance. We have a high level of security in place to ensure separation of service between clients. When on boarding new clients Zaizi have an internal process to assess whether additional resources and capacity is required to provide the service we supply. For concurrent usage multiple nodes can be introduced and load balanced.


Service usage metrics
Metrics types
The application provides an number of out of the box basic metrics. Dependent on the clients requirements, Zaizi can customise the system to show the required metrics.
Reporting types
  • API access
  • Regular reports
  • Reports on request


Supplier type
Reseller providing extra features and support
Organisation whose services are being resold
Amazon Web Services, Alfresco, Talend, Mulesoft, Ephesoft

Staff security

Staff security clearance
Conforms to BS7858:2012
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least once a year
Penetration testing approach
Protecting data at rest
Other data at rest protection approach
Our solution is based on the AWS Cloud. AWS adheres to independently validated privacy, data protection, security protections and control processes. AWS is responsible for the security of the cloud; customers are responsible for security in the cloud. customers control their content (where it will be stored, how it will be secured in transit or at rest, how access to their AWS environment will be managed). Wherever appropriate, AWS offers customers options to add additional security layers to data at rest, via scalable and efficient encryption features. AWS offers flexible key management options and dedicated hardware-based cryptographic key storage
Data sanitisation process
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
Equipment disposal approach
In-house destruction process

Data importing and exporting

Data export approach
Zaizi would take a data migration approach to this to export data out of the system using our standard tools and processes. This would be billable, please refer to SFIA Rate Card for pricing.
Data export formats
  • CSV
  • ODF
  • Other
Other data export formats
Open standards
Data import formats
  • CSV
  • ODF
  • Other
Other data import formats
Open Standards

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Bonded fibre optic connections
  • Other
Other protection between networks
We protect data between networks by applying firewall rules, IP based access restrictions, multi factor authentication and secure access devices. What will be used for each client is dependent on clients requirements.
Data protection within supplier network
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Other
Other protection within supplier network
Additional ways Zaizi protect their data within our own network is by two factor authentication, Distributed Denial of Service (DDOS) Mitigation, IP Based access restriction, real time network monitoring, Man in the Middles(MITIM Mitigation, Internet Protocol Spoofing, Port Scanning .

Availability and resilience

Guaranteed availability
Zaizi provide high availability and disaster recovery using multiple level availability zones. The SLA’s are decided with clients based on their requirements and levels of support. The key factors when deciding these will be recovery time objectives and recovery point objectives.
Approach to resilience
Zaizi has identified critical system components required to maintain the availability of the system and recover service in the event of outage. Critical system components (example: code bases) are backed up across multiple, isolated locations known as Availability Zones. Each Availability Zone runs on its own physically distinct, independent infrastructure, and is engineered to be highly reliable. Common points of failures like generators and cooling equipment are not shared across Availability Zones. Additionally, Availability Zones are physically separate, and designed such that even extremely uncommon disasters such as fires, tornados or flooding should only affect a single Availability Zone.
Outage reporting
Zaizi use a number of monitoring tools based on clients requirements to detect and alert for outages. We use technologies such as, but not limited to Cloud Watch, Nagios, Pingdom and custom scripts. Alerts can be provided in a number of ways, but not limited to public dashboards, an API, email alerts. This is all dependant on customer requirements and what fit best.

Identity and authentication

User authentication needed
User authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Limited access network (for example PSN)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels
There are roles and permissions that are assigned to users, restricting what access, rights and information they can have access to.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Dedicated link (for example VPN)
  • Username or password

Audit information for users

Access to user activity audit information
Users contact the support team to get audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
Bureau Veritas
ISO/IEC 27001 accreditation date
What the ISO/IEC 27001 doesn’t cover
The following is excluded from the scope of Zaizi’s Statement of ISO 27001:2013 Statement of Applicability: A.11.2.4 – Equipment Maintenance Reason - No fixed asset has high-value (i.e. >£3k) are depreciated on purchase and have no residual value after 3 years. Items considered beyond economic local repair are the subject of straight replacement from new. Servers are leased and cloud-based and out of scope of this requirement. A.11.1.5 – Working in secure areas. Reason Zaizi does not operate a system of permanent secure areas. Secure area working is restricted to customer sites in accordance with current HMG information classification guidelines. Working on-premise is constrained to the HMG classification of OFFICIAL. A.14.2.7 – Outsourced Development. Reason - Zaizi does not outsource the development of software (it is a software development house).
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications
Any other security certifications
Cyber Essentials

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
ISO/IEC 27001
Information security policies and processes
We are fully ISO27001 assured and follow standard procedures. Our processes are reviewed internally at management level at regular intervals during the year, including our Chief Exec and CSIO. Incidents are managed by our CSIO and by the process alerted to the Management team

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
Configuration management software is installed when new servers are provisioned. These tools are run on all hosts to validate that they are configured and software is installed in a standard manner based on host classes and updated regularly. Only approved Systems Engineers and additional parties authorised through a permissions service may log in to the central configuration management servers.
Vulnerability management type
Supplier-defined controls
Vulnerability management approach
The service is delivered on the AWS public cloud. The vulnerability management sub-principle and related processes within AWS services are subject to audit at least annually under ISO 27001:2013, AICPA SOC 1, SOC 2, SOC 3 and PCI-DSS certification programs. These certifications are recognised by ENISA under the Cloud Certification Schemes. Zaizi implements full ISO27001 controls for the management and uses multiple sources (vendor, authorities and internet) to identify threats and then implement patches under P1 service request conditions.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
The Zaizi platform runs on the AWS platform. AWS deploys (pan-environmental) monitoring devices to collect information on unauthorized intrusion attempts, usage abuse, and network/application bandwidth usage. Devices monitor: • Port scanning attacks • Usage (CPU, processes, disk utilization, swap rates, software-error generated losses) • Application metrics • Unauthorized connection attempts Near real-time alerts flag potential compromise incidents, based on AWS Service/Security Team- set thresholds. Requests to AWS KMS are logged and visible via the account’s AWS CloudTrail Amazon S3 bucket. Logs provide request information, under which CMK, and identify the AWS resource protected through the CMK use.
Incident management type
Supplier-defined controls
Incident management approach
Incident management is either reported by the client or detected by our service desk and management tools. Once identified the incident is classified within our systems and managed within our SLA following full ITIL processes, with agreed escalation points and reporting to the client dependant on the level of severity. Upon request full incident reports will be provided for P1 events

Secure development

Approach to secure software development best practice
Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v3.0)

Public sector networks

Connection to public sector networks


£1000 per instance per month
Discount for educational organisations
Free trial available

Service documents

Return to top ↑