UltraCompute SaaS Deployment & Implementation for AWS
UltraCompute is a licensed, productised HPC platform removing the need to design, build, and harden an HPC environment from first principles. It allows organisations to launch a new HPC service, replace ageing legacy clusters, or add burst capacity on demand—while running entirely inside the customer’s AWS account and security perimeter.
Features
- Licensed UltraCompute HPC platform deployed in the customer’s AWS account
- Automated installation and configuration of core HPC services
- Configured schedulers, compute pools, and scaling policies
- Integrated storage and data access paths optimised for HPC
- Secure access aligned to existing IAM and network controls
- Initial workload onboarding and operational validation
Benefits
- Delivers a full HPC service in hours, not months
- Eliminates months of bespoke HPC platform engineering
- Runs entirely within the customer’s AWS account
- Keeps all data inside existing security and compliance boundaries
- Supports new, replacement, and burst HPC use cases
- Continuously improved through a managed product control plane
Pricing
- Education pricing available
- Free trial available
Service documents
Request an accessible format
Framework
G-Cloud 15
Service ID
6 4 6 4 9 2 0 3 4 2 0 8 1 4 3
Contact
THE SERVER LABS LTD
Chris Mlynarczyk
Telephone: 07795100733
Email: sales@theserverlabs.com
About your service
- Service categories
-
Application Development and Deployment
Application development
- Development languages, environments and tools
- Software construction components
Modelling and architecture
- Enterprise Architecture Tools
- Multi cloud support
- No
Service scope
- Software add-on or extension
- No
- Cloud deployment model
- Public cloud
- Service constraints
- This SaaS is designed for deployment on Amazon Redshift
- System requirements
-
- A modern web browser (Chrome, Firefox, Edge, Safari) is needed
- Local clients are on versions compatible with standard repository protocols.
- Ensure your corporate network allows traffic to AWS SaaS environment:
- Stable internet connection and sufficient bandwidth for artifact uploads/downloads.
User support
- Email or online ticketing support
- Yes
- Support response times
-
This depends on the severity of the trouble ticket, the following is a summary, but we have a more detailed service model document we can provide:
Severity level 1: <= 2hrs
S2 <= 4hrs
S3 <= 12hrs
S4 <= 24hrs
S5 <= 48hrs - User can manage status and priority of support tickets
- Yes
- Online ticketing support accessibility
- WCAG 2.2 A
- Phone support
- No
- Web chat support
- No
- Onsite support
- No
- Support levels
- Please refer to the supporting document TSL Managed Service Support Model for a full description of support offering (this can be provided on application). TSL provide 8x5 and 24x7 support levels The cost of support levels depends on the scope of the project delivered, and the support models the client requires. For example, we can offer support as a percentage of the price to the customer. In which case, 5x8 support is between 10% and 20%, whereas 24x7 is between 25% and 35%. We also offer fixed fee, and also hourly support models. For hourly support models, the cost is between £90 and £120 an hour. TSL can provide a technical account manager or cloud support engineer, but this is a costed extra for 8x5.
- Support available to third parties
- Yes
Onboarding and offboarding
- Getting started
- For AWS SaaS, once we have created the initial set up for the SaaS managed service environment. It really depends on the customer. We have clients who simply want us to set up the SaaS environment and then leave the client to do the rest, right through to clients who require TSL to set up the entire environment for them. Set up the AWS tools and applications, and provide ongoing consultative support. So we provide a broad range of training, which can be either online or onsite. Post deployment, we provide either a "bag of hours" approach to ongoing remote consultative support, or we can provide tailored specific post deployment managed service support. Which provides everything from mentoring, through providing a FinOps service, Cloud security service etc. In terms of user documentation, the vast majority of this is provided via the AWS website, but TSL will create custom documentation where necessary. If the client also wishes TSL to migrate their existing data into the new AWS environment, TSL can do this via the use of the AWS MAP process. The details of what TSL offer in terms of AWS services is covered via our AWS services offering listed in Lot3
- Service documentation
- Yes
- Documentation formats
-
- HTML
- End-of-contract data extraction
-
Data extraction with AWS involves a planned process of identifying, securing, transferring, and verifying data before decommissioning resources, using various AWS services tailored to the specific type, volume, and location of the data. The goal is to move the data securely and reliably to a new location for retention or analysis. General Steps for End-of-Use Data Extraction The process generally follows these high-level steps: Assessment and Planning: Identify the data sources, estimate the data volume, determine the destination and available network bandwidth, and establish security and compliance requirements.
Extraction and Transfer: Choose the appropriate AWS service to extract and transfer the data. AWS provides both online and offline migration methods. Validation and Reconciliation: Verify the integrity and completeness of the extracted data in the new destination.
Decommissioning: Once verification is complete and stakeholders confirm the data is safe, securely delete the original data and terminate the AWS resources to avoid future costs. Please refer to the AWS website for further information - End-of-contract process
- The contract with TSL includes the management of the AWS hosted IaaS environment. Typically, the client needs to provide at least one months notice of a desire to terminate the contract with TSL. Depending on whether the client wishes to stop using AWS entirely and is going to migrate to a different environment. Or whether the client simply wishes to stop using TSL, but will remain an AWS user, the process is different. For the former, the process described above for end of use covers the key activities. For switch over to another AWS IaaS service provider, TSL would work with the client, AWS and potentially the new IaaS provider to re-assign the AWS accounts to the new IaaS provider. If the Client wishes TSL to help manage them to move their data out of AWS into a new environment, this would typically be an additional cost outwith the pre-existing standard IaaS contract.
- Documentation accessibility standard
- WCAG 2.2 A
Using the service
- Web browser interface
- Yes
- Supported browsers
-
- Microsoft Edge
- Firefox
- Chrome
- Safari
- Opera
- Other
- Application to install
- No
- Designed for use on mobile devices
- Yes
- Differences between the mobile and desktop service
- Users can access either via web browser or via the dedicated mobile app
- Service interface
- Yes
- User support accessibility
- WCAG 2.2 A
- Description of service interface
- Amazon Redshift supports several management interfaces that you can use to create, manage, and delete Amazon Redshift clusters: the AWS SDKs, the AWS Command Line Interface (AWS CLI), and the Amazon Redshift management API.
- Accessibility standards
- WCAG 2.2 AA
- Accessibility testing
-
Yes, Amazon Redshift can be used by individuals requiring assistive technology, as part of Amazon Web Services (AWS) broader commitment to accessibility. AWS provides, maintains, and updates accessibility, including screen reader support and keyboard navigation, for the AWS Management Console and associated services.
Key Aspects of Accessibility for Amazon Redshift:
Accessible Management Console: The AWS Management Console, used to configure and manage Redshift clusters, is designed to support assistive technologies, including screen readers.
Alternative Access Methods: Beyond the console, users can interact with Redshift using standard SQL clients (JDBC/ODBC) and the Data API, which can be operated via accessible terminal or scripting tools.
Documentation Accessibility: If documentation is needed in a more accessible format, users can contact AWS support.
VPAT/ACR: Accessibility Conformance Reports (ACRs) based on the Voluntary Product Accessibility Template (VPAT®) are available via AWS Artifact, which evaluate compliance with standards like WCAG and Section 508. - API
- Yes
- What users can and can't do using the API
-
The Amazon Redshift Data API (as of January 2026) allows you to interact with Amazon Redshift provisioned clusters or serverless workgroups via a secure HTTP endpoint, eliminating the need for persistent database connections or JDBC/ODBC drivers.
Key Capabilities
Asynchronous Execution: Queries run in the background. You receive a unique Query ID immediately and can poll for results or status later.
Session Reuse: New as of late 2024, the API supports persistent sessions for multi-step ETL workflows, allowing you to maintain temporary tables and state across sequential queries.
Integrated Security: Authenticate using IAM credentials (temporary) or secrets stored in AWS Secrets Manager. It also supports trusted identity propagation.
Event-Driven Integration: Can be configured to send status notifications (e.g., query finished/failed) directly to Amazon EventBridge. - API documentation
- Yes
- API documentation formats
-
- HTML
- API sandbox or test environment
- Yes
- Customisation available
- Yes
- Description of customisation
- The underlying software cannot be customised, but the look and feel and the data manipulated can be customised. Customisation is via the GUI, all users with edit permission can customise
Scaling
- Independence of resources
- AWS IaaS resources are set up as part of the contract, AWS instances required can be set up as dedicated or on-demand. The client can choose a mixture, so they get the cost benefit of dedicated instances, whilst at the same time having access to on-demand instances to ensure if the load suddenly surges, then instances will be spun up in real-time to ensure a spike in load does not affect other users.
Analytics
- Service usage metrics
- Yes
- Metrics types
-
CPU
Disk
HTTP request and response status
Memory
Network
Number of active instances
Please refer to AWS website for further information on the broad range of metrics available. - Reporting types
-
- API access
- Real-time dashboards
- Regular reports
- Reports on request
- Resource tagging
- Yes
- FOCUS resource tagging
- Yes
Resellers
- Supplier type
- Reseller providing extra support
- Organisation whose services are being resold
- JFROG
Staff security
- Staff security clearance
- Conforms to BS7858:2019
- Government security clearance
- Security Clearance (SC)
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 4.0)
- Penetration testing frequency
- At least every 6 months
- Penetration testing approach
- NCSC approved service provider
- Protecting data at rest
- Encryption of all physical media
- Data sanitisation process
- Yes
- Equipment disposal approach
- Complying with a recognised standard, for example CSA CCM v4.0, CAS (Sanitisation) or ISO/IEC 27001
- Data sanitisation type
-
- Deleted data can’t be directly accessed / Cryptographic Erasure
- Data Erasure
Data importing and exporting
- Data export approach
- Please refer to Amazon website for further information on extract of data from Amazon Redshift
- Data export formats
-
- CSV
- Other
- Other data export formats
-
- JSON
- Apache Parquet
- ORC
- Data import formats
-
- CSV
- Other
- Other data import formats
- Same as for export formats
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
- Guaranteed availability
- This depends on the type of AWS infrastructure used: Guarantees often depend on how you architect your resources, with higher uptime typically requiring multi-location redundancy. Amazon EC2 (Compute): 99.99% for instances deployed across multiple Availability Zones (AZs). 99.5% for a single EC2 instance. Amazon S3 (Storage): 99.9% standard availability SLA. Note: While availability is 99.9%, S3 is designed for 99.999999999% (11 nines) of data durability, ensuring data is not lost even if it is temporarily unavailable. Amazon RDS (Databases): 99.95% for Multi-AZ deployments. Single-AZ instances typically do not have a formal availability guarantee. Networking & Serverless: 99.99% for Elastic Load Balancing (ELB) and Amazon Route 53. 99.95% for AWS Lambda and Amazon EKS. When availability drops below the guaranteed threshold, AWS provides credits based on the severity of the downtime: 10% Credit: Typically triggered if uptime falls below the commitment (e.g., <99.99% for Multi-AZ EC2) but remains above 99.0%. 25% - 30% Credit: Triggered if uptime falls below 99.0%. 100% Credit: Triggered if uptime falls below 95.0%.
- Approach to resilience
- Please refer to the AWS website for in depth information on AWS data centre resilience
- Outage reporting
- Customers can configure proactive alerts to receive outage information via multiple channels: AWS User Notifications: Centralizes alerts from multiple AWS accounts, allowing you to receive emails, push notifications to the AWS Console Mobile App, or messages in chat applications like Slack. Amazon EventBridge: For programmatic or advanced alerting, users can create EventBridge rules that trigger actions—such as sending an SMS via Amazon SNS or running an AWS Lambda function—the moment an AWS Health event is detected. CloudWatch Alarms: Alarms can be set to monitor specific service metrics or AWS Health events, sending notifications via email, SMS, or third-party tools like PagerDuty. Please refer to the AWS website for further information
Identity and authentication
- User authentication needed
- Yes
- User authentication
-
- Multi-Factor Authentication (MFA)
- Username or password
- Access restrictions in management interfaces and support channels
- Access restrictions in AWS are enforced using Role-Based Access Control (RBAC) model combined with Permission Targets to manage user authentication and authorization. Please refer to AWS website and contact AWS for further information on how access restrictions are enforced
- Access restriction testing frequency
- At least every 6 months
- Management access authentication
-
- Multi-Factor Authentication (MFA)
- Username or password
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
- User-defined
- Access to supplier activity audit information
- Users have access to real-time audit information
- How long supplier audit data is stored for
- User-defined
- How long system logs are stored for
- User-defined
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
-
JFROG & TSL are ISO 27001 accredited companies. TSL have a fully UKAS audited ISMS, with 24 ISMS policies that are ISO 27001:2022 audited on a yearly basis, TSL have now been an ISO 27001 certified organisation for six years.
We can provide further information on our ISO 27001 ISMS on application.
In addition, TSL recently ugraded their Cyber Essentials certification to the fully audited Cyber Essential Plus certification.
TSL have an Information Security Committee, which meets monthly. It has an ISO who reports to the CEO, with the CEO being the designated DPO. TSL run internal ISO 27001 audits twice a year. - Software Security Code of Practice
- Yes
Operational security
- Configuration and change management standard
- Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
- Configuration and change management approach
- TSL and AWS adhere to several global and industry-specific compliance standards for configuration and change management. These standards ensure that infrastructure and service modifications are planned, authorized, and documented to maintain security and operational integrity. ISO/IEC 27001:2022: TSL & AWS is certified under this international standard, which specifically mandates controls for change management in Annex A Control 8.32. This requires that changes to information systems be formally planned, assessed for risk, and authorized. Please refer to the AWS website for a full overview of the AWS configuration and change management processes
- Vulnerability management type
- Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
- Vulnerability management approach
- AWS employs a comprehensive, multi-layered vulnerability management approach that divides responsibilities between the security of the cloud and security in the cloud. Security OF the Cloud (AWS Responsibilities) AWS manages vulnerabilities in the underlying physical infrastructure, software, and networking that power its services. All AWS services undergo mandatory, rigorous security assessments and vulnerability scanning prior to launch. AWS operates an internal program that continuously discovers and reassesses vulnerabilities across its entire global fleet. Critical vulnerabilities and zero-day threats are patched "around the clock" until the fleet is secure. AWS manages a public disclosure program via HackerOne and publishes Security Bulletins.
- Protective monitoring type
- Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
- Protective monitoring approach
- Both TSL and AWS adhere to ISO/IEC 27001:2022: Annex A controls (e.g., A.12.4.1 - Logging and Monitoring), requiring that all administrative activities and security events are logged and protected from tampering. ISO/IEC 27001:2022: AWS adheres to Annex A controls (e.g., A.12.4.1 - Logging and Monitoring), requiring that all administrative activities and security events are logged and protected from tampering.
- Incident management type
- Complies with a recognised standard, for example, CSA CCM v4.0 or ISO/IEC 27035:2011 or SSAE-18 / ISAE 3402
- Incident management approach
- TSL have an incident management platform which is part of its ISO 27001 ISMS. The incident management platform is built in Jira Service Desk. It has specifically defined processes for information security incidents and breaches. Users report incidents to the ISO and his deputies (other members of the ISC). We provide incident reports directly from Jira and to the staff via Slack. In addition we have an incident and non conformity log, which is tracked and reported via an agreed set of security KPI's. For AWS ISO 27001 ISMS, please refer to the AWS website for further information
- Post-quantum cryptography secure
- Yes
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 v4.0)
Public sector networks
- Connection to public sector networks
- No
Pricing
- Discount for educational organisations
- Yes
- Free trial available
- Yes
- Description of free trial
- Full feature access, typically for 14 days, but can be extended to 30 days
Discount percentage by annual call-off contract value (excluding VAT)
- Less than £250,000
- 0%
- Between £250,000 and £500,000
- 0%
- Between £500,001 and £1,000,000
- 0%
- Between £1,000,001 and £2,500,000
- 0%
- Between £2,500,001 and £5,000,000
- 0%
- Over £5,000,001
- 0%
Non-mandatory Standards and certifications
- ISO/IEC 27001 certification
- Yes
- Who accredited the ISO/IEC 27001
- UKAS/CFA
- ISO/IEC 27001 accreditation date
- Friday 2 August 2024
- What the ISO/IEC 27001 doesn’t cover
- All Information systems within TSL are covered by the TSL Information Security Management System. TSL is a virtual company, there are no other systems or infrastructure.
- ISO 28000:2022 certification
- No
- ISO 9001 certification
- No
- Quality management systems (QMS)
- No
- CSA STAR certification
- No
- PCI certification
- No
- Cyber essentials
- Yes
- Please provide your Cyber Essentials Certificate Number
- F03cb052-a3b2-410f-83f9-671bcbc18a63
- Cyber essentials plus
- Yes
- Please provide your Cyber Essentials Plus Certificate Number
- 37c834c7-be6d-481f-9446-ec86bcbc3033
- Other security certifications
- No
Social value
- Section B - Commitment for Future: Delivery
-
-
Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.
Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority
- Plans to engage the contract workforce in deciding the most important workplace issues to address
- Ensuring new workers are informed of their right to join a trade union
- Employment contracts that reflect actual hours worked; steps taken to ensure employees understand their contracts and have the ability to review and adjust them if actual hours regularly exceed contracted hours
- Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
- Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
- Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
- Entitlement to sick pay for the contract workforce, with provision in place for any staff who do not meet the earnings threshold for statutory sick pay, payment of sick pay from day one of absence and payment of staff on the contract workforce who are off sick a replacement income of 100% of their usual earnings for as long as possible
- Measures to support in-work progression to help people in the contract workforce, to move into higher paid work by developing new skills relevant to the contract
- Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
- Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors
- Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
-
Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.
Policy Outcome 2: Skills for growth: Supporting growth sectors and addressing skills gaps.
- Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
-
Mission: Make Britain a clean energy superpower: To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero
Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.
- Understanding of opportunities for additional environmental benefits delivery in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
- Collaborative ways of working with the supply chain to deliver additional environmental benefits in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
- Understanding of how to influence staff, suppliers, customers, communities and/or any other appropriate stakeholders through the delivery of the contract to support climate and nature protection and improvement
-
Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain
Policy Outcome 6: Employment and training: For those who face barriers to employment
- Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce
-
Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.
Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.
- Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
-