PeaSoup Infrastructure as a Service (IaaS) enables organisations to rapidly provision and control, Virtual Servers, networks and firewalls in minutes. The secure and resilient Virtual Data Centre (vDC) environment can be connected to your on-premise environment in a Hybrid computing model or controlled via our fully functional portal interface.
- A true software defined datacentre, with full autonomous control.
- Manage your environment, networks, firewalls, load balancers and servers.
- Build servers in minutes from customisable templates or uploaded media
- Hybrid connections allows full control from local vSphere management tools
- Hyper-Converged Cloud Architecture for high performance and resilience by design
- No maintenance windows within the SLA
- SLA is authentic with only 4.38 hours risk per year
- Multiple Tier3 datacentres, two PoPs and four key transit providers
- Object based storage, no RAID removes risks of degrade performance
- Full 24/7 support accessible via telephone, email or portal
- Dedicated account relationship management for advice and continuity
- Aligns actual IT consumption with cost, a true utility model
- Quarterly pricing reviews to ensure no monthly invoice surprises
- Agile scaling to organisational demand making additional resources instantly available
- UK Sovereign, UK owned company. Data never leaves the UK
- Real time utilisation reporting through our fully functional portal
- Documented processes, supported with video for common administration tasks
- Ability to snapshot servers before change to provide rollback safeguards
- Complete 24/7/365 service monitoring of the infrastructure performance and uptime
- No hidden costs, simple pricing model with free trials available
£0.05 per gigabyte per month
- Education pricing available
- Free trial available
01932 450 400
The 24/7 support covers our infrastructure and our clients usage of the virtual datacentre. We do not support clients server operating systems or applications directly.
Services implemented within the Virtual Datacentre should not be running their own hypervisor or require direct access to the PeaSoup Cloud hypervisor management Layer
|Email or online ticketing support||Email or online ticketing|
|Support response times||
Within PeaSoup, any infrastructure issues have the highest priority, 30-minute response. and are constantly monitored 24/7.
Customer calls are raised as either Priority1 – (see below) should already be in progress. Customer updates are provided every hour.
Or raised as Priority 4 - Operational questions, advice or a change in service. This carries an 8 hour response time and a 95% SLA to resolution within 40 hours.
Responses at weekends are answered within 2 hours of the request.
|User can manage status and priority of support tickets||Yes|
|Online ticketing support accessibility||None or don’t know|
|Phone support availability||24 hours, 7 days a week|
|Web chat support||No|
PeaSoups infrastructure has the highest priority, 30-minute response which is constantly monitored 24/7. This is unseen by our customers. The infrastructure is designed to cope with failure and an internal SLA provides 95% of all calls fixed within a 4hr window.
If there is an operational issue preventing the delivery of the service, and customers are affected, updates are provided every hour.
Customer raised calls generally are priority 4 calls relating to operational questions, advice or a change in service. This carries an 8 hour response time and a 95% SLA to resolution within 40 hours. Much of this level is mitigated through our support desk with a plethora of videos and documents on general usage of the systems provided.
Support is operated by the engineering team, however each client has their own account manager who monitors the support ticket and provides the communication.
The support describes is included within the pricing of the service contract covering the infrastructure of the service. PeaSoup do not directly provide support and maintenance of the customers operating systems or applications.
|Support available to third parties||Yes|
Onboarding and offboarding
We provide an onboarding Webex in which we go through all of the features of the platform and how to setup everything up within the environment. This includes the virtual machines, catalogues, users, firewalls, networking and load balancers. This is supplemented by our full documentation, setup guides and access to the documentation on the support portal.
For pre-existing environments, we can migrate to the PeaSoup platform using cloud DR techniques or uploading data through the portal interface. Data can also be seeded directly into the datacentre via customer-provided external drives.
|End-of-contract data extraction||Depending on the size of the data and the nature of the migration we can use standard cloud DR techniques to synchronise data with another platform/provider. Data can be migrated through the portal or we can provide a method of migration via customer-provided external drives and shipping.|
At the end of the contract, the customer may decide to renew/change/cease the service.
If there is no migration of data required or the customer does this through the self-service interface then there are no additional charges. If PeaSoup needs to be involved to operate a disaster recovery style migration or to move physical data then these services will incur an additional charge.
Using the service
|Web browser interface||Yes|
|Using the web interface||
Users can log into the web interface to make changes to their environment.
This includes but not limited too:
1) Provisioning of VMs from ISO or from catalog
2) Snapshotting, suspending, rollback or deletion of VMs
3) Assigning resources to individual VMs
4) Configure/manage firewalls and networking.
5) Setup load balancers.
6) Setup users with varying levels of user privileges.
7) Manage virtual datacentres
8) Monitor resource usage/allocation
9) Managing Catalogs including uploading new media
10) Creation from OVF package as vApp templates
11) Creating and managing vApps
12) Change guest OS properties
13) Connect remotely to VMs
Access can be through PC, MAC, smartphone, tablet.
- Internet explorer 9+
Full control of the virtual datacentre that would be expected with a physical datacentre.
|Web interface accessibility standard||None or don’t know|
|How the web interface is accessible||Upon signing up to the service, clients are provided with a document on how to connect to the environment, this includes the web page, username and passwords.|
|Web interface accessibility testing||N/A|
|What users can and can't do using the API||
The VMware vCloud API provides support for developers who are building interactive clients of VMware vCloud Director using a RESTful application development style.
vCloud API clients and vCloud Director servers communicate over HTTP, exchanging representations of vCloud objects. These representations take the form of XML elements. You use HTTP GET requests to retrieve the current representation of an object, HTTP POST and PUT requests to create or modify an object, and HTTP DELETE requests to delete an object.
|API automation tools||
|API documentation formats||
|Command line interface||Yes|
|Command line interface compatibility||
|Using the command line interface||
This is unused by PeaSoup, however all information on command line interface is highlighted in the following URL:
|Independence of resources||Within the vDC all resources are reserved for each customer ensuring that the compute power is always available when required, without impact or cross over from other users.|
|Infrastructure or application metrics||Yes|
|Supplier type||Not a reseller|
|Staff security clearance||Conforms to BS7858:2012|
|Government security clearance||None|
|Knowledge of data storage and processing locations||Yes|
|Data storage and processing locations||United Kingdom|
|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||At least once a year|
|Penetration testing approach||In-house|
|Protecting data at rest||
|Other data at rest protection approach||
- All data is stored within ISO27001 PCI-DSS Service Provider accredited facility.
- Guest OS can also be fully encrypted.
- Encryption can be applied to media and is user defined
|Data sanitisation process||Yes|
|Data sanitisation type||
|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||Yes|
|What’s backed up||VM's Including all files, databases and applications within the VM's|
|Backup controls||Backups are controlled via the Veeam vCloud Director Support. This gives control over which VM's are to be backed up with customisable backup plans/schedules.|
|Datacentre setup||Single datacentre with multiple copies|
|Scheduling backups||Users schedule backups through a web interface|
|Data protection between buyer and supplier networks||
|Data protection within supplier network||
Availability and resilience
Uptime rate of 99.95% non-caveated by planned or unplanned maintenance.
A discount of 5% of the monthly Fees payable for each whole 30 minute period of Downtime. Such discounts shall be applied to the Fee payment due immediately following the Downtime. Discounts shall be made up to a maximum of 100% of the Fees payable for a given month.
|Approach to resilience||
Operating within Tier 3, datacentres with multiple power supplies, generators and cooling units for resilience. Our cloud configuration is maintained under strict change control and protected by internal processes and procedures.
Our network connectivity is provided separately from two Points of Presence in two diverse Tier3 datacentres, away from the server environment, where our core internet routers reside, these connect us to our four main internet providers in a BGP configuration.
Networking connectivity is one of the most common causes of datacentre outages and we have the ability to survive multiple failure scenarios in our design.
We have simplified our cloud design to reduce the risk of downtime. We have NO physical SAN architecture, dramatically reducing our risk of failure associated with traditional architectures.
The PeaSoup Cloud is a software defined datacentre. Networking, firewalls, compute power and storage are all controlled at the software layer within clusters of physical servers for resilience. We scale out adding more servers as needed to meet demand and with each additional server we add not only more capacity but also more performance across the whole cluster, especially the performance of the storage.
|Outage reporting||In the event of an outage, email alerts are sent followed up by a phone call from your dedicated account manager to keep you informed of the progress in resolving any issues.|
Identity and authentication
|Access restrictions in management interfaces and support channels||User accounts are set up with specific access using a role-based access system that ensures granularity of the available services within the environment. PeaSoup access is additionally restricted via the internal Information Security Policy which ensures only the authorised personnel within the support team have access to the management interface whereas account managers only have access to read-only reporting information.|
|Access restriction testing frequency||At least every 6 months|
|Management access authentication||
|Devices users manage the service through||
Audit information for users
|Access to user activity audit information||Users have access to real-time audit information|
|How long user audit data is stored for||Between 1 month and 6 months|
|Access to supplier activity audit information||Users have access to real-time 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
|ISO/IEC 27001 certification||Yes|
|Who accredited the ISO/IEC 27001||BSI|
|ISO/IEC 27001 accreditation date||13/1/2015|
|What the ISO/IEC 27001 doesn’t cover||Stage 2 - in process with BSI|
|ISO 28000:2007 certification||No|
|CSA STAR certification||Yes|
|CSA STAR accreditation date||13/1/2015|
|CSA STAR certification level||Level 1: CSA STAR Self-Assessment|
|What the CSA STAR doesn’t cover||Ongoing in line with our certifications with BSI stage 2.|
|Other security accreditations||No|
|Named board-level person responsible for service security||Yes|
|Security governance accreditation||Yes|
|Security governance standards||ISO/IEC 27001|
|Information security policies and processes||In line with our Information Security Policy Peasoup are committed to the development and continual improvement of Information Security and its supporting information security management system, in order to provide; - Assurance with legal, regulatory and contractual obligations - Reputation management - Protection of critical assets.|
|Configuration and change management standard||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Configuration and change management approach||
PeaSoup operates a change control process in-line with our ISO27001 procedures.
This covers all the components that use an operating system to control hardware and/or software activity, any building services supplied to PeaSoup (power, air conditioning etc) and any service provided to PeaSoup upon which the continuity of service to its customers is reliant. The request for change or emergency change procedure requires top-level authorisation with technical and business approvers. This also aligns with our Continual Improvement and Corrective action Policy. All components of the infrastructure are tracked inline with our Infrastructure Management Policy controlling the configuration tracking of all devices
|Vulnerability management type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Vulnerability management approach||
The PeaSoup Security Steering Group uphold the Risk Management Policy which is aligned to ISO27005:2018-Information Security Risk Management. This ensures risks are identified, evaluated and treated appropriately in an ongoing basis. PeaSoup hold a strong relation with all of our vendors and keep track industry information and also monitor software security mailing lists.
Known critical patches are applied as soon as possible following the change control process, less critical patches are assessed through the risk register maintained by the Security Steering Group.
|Protective monitoring type||Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402|
|Protective monitoring approach||In line with our Audit and Monitoring Policies - The PeaSoup Security Manager must be informed immediately of any unusual traffic flows or network device activity that arises from regular network monitoring or alerts. Quantitative or qualitative information on network activity may indicate either device failure or network attacks. The Security Manager need to be made aware of this activity to investigate the possibility of a network attack that requires remedial action or escalation.|
|Incident management type||Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402|
|Incident management approach||
All incidents, are classified, handled, reviewed, resolved and documented using the Incident Management Process in order to aid in business continuity and business recovery activities.
The purpose of this policy is to help identify and resolve incidents effectively, minimise the business impact and reduce the risk of similar incidents occurring.
There are predefined procedures, for events triggered by suspicious activity in monitoring any evidence of unauthorised activity or critical IDS/IPS alerts.
The policy also defines the processes used to report incidents for users. It the security managers responsibility to report and distribute a response and escalate as necessary.
|Approach to secure software development best practice||Supplier-defined process|
Separation between users
|Virtualisation technology used to keep applications and users sharing the same infrastructure apart||Yes|
|Who implements virtualisation||Supplier|
|Virtualisation technologies used||VMware|
|How shared infrastructure is kept separate||
The platform utilises vCloud technology and each organisation is completely seperated at the network level by design. Each client is provisioned with their own virtual private datacentre with their own login credentials, own networking and own firewalls providing the control of who can access their virtual datacentre.
This creates a separate environment that is completely under each organisations control.
|Price||£0.05 per gigabyte per month|
|Discount for educational organisations||Yes|
|Free trial available||Yes|
|Description of free trial||As part of the trial, we provide a full handheld walkthrough of the Virtual Datacentre (vDC) with full access to all features within the platform over a 2 week period. The following resources are provisioned: 2vCPU, 8GB vRAM, 100GB HDD, 10Mbps of Bandwidth. This does not include backup services.|
|Pricing document||View uploaded document|
|Service definition document||View uploaded document|
|Terms and conditions document||View uploaded document|