TESTFYRA LIMITED

Software & AI Engineering Development Services

Custom software and AI engineering for government digital transformation. Full-stack development (web, mobile, desktop), API integration, blockchain solutions, and advanced AI/ML applications. Specializations include RAG systems, autonomous AI agents, custom chatbots, fraud detection, AIOps, private LLM deployment, and AI-powered workflow automation

Features

• Full‑stack development for web, mobile, and desktop platforms
• Custom AI model development with private LLM deployment
• RAG systems enabling intelligent knowledge retrieval and analysis
• Autonomous AI agents providing self‑healing automation and orchestration
• AI‑powered cybersecurity delivering fraud detection and threat intelligence
• Blockchain development supporting secure ledgers and smart contracts
• API integration and automation connecting legacy and modern systems
• Multi‑modal AI processing text, images, video, and speech
• AIOps implementation using predictive analytics for IT operations
• Cloud‑native architecture supporting AWS, Azure, GCP, and hybrid

Benefits

• Accelerate digital transformation using modern software and advanced AI
• Reduce operational costs through intelligent automation removing repetitive tasks
• Enhance security posture with AI‑powered threat detection and prevention
• Improve citizen services using conversational AI and automated responses
• Scale applications efficiently without infrastructure constraints or vendor lock‑in
• Future‑proof technology investments using cutting‑edge AI and engineering
• Ensure data sovereignty through private on‑premises AI deployments
• Comply with regulations using governance frameworks meeting UK standards
• Increase developer productivity using automated DevOps pipelines and AIOps
• Deliver custom solutions avoiding generic product limits and constraints

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at contact@testfyra.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

227266861169126

Contact

Kam Sangha
07814
contact@testfyra.com

About your service

• Service categories:

  Application Development and Deployment

  Application development

  • Development languages, environments and tools

  Modelling and architecture

  • Business Process Modelling Tools
• Multi cloud support: Yes

Service scope

• Software add-on or extension: No
• Cloud deployment model:
  • Public cloud
  • Private cloud
  • Community cloud
  • Hybrid cloud
• Service constraints: Successful software development depends on clear requirements, stakeholder availability for reviews, and timely feedback. AI model training requires high‑quality, unbiased data to ensure accuracy. Private LLM deployments demand significant GPU resources, either client‑provided or separately procured. Custom development typically spans three to six months, with rushed timelines risking reduced quality. Legacy system integration relies on documentation and accessible APIs. AI accuracy improves iteratively through testing and refinement, with early deployments often needing tuning. Blockchain solutions require appropriate network infrastructure and consensus choices. Certain AI capabilities also require ongoing retraining and maintenance beyond the initial development phase.
• System requirements:
  • Modern cloud infrastructure or on‑premises servers providing adequate computing resources
  • Computing resources supporting GPU acceleration for intensive AI model training
  • Database systems compatible with relational and non‑relational organisational data storage
  • Container orchestration platforms like Kubernetes or Docker enabling scalable deployments
  • API endpoints and integration documentation required for connecting existing systems
  • Version control repository access via Git, GitLab, or GitHub
  • CI/CD pipeline infrastructure enabling automated testing, building, and deployment workflows
  • Authentication and authorisation systems ensuring secure user access control mechanisms
  • Development, staging, production environments replicating configurations for safe testing
  • Administrative access permissions required for deployment, configuration, and integration activities

User support

• Email or online ticketing support: Yes, at extra cost
• Support response times: TestFyra offers flexible support tailored to testing project needs. Standard Support provides business‑hours remote assistance, monitoring, defect triage, and troubleshooting, with 4‑hour critical and 24‑hour non‑critical responses. Enhanced Support extends hours with a dedicated Manager, priority defect handling, analytics, automation support, and strategy reviews, with 2‑hour and 8‑hour response targets. Premium Support delivers 24/7 coverage with an Technology Lead, real‑time dashboards, immediate incident response, proactive monitoring, and continuous improvement, with 1‑hour and 4‑hour response times. All tiers include documentation, knowledge transfer, and access to TestFyra’s provided platforms.
• User can manage status and priority of support tickets: Yes
• Online ticketing support accessibility: WCAG 2.2 AA
• Phone support: No
• Web chat support: No
• Onsite support: Yes, at extra cost
• Support levels: TestFyra provides structured software and AI development support across the full project lifecycle, delivered through three service tiers.; Standard Support offers business‑hours coverage (9am–5pm, Monday to Friday) via email and phone during active development. It includes bug fixes, minor enhancements, and technical guidance for delivered applications. Monthly progress meetings cover project updates and sprint planning. Response times are four hours for critical issues and twenty‑four hours for non‑critical. A ninety‑day post‑deployment warranty provides continued bug‑fix support. Pricing is £850 per developer per day, plus £400 per month for post‑deployment assistance.; Enhanced Support extends coverage to 8am–8pm, Monday to Saturday, with a dedicated Technical Lead providing architectural guidance, code reviews, and quality assurance. This tier includes bi‑weekly sprint reviews, documentation, priority bug resolution, performance optimisation. Response times are two hours for critical issues and eight hours for non‑critical. Pricing is £1,200 per day, plus £800 per month post‑deployment.; Premium Support provides 24/7 production coverage with an AI Solution Architect offering strategic direction, technical leadership, and stakeholder engagement. It includes continuous development, rapid feature delivery, proactive monitoring, AI model performance tracking, and a twelve‑month warranty. Pricing is £2,200 per day, plus £1,500 per month for managed support.; include source‑code ownership, documentation, knowledge‑transfer
• Support available to third parties: No

Onboarding and offboarding

• Getting started: TestFyra ensures successful software and AI project initiation through a structured onboarding process delivered across five phases.; Phase 1: Discovery and Requirements (Weeks 1–2); An initial consultation workshop defines business objectives, user needs, technical constraints, and success criteria. Stakeholder interviews conducted across technical teams, business units, end users. Existing systems, architecture, integration requirements, AI training data quality reviewed. Outputs include a requirements document, technical architecture proposal, project roadmap, resource plan.; Phase 2: Development Environment Setup (Week 2); Development infrastructure is established, including version control repositories, CI/CD pipelines, development and staging environments, and collaboration tools such as Jira, Confluence, and Teams. Access permissions, API credentials, integration endpoints, automated testing frameworks, and code‑quality tools are configured.; Phase 3: Agile Development Kickoff (Week 3); A project kickoff meeting aligns the team on objectives, timelines, and communication protocols. Sprint planning defines initial user stories and acceptance criteria. A design sprint produces wireframes, mock‑ups, and architecture diagrams, supported by knowledge‑transfer sessions.; Phase 4: Iterative Development (Weeks 3+); Two‑week sprints deliver incremental progress through demos, daily stand‑ups, and bi‑weekly reviews. Continuous deployment to staging enables early testing.; Phase 5: Training and Handover; User training, administrator documentation, operational handover, post‑deployment support transition complete the process.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: TestFyra ensures complete data ownership and seamless extraction at project conclusion:; Source Code & Intellectual Property: All custom-developed software source code transferred to client via Git repositories with complete commit history. Clients own 100% intellectual property rights for custom developments. Source code provided with comprehensive documentation, architectural diagrams, technical specifications. Third-party libraries, dependencies documented with licensing information.; AI Models & Training Data: Trained AI models exported in standard formats (ONNX, TensorFlow SavedModel, PyTorch) enabling deployment on any infrastructure. Model weights, hyperparameters, training configurations provided. Training datasets remain client property; TestFyra retains no copies post-contract. Model performance metrics, evaluation reports, benchmarking data delivered.; Application Data: Database schemas with migration scripts for easy data extraction and portability. Application data exported in standard formats (JSON, CSV, SQL dumps) compatible with industry-standard . User data, configurations, system logs provided with metadata ensuring context.; Documentation Package: Comprehensive technical documentation including architecture diagrams, API specifications, deployment guides, troubleshooting runbooks, and user manuals. Video training materials and recorded knowledge transfer sessions provided.; Deployment Artifacts: Docker images, Kubernetes configurations, infrastructure-as-code templates, and CI/CD pipeline definitions enabling independent deployment and operations.; No Vendor Lock-In: Applications architected using open standards and portable technologies preventing dependency on TestFyra-specific infrastructure or services.
• End-of-contract process: TestFyra manages software development contract closure through a structured process that ensures a smooth and secure operational transition.; 30 Days Before Contract End; Final sprint planning is completed to address remaining user stories and outstanding issues. A full code review confirms adherence to quality standards, and a final security audit with penetration testing validates the application’s security posture. Knowledge‑transfer sessions and documentation handover are scheduled.; Final Weeks; All deliverables are finalised, including source code, documentation, training materials, and deployment artefacts. Technical handover sessions cover architecture, codebase navigation, deployment procedures, troubleshooting, and maintenance. Administrator and user training is delivered to ensure operational readiness.; Contract End Date; The complete source‑code repository, including commit history, is transferred to the client’s Git platform. A full documentation package is provided, covering architecture, API specifications, deployment guides, and user manuals. AI model exports, training datasets, and performance reports are delivered. TestFyra access credentials are removed from client systems.; Warranty Period; Post‑deployment warranty support continues, providing bug fixes, technical assistance, and prioritised security patches.; Optional Transition Support; Extended support contracts are available for maintenance, enhancements, and technical consulting.; Final Deliverables; A closure report summarises delivered features, technical decisions, lessons learned, and recommendations.
• Documentation accessibility standard: WCAG 2.2 AA

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: Some features work better on desktop version.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: TestFyra offers role-based access through four intuitive interfaces. The Web-Based Dashboard provides a responsive browser platform (Chrome, Firefox, Safari, Edge) for managing projects, monitoring real-time execution, and generating reports. RESTful APIs allow programmatic test execution, result retrieval, and CI/CD integration. Finally, the Admin Console centralises user permissions, project setup, and reporting, secured via SSO authentication. Each interface ensures seamless, efficient testing tailored to user needs.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: TestFyra has not conducted formal user testing with assistive technology users to date. However, our web-based interfaces are developed following WCAG 2.1 Level AA guidelines including semantic HTML markup, keyboard navigation support, ARIA attributes for dynamic content, sufficient color contrast ratios (4.5:1 minimum), and alternative text for non-text content. Automated accessibility scanning performed using Axe and WAVE tools during development identifying and addressing common accessibility barriers. We are committed to conducting formal accessibility testing with assistive technology users for future releases and welcome feedback from users requiring accessibility accommodations to improve service inclusivity.
• API: Yes
• What users can and can't do using the API: TestFyra provides custom API implementations tailored to client requirements rather than standardized product APIs. Typical capabilities include programmatic test execution, real-time status monitoring, automated result retrieval, performance data extraction, and CI/CD integration. Users can automate testing workflows, integrate with DevOps pipelines, and generate custom reports.; API limitations defined collaboratively based on security and operational requirements, typically including rate limiting, authentication token expiration, restricted production environment access, and read-only access for sensitive configurations. Specific API capabilities, endpoints, authentication methods, and constraints documented in project-specific specifications ensuring APIs match exact client needs and security policies.
• API documentation: Yes
• API documentation formats:
  • Open API (also known as Swagger)
  • HTML
  • PDF
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: TestFyra services are highly customisable to match specific organisational requirements, workflows, and technical environments.; What Can Be Customised: Dashboards and reporting formats tailored to stakeholder preferences, alert thresholds and notification rules matching operational priorities, integration points with existing systems (ITSM, monitoring, CI/CD tools), user roles and permissions reflecting organisational structure, automated workflows and business logic specific to client processes, data retention policies meeting compliance requirements, branding elements including logos and colour schemes, and API endpoints for custom integrations.; How Users Customise: Configuration performed through web-based administrative interfaces for standard customisations including dashboard layouts, alert rules, user management, and reporting preferences. Complex customisations requiring code changes (custom integrations, workflow logic, API extensions) delivered through change request process with TestFyra development team implementing modifications. Infrastructure-as-code configurations enable version-controlled customisation management.; Who Can Customise: Administrative users with appropriate permissions can perform standard customisations through web interface including dashboard modifications, alert configurations, user management, and report generation. Technical customisations requiring code changes restricted to designated administrators submitting formal change requests. TestFyra provides training enabling client teams to perform routine customisations independently while supporting complex modifications through professional services engagements.

Scaling

• Independence of resources: TestFyra implements strict project isolation to ensure development quality and guaranteed resource availability. Each project is assigned dedicated developers, architects, and AI specialists, preventing resource conflicts across concurrent workstreams. Independent development, staging, and testing environments are maintained per client, ensuring data separation and avoiding cross‑project interference. Capacity planning reserves development resources based on contractual commitments, with new projects accepted only when sufficient availability exists. Separate Git repositories, CI/CD pipelines, and deployment environments provide full code isolation. SLAs guarantee minimum resource allocation with financial penalties for shortfalls. Client‑specific code is never reused, maintaining clear intellectual‑property boundaries

Analytics

• Service usage metrics: Yes
• Metrics types: TestFyra provides comprehensive service metrics enabling performance monitoring and continuous improvement. Metrics include availability percentages, incident response times,resolution times, ticket volumes by severity, service request fulfillment rates, and SLA compliance percentages. Real-time dashboards display current service health, performance trends, and capacity utilisation. Monthly reports deliver detailed analytics covering incident patterns, root cause analysis, service quality trends,improvement recommendations. Custom metrics tailored to client requirements including business-specific KPIs, user satisfaction scores, and operational efficiency indicators. Historical data retention enables trend analysis and forecasting. All metrics accessible via web dashboards, automated email reports, and API exports for integration with client analytics platforms
• Reporting types:
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
• Resource tagging: Yes
• FOCUS resource tagging: No

Resellers

• Supplier type: Not a reseller

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: Security Clearance (SC)

Asset protection

• 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: Supplier-defined controls
• Penetration testing frequency: At least once a year
• Penetration testing approach: In-house
• Protecting data at rest: Encryption of all physical media
• Data sanitisation process: Yes
• Equipment disposal approach: A third-party destruction service
• Data sanitisation type:
  • Deleted data can’t be directly accessed / Cryptographic Erasure
  • Data Erasure

Data importing and exporting

• Data export approach: Users export software and AI assets through structured delivery mechanisms. Source code is provided as a complete Git repository with full commit history, branches, and tags, transferred to client‑owned platforms. Databases are exported using automated backup scripts producing SQL dumps, JSON exports, or CSV files compatible with standard systems. AI models are delivered in framework‑agnostic formats such as ONNX, TensorFlow SavedModel, or PyTorch, including checkpoints and performance metrics. Documentation is supplied in editable formats with training videos. Deployment packages include Docker images, Kubernetes manifests, and infrastructure‑as‑code templates enabling independent deployment.
• Data export formats: CSV
• Data import formats: CSV

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
  • Legacy SSL and TLS (under version 1.2)
• Data protection within supplier network:
  • TLS (version 1.2 or above)
  • IPsec or TLS VPN gateway
  • Legacy SSL and TLS (under version 1.2)

Availability and resilience

• Guaranteed availability: TestFyra guarantees industry‑leading service availability through comprehensive SLAs designed to support critical software, AI operations. Availability commitments structured across three service tiers, each offering defined uptime targets and operational safeguards.; Standard Tier provides 99.5% uptime during business hours (9am–5pm, Monday to Friday), allowing a maximum of two hours monthly downtime. Planned maintenance windows are excluded from calculations and are scheduled outside business hours with a minimum of five days’ advance notice.; Enhanced Tier offers 99.7% uptime across extended operating hours (8am–8pm, Monday - Saturday), permitting up to 1.3 hours monthly downtime. Emergency maintenance is allowed with 24 hours’ notice, while routine maintenance is performed outside supported hours to minimise disruption.; Premium Tier delivers 99.9% uptime on a 24/7/365 basis, with only one to two hours monthly downtime permitted. This tier is supported by fully redundant infrastructure, automatic failover mechanisms, and zero‑downtime rolling updates. Emergency support is available within fifteen minutes.; Measurement/Reporting; Availability is measured monthly, excluding scheduled maintenance windows. Clients have access to a real‑time status dashboard showing current system health ,historical uptime metrics. Monthly SLA reports detail actual performance against agreed targets.; Exclusions; Force majeure events, client‑caused issues, third‑party service failures, scheduled maintenance windows are excluded from availability calculations.
• Approach to resilience: TestFyra’s development methodology and application architecture are designed to deliver strong resilience across the entire software and AI delivery lifecycle. Agile delivery using two‑week sprints enables incremental releases, reducing big‑bang deployment risks and allowing early course correction through regular stakeholder reviews. Continuous integration ensures issues are identified early, preventing late‑stage integration failures. Team redundancy is built in through cross‑training, peer code reviews, and continuous documentation, ensuring no single point of knowledge dependency. Git‑based version control with feature branches supports safe experimentation, while tagged releases provide stable rollback points whenever issues arise.; Application resilience is achieved through cloud‑native design principles, using microservices, containerisation, and orchestration to ensure component‑level fault tolerance. Individual services can restart automatically without affecting the wider system. Database resilience is maintained through replication, automatic failover, and regular automated backups with point‑in‑time recovery. Connection pooling and retry logic mitigate transient database issues. API resilience is strengthened through circuit breakers, timeouts, exponential backoff, and graceful degradation to maintain essential functionality during dependency failures. Infrastructure resilience is supported by multi‑availability‑zone deployments, load balancing, and automated health checks that remove unhealthy instances. AI model resilience is ensured through versioning, rapid rollback, A/B testing, fallback mechanisms that maintain continuity if models become unavailable.
• Outage reporting: TestFyra maintains transparent, proactive communication throughout development delays and production application outages, ensuring stakeholders remain fully informed and able to respond effectively.; Development Phase Reporting; Sprint progress is visible in real time through Jira dashboards showing user story status, blockers, and velocity trends. Daily stand‑ups highlight impediments immediately, enabling rapid intervention. When risks threaten sprint commitments—such as technical challenges, unclear requirements, or resource constraints—TestFyra issues early risk alerts with proposed mitigation actions. If sprint deliverables are delayed, stakeholders receive prompt email notification explaining the cause, revised timelines, and recovery plans, supported by formal change requests where scope or schedule adjustments are required.; Production Application Outages; Each application includes a real‑time status page displaying system health, component availability, and historical uptime. Monitoring systems detect outages within sixty seconds and trigger automated alerts via email, SMS, and webhook integrations. During active incidents, updates are issued every thirty minutes through email, the status page,Teams channels, outlining investigation progress and expected resolution times. Within twenty‑four hours of resolution, TestFyra provides a detailed post‑incident report covering the timeline, root cause, corrective actions,preventive measures.; Support Channels; A 24/7 emergency hotline is available for critical issues under premium tier, with email,ticketing support for non‑urgent matters.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Dedicated link (for example VPN)
  • Username or password
• Access restrictions in management interfaces and support channels: TestFyra enforces strict access controls to protect application administration and development resources. Multi‑factor authentication is mandatory for all access to code repositories, cloud consoles, CI/CD pipelines, production systems, and client data. Role‑based access control ensures developers only access assigned projects and environments, with production access limited to authorised operations staff. Administrative interfaces are restricted through IP whitelisting, allowing access only from corporate networks or approved VPNs. Privileged credentials are stored in secure vaults with time‑limited production access. All administrative actions, including commits, deployments, configuration changes, and data access, are immutably logged.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • 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

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: No
• Security governance approach: TestFyra has established a comprehensive security governance framework in preparation for ISO 27001 certification. A designated Information Security Manager oversees governance with senior management involvement and quarterly security reviews. A full policy suite is in place covering information security, secure development, access control, data protection, incident response, and business continuity aligned to ISO 27001. Risks are identified and mitigated through structured assessments, vulnerability management,penetration testing. Cyber Essentials certification provides validated baseline controls. Secure development follows OWASP guidance with code reviews and automated testing. GDPR procedures are documented. Staff receive quarterly training. Internal audits are complete, with certification expected in 2026.
• Information security policies and processes: TestFyra maintains comprehensive information security governance aligned with international standards to ensure the protection of client systems, data, and AI assets. Its Information Security Management System (ISMS) is progressing towards ISO/IEC 27001:2022 certification, covering all testing services and supporting infrastructure. Annual surveillance audits maintain compliance, while the policy framework is reviewed quarterly to address emerging threats.; The Secure Development Policy Framework includes OWASP‑aligned secure coding standards, mandatory peer code reviews with a security focus, and rigorous security testing through SAST, DAST, dependency scanning, and pre‑deployment penetration testing. Data protection controls ensure client data is encrypted at rest using AES‑256 and in transit using TLS 1.3, supported by GDPR compliance and privacy‑by‑design principles. AI security controls address model poisoning, adversarial robustness, secure deployment, training‑data protection, and explainability for regulated use cases.; Development environments are secured through MFA‑protected version control, branch protection rules, secrets management via vaults, and isolated environments per project. TestFyra also operates a structured compliance framework, holding Cyber Essentials certification and conducting regular independent audits. Third‑party risk is managed through vendor security assessments, strict sub‑processor requirements, and annual external security reviews
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: TestFyra applies disciplined configuration and change management across all development activities. All code, configurations, and infrastructure‑as‑code are stored in Git with atomic commits, descriptive messages, feature branches, pull requests, and tagged releases marking stable versions. Environments are managed through Terraform or CloudFormation to maintain parity across development, staging, and production. Production changes require approval from the technical lead and product owner, supported by automated pipelines with manual approval gates and an emergency hotfix process. All configuration changes are logged, with regular drift detection ensuring consistency and compliance.
• Vulnerability management type: Supplier-defined controls
• Vulnerability management approach: TestFyra proactively identifies, remediates security vulnerabilities:; Continuous Scanning - Automated vulnerability scanning performed weekly across all infrastructure, applications, and dependencies. Critical vulnerabilities flagged immediately.; Patch Management - Critical security patches applied within 48 hours; high-severity within 7 days; medium within 30 days. Emergency patching process for zero-day exploits.; Penetration Testing - Independent third-party penetration testing conducted annually with remediation of identified issues before re-testing.; Threat Intelligence - Subscription to threat intelligence feeds providing early warning of emerging vulnerabilities affecting our technology stack.; Remediation Tracking - Vulnerability management system tracks findings through complete remediation lifecycle with management reporting on security posture.
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: TestFyra maintains 24/7 security monitoring to detect and respond to threats. A centralised SIEM aggregates logs from all systems, using machine‑learning analytics to identify anomalous behaviour and trigger real‑time alerts. Failed authentication attempts, unusual access patterns, data‑exfiltration indicators, malware signatures, and network anomalies automatically initiate investigations. The Security Operations Centre responds to critical alerts within fifteen minutes, with automated containment preventing lateral movement and forensic analysis determining root cause and scope. Response targets include fifteen‑minute response and one‑hour containment for critical incidents, and one‑hour response with four‑hour containment for high‑severity issues.
• Incident management type: Supplier-defined controls
• Incident management approach: TestFyra follows ITIL‑based incident management to ensure rapid, consistent resolution of operational issues. Pre‑defined runbooks guide responses to common incidents such as outages, performance degradation, and security breaches. Incidents can be reported via a 24/7 hotline, email, web portal, or Teams, with automated monitoring generating tickets proactively. Incidents are classified by business impact: Critical, High, Medium, or Low. Engineers investigate with regular status updates, and post‑incident reports are issued within forty‑eight hours detailing root cause and preventive actions. Unresolved incidents escalate automatically at thirty minutes, two hours, and four hours to ensure timely resolution.
• Post-quantum cryptography secure: No

Secure development

• Approach to secure software development best practice: Supplier-defined process

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: TestFyra offers a complimentary 2-hour discovery workshop to assess current testing, infrastructure, or development practices. It includes gap analysis, challenge identification, and initial recommendations. Excludes full discovery assessment, implementation, or detailed documentation. Limited to one session per organization, providing insight into TestFyra’s approach and service fit before commitment.

Discount percentage by annual call-off contract value (excluding VAT)

• Less than £250,000: 4%
• Between £250,000 and £500,000: 7%
• Between £500,001 and £1,000,000: 10%
• Between £1,000,001 and £2,500,000: 11%
• Between £2,500,001 and £5,000,000: 12%
• Over £5,000,001: 14%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: No
• ISO 28000:2022 certification: No
• ISO 9001 certification: No
• Quality management systems (QMS): Yes
• CSA STAR certification: No
• PCI certification: No
• Cyber essentials: Yes
• Please provide your Cyber Essentials Certificate Number: F591209e-cfca-49d7-9cbd-1b984b5acee9
• Cyber essentials plus: No
• Cyber Essentials Alternative: None of the criteria
• 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

    • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d
    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • 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 report and address bullying and harassment
    • Activities to cascade good practice on fair working conditions throughout the supply chain
    • Offer a pay and leave entitlement to all eligible staff who become kinship carers, ideally equivalent to statutory adoption pay and leave
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Monitoring and reporting of gender and ethnicity pay gaps and plans to address them where necessary
    • 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
    • Plans for an appropriate income replacement policy for staff who are required to spend time away from work to care for a sick dependent or close relative
    • Understanding of in-work progression issues affecting 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 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 the contract workforce by providing career advice, and providing opportunities for staff working on the contract with in-work progression career development into known skills shortages or high growth areas
    • 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
    • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
    • 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
    • How these flow down the supply chain and are monitored Illustrative examples include reporting, site visits, audits, etc.
    • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain
    • How the supplier will work with NGOs, trade unions or other businesses to address modern slavery risk
    • Means of influencing staff, suppliers, customers, communities and/or any other appropriate stakeholders with respect to modern slavery risks relating to the contract

  • 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.

    • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Activities to support relevant sector related skills growth and sustainability in the contract workforce. Illustrative examples: careers talks, curriculum support, literacy support, safety talks and volunteering

  • 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 3: Resilient, innovative and flexible supply chains: Support economic growth through enabling resilient businesses, opportunities for small businesses and voluntary, community and social enterprises

    • Understanding of the types of businesses in the market and the level of participation by new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Activities to identify opportunities to open up sub-contracts under the prime contract to a diverse range of businesses, including new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Plans for engaging a diverse range of businesses in engagement activities prior to appointing subcontractors (including activities prior to award of the main contract and during the contract term)
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Advertising of supply chain opportunities openly and to ensure they are accessible to a diverse range of businesses, including advertising all subcontracting opportunities on Contracts Finder
    • Ensuring accessibility to contracting and subcontracting opportunities for disabled business owners and employees
    • Structuring of the supply chain selection process to ensure fairness (e.g. anti-corruption) and encourages participation by a diverse range of businesses, including with regard to new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutual
    • Understanding of local demographics, needs and opportunities for the co-design of the goods, services and works to be delivered under the contract
    • Methods for engaging with different parts of the community (including the education system and charities representing the community) and how communities come together to inform decisions, strategy and projects to leave a positive legacy for future generations
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • Plans for positive actions with community groups.
    • Measures for making facilities used in the delivery of the contract available for community groups, education or training
    • Measures to engage users and communities and build relationships to increase community integration build trust and influence how the contract is delivered
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives
    • Support for community-led initiatives relevant to the contract. Illustrative examples: improving transport links; reducing loneliness; helping with English language proficiency; and facilitating social mixing among people with different backgrounds
    • Collaborating with anchor institutions and community groups to make facilities available for education, training or community events

  • 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
    • Delivery of additional environmental benefits through 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
    • Activities to reconnect people with the environment and increase awareness of ways to protect and enhance it

  • 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 employment and skills issues, and of the skills and employment shortages of high growth sectors relating to the contract
    • Understanding of the issues affecting the representation of disabled people in the workforce in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • Collection of the views and expertise of disabled people and their representative organisations on successfully supporting disabled employees or applicants
    • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Introducing transparency to pay and reward processes
    • Offering a range of quality opportunities with routes of progression if appropriate, e.g. T Level industry placements, students supported into higher level apprenticeships.
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Other measures to provide equality of opportunity for disabled people and those with health conditions into employment, including becoming a Disability Confident employer and inclusion of supported businesses in the contract supply chain
    • 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: 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 7: Creating a pipeline of opportunities: For the contract workforce, reducing barriers to entry for under-represented groups.

    • Understanding of the issues affecting the development of new skills by target cohort
    • Understanding of the underlying factors affecting improvements to reduce barriers to entry and training schemes for the target cohort(s) related to the contract workforce
    • Other measures to offer development opportunities for the target cohort(s) in the contract workforce
    • Understanding of issues relating to entering the contract workforce
    • Creation of outreach activities to create a pipeline of employees for the future contract delivery
    • Content of the outreach activity is designed to suit the target cohort
    • Advertising, promotional and outreach activities designed to raise awareness of the offer to reach the target cohort

  • 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
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition
    • Actions to invest in the physical and mental health and wellbeing of the contract workforce

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

Request an accessible format

If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at contact@testfyra.com. Tell them what format you need. It will help if you say what assistive technology you use.