Ixis IT Limited

Dynamic Development Sandbox Hosting

For projects that require a fast-paced development, testing and review process, with the ability to work on several features or fixes simultaneously, our dynamic multi-environment platform offers flexibility and scalability suitable for developers working with open source technology and applications.


  • 99.5% uptime
  • ISO 27001 & Cyber Essentials Certified
  • Dedicated isolated environments not shared with any other clients
  • Multiple environments for development, testing, stage
  • Linux operating system management including security patching
  • Fully managed backup with minimum 2 week retention
  • Amazon Web Services (AWS) Partner


  • PHP 5 & 7, MySQL, Solr, Elasticsearch supported
  • Drupal specific support over and above traditional hosting providers
  • Scalability to increase and decrease as required
  • Continual development and evergreening of the cloud hosting service
  • Support for Drush and Composer tool set
  • Unique URL for every branch environment


£1050 per unit per 6 months

  • Education pricing available

Service documents

G-Cloud 10


Ixis IT Limited

Dan Pala



Service scope

Service scope
Service constraints Linux based Open Source Applications (PHP, Node)
System requirements
  • Must run in a Linux based environment
  • Your code will be managed in Git version control

User support

User support
Email or online ticketing support Yes, at extra cost
Support response times Support is available working weekdays only 9am-6pm.
User can manage status and priority of support tickets Yes
Online ticketing support accessibility None or don’t know
Phone support Yes
Phone support availability 9 to 5 (UK time), Monday to Friday
Web chat support No
Onsite support No
Support levels Single support level from a dedicated cloud support engineer for support queries, on-boarding and any business changes requested.
Support available to third parties Yes

Onboarding and offboarding

Onboarding and offboarding
Getting started Fully managed service provided as standard.

Initial setup involves setting up users with the ability to mirror your project Git repository to our interim Git repository used for deployments.

Everything else is based on YAML configuration and standard Git push/branch commands.
Service documentation Yes
Documentation formats PDF
End-of-contract data extraction Database content and files can be accessed with SSH tools such as Drush sync. Application code is all located in your own Git repository.
End-of-contract process Once any data has been backed up, environments are destroyed along with any data backup.

Using the service

Using the service
Web browser interface No
Command line interface No


Scaling available No
Independence of resources Container technology is used to separate resources and data between clients.
Usage notifications Yes
Usage reporting
  • Email
  • Other


Infrastructure or application metrics No


Supplier type Not a reseller

Staff security

Staff security
Staff security clearance Other security clearance
Government security clearance Up to Developed Vetting (DV)

Asset protection

Asset protection
Knowledge of data storage and processing locations Yes
Data storage and processing locations
  • United Kingdom
  • European Economic Area (EEA)
User control over data storage and processing locations Yes
Datacentre security standards Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency Never
Protecting data at rest
  • Physical access control, complying with SSAE-16 / ISAE 3402
  • Physical access control, complying with another standard
  • Encryption of all physical media
Data sanitisation process No
Equipment disposal approach Complying with a recognised standard, for example CSA CCM v.30, CAS (Sanitisation) or ISO/IEC 27001

Backup and recovery

Backup and recovery
Backup and recovery Yes
What’s backed up
  • Virtual machine
  • Database
  • File assets
Backup controls The service is fully managed by the supplier.
The data in the master environment is backed up, all other environments are copied from the master dataset.
Datacentre setup Multiple datacentres with disaster recovery
Scheduling backups Supplier controls the whole backup schedule
Backup recovery Users contact the support team

Data-in-transit protection

Data-in-transit protection
Data protection between buyer and supplier networks TLS (version 1.2 or above)
Data protection within supplier network TLS (version 1.2 or above)

Availability and resilience

Availability and resilience
Guaranteed availability 99.5% uptime SLA on Standard Hosting Server
Approach to resilience The datacentre operator continuously monitors service usage to project infrastructure needs to support availability commitments and requirements. They maintain a capacity planning model to assess infrastructure usage and demands at least monthly, and usually more frequently (e.g., weekly). In addition, the capacity planning model supports the planning of future demands to acquire and implement additional resources based upon current resources and forecasted requirements.

The service itself (the "stack", running on the infrastructure) is designed to be as resilient and self-healing as possible, with continuous monitoring of running services and automated systems to attempt recovery and mitigation in the event of software error.
Outage reporting Incidents (high error rates, unusual resource usage, etc) and outages (service failure, web site unavailable, etc) are reported directly to responsible parties via e-mail and/or pager system, as well as being reported to our internal chat system where teams can coordinate and resolve issues.

Identity and authentication

Identity and authentication
User authentication
  • Public key authentication (including by TLS client certificate)
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels An SSH publickey is required to associate with a username and password pair for Git code access.
Access restriction testing frequency At least once a year
Management access authentication
  • 2-factor authentication
  • Public key authentication (including by TLS client certificate)
  • Dedicated link (for example VPN)
  • Username or password
Devices users manage the service through
  • Any device but through a bastion host (a bastion host is a server that provides access to a private network from an external network such as the internet)
  • Directly from any device which may also be used for normal business (for example web browsing or viewing external email)

Audit information for users

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 Between 1 month and 6 months
Access to supplier activity audit information Users contact the support team to get audit information
How long supplier audit data is stored for Between 1 month and 6 months
How long system logs are stored for Between 1 month and 6 months

Standards and certifications

Standards and certifications
ISO/IEC 27001 certification Yes
Who accredited the ISO/IEC 27001 Alcumus ISOQAR
ISO/IEC 27001 accreditation date 27/04/2018
What the ISO/IEC 27001 doesn’t cover Working in secure areas (11.1.5)
ISO 28000:2007 certification No
CSA STAR certification Yes
CSA STAR accreditation date 01/01/2017
CSA STAR certification level Level 2: CSA STAR Attestation
What the CSA STAR doesn’t cover N/A
PCI certification No
Other security certifications Yes
Any other security certifications Cyber Essentials

Security governance

Security governance
Named board-level person responsible for service security Yes
Security governance certified Yes
Security governance standards ISO/IEC 27001
Information security policies and processes We are certified against the ISO 27001: 2013 and have an established Integrated Management System (IMS) that sets out our procedures and policies to ensure that we adhere to the standard at all times. We are also aware of and adhere to our obligations concerning the Data Protection Act, and GDPR, which is also governed within the IMS.

Operational security

Operational security
Configuration and change management standard Supplier-defined controls
Configuration and change management approach Configuration changes are self service through the use of configuration files placed in your Git repository.
Vulnerability management type Supplier-defined controls
Vulnerability management approach The vulnerability management sub-principle and related processes within the datacentre and cloud 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.

The "stack" (operating system, software, and applications) receives automated security patching for all software directly from the OS maintainers, with security patches applied as soon as they are available and have been tested on pre-production environments. Alerts and newsletters are available from the maintainer, and staff monitor a number of respected advisory services for news.
Protective monitoring type Supplier-defined controls
Protective monitoring approach Systems within the datacentre are extensively instrumented to monitor key operational and security metrics. Alarms are configured to automatically notify operations and management personnel when early warning thresholds are crossed on key metrics. When a threshold is crossed, the incident response process is initiated. The Incident Response team employs industry-standard diagnostic procedures to drive resolution during business-impacting events.

Security monitoring tools help identify several types of denial of service
(DoS) attacks, including distributed, flooding, and software/logic attacks. When DoS attacks are identified, the incident response process is initiated. In addition to the DoS prevention tools, redundant network capacity is available.
Incident management type Supplier-defined controls
Incident management approach Policies exist that describe our response process for common events, with coordination and escalation available for non-standard incidents. Users report incidents through our ITIL service desk, and are kept updated with the progress and state of the incident throughout the event. Full incident reports are provided in the event of serious incidents (for example, extended outages or security events).

Secure development

Secure development
Approach to secure software development best practice Supplier-defined process

Separation between users

Separation between users
Virtualisation technology used to keep applications and users sharing the same infrastructure apart Yes
Who implements virtualisation Supplier
Virtualisation technologies used Other
Other virtualisation technology used Xen hypervisor
How shared infrastructure is kept separate Customer instances have no access to raw disk devices, but instead are presented with virtualized disks. The disk virtualization layer automatically erases every block of storage before making it available for use, which protects one customer’s data from being unintentionally exposed to another. Encryption is supported.

A mandatory firewall is enabled in a default deny-all mode and ports must be explicitly opened to allow inbound traffic. Each client is hosted within an isolated Virtual Private Cloud, preventing network connections from any other systems. "Sniffing" of network traffic is prevented at the hypervisor and interface level.

Energy efficiency

Energy efficiency
Energy-efficient datacentres No


Price £1050 per unit per 6 months
Discount for educational organisations Yes
Free trial available No


Pricing document View uploaded document
Terms and conditions document View uploaded document
Return to top ↑