Remarkable

Contentful CMS

Contentful is a headless content management system (CMS). It lets you create, manage, and edit the content on your website or app without it being directly tied to the design or layout. This allows for greater flexibility and makes it easier to deliver content across different channels.

Features

• Content Modeling
• User-friendly Interface
• Multi-language Support
• Collaboration Tools
• API-first approach
• Composable Content
• Omnichannel Delivery
• Scalability
• Role-based access control and disaster recovery plans

Benefits

• APIs streamline integration with existing systems
• Fast time-to-market for new content and campaigns
• Front-end technology is unique to each project
• Localised experiences for your audience
• Collaboration among editors, streamlining workflows
• Content is delivered through APIs
• Deliver content through various channels (websites, apps, digital displays)
• Unify content into a single content hub
• Increase reusability and scalability

• 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 paul@remarkable.global. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

125215970117417

Contact

Paul Stephen
07785 523033
paul@remarkable.global

About your service

• Service categories:

  Applications

  Content workflow and management

  Content services

  • Enterprise Content Management Applications
• Multi cloud support: No

Service scope

• Software add-on or extension: No
• Cloud deployment model: Public cloud
• Service constraints: The service is delivered as a fully managed Software-as-a-Service platform. Buyers do not manage or control the underlying cloud infrastructure or data residency. The service is accessed over the public internet and requires compatible web browsers and network connectivity. Configuration and customisation are provided within the standard capabilities of the service rather than bespoke changes to the underlying platform.
• System requirements:
  • Accessed through a browser
  • Requires public internet
  • Standard https connectivity

User support

• Email or online ticketing support: Yes, at extra cost
• Support response times: Support queries are acknowledged and responded to within one business day during business hours. Issues are prioritised based on impact and urgency, with critical issues handled as a priority.
• 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: Yes, at extra cost
• Support levels: Support is provided through email and an online ticketing system during business hours. Requests are logged, tracked, and prioritised based on impact and urgency.; ; Standard support includes assistance with service usage, configuration guidance, and issue investigation. Higher-impact issues are prioritised for faster response, and where appropriate, issues are escalated to the underlying software provider. Support levels are designed to ensure effective issue resolution while minimising disruption to service use.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Users are supported through a structured onboarding process. This includes initial account setup, guidance on configuring content models and workflows, and access to documentation and support resources. Additional onboarding assistance, such as configuration guidance, integration support, and introductory training, can be provided to help users start using the service effectively.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: When the contract ends, users can extract their data using the service’s standard export functionality and APIs. Content and related data can be exported in commonly used formats to support reuse or transition to another service. Access is maintained for an agreed offboarding period to allow data extraction before the account is closed.
• End-of-contract process: At the end of the contract, the service enters an offboarding period during which users can access the service to extract their data using standard export tools and APIs. Once offboarding is complete, access to the service is withdrawn and the account is closed in line with the service’s offboarding and data management processes. Data is handled in accordance with applicable data protection requirements.
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: No
• Designed for use on mobile devices: Yes
• Differences between the mobile and desktop service: The service is accessible on both mobile and desktop devices using supported web browsers. On mobile devices, the interface is optimised for smaller screens and supports viewing and basic content management tasks. The desktop interface provides the full range of features and is recommended for more complex content editing, configuration, and administrative activities.
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: The service provides a web-based user interface accessed through a supported web browser. The interface allows authorised users to create, edit, and manage content, configure content models, manage workflows and environments, and administer user access and permissions. The interface is designed to support content management tasks in a structured and controlled manner.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: Accessibility testing is carried out as part of the service’s design and quality assurance processes. This includes testing the user interface with assistive technologies such as screen readers and keyboard-only navigation to assess usability and accessibility. Findings from this testing are used to identify issues and inform ongoing improvements to the service.
• API: Yes
• What users can and can't do using the API: The API allows authorised users and systems to access, create, update, and retrieve content and related metadata, and to integrate the service with external applications. APIs support content delivery, content management, and automation of content workflows.; ; Administrative activities such as service provisioning, billing management, and certain configuration and user management functions are restricted to the service’s management interface and cannot be performed through the API.
• API documentation: Yes
• API documentation formats:
  • HTML
  • PDF
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: Users can customise the service through configuration options within the platform. This includes defining and managing content models, workflows, roles and permissions, environments, and content structures. Users can also customise how content is delivered and integrated with other systems using supported APIs. Customisation is provided within the standard capabilities of the service rather than bespoke changes to the underlying platform.

Scaling

• Independence of resources: The service is delivered using a multi-tenant, cloud-native architecture designed to isolate customers from one another. Capacity management, scaling, and performance controls are managed centrally to ensure consistent service levels. Usage by one customer does not directly impact the performance or availability experienced by other users.

Analytics

• Service usage metrics: Yes
• Metrics types: The service provides usage and operational metrics through built-in dashboards and reporting features. These include information on content activity, API usage, environments, and user activity. Metrics are available to authorised users through the service interface and APIs to support service management and monitoring.
• Reporting types:
  • API access
  • Real-time dashboards
• Resource tagging: No
• FOCUS resource tagging: No

Resellers

• Supplier type: Reseller providing extra support
• Organisation whose services are being resold: Contentful GmbH

Staff security

• Staff security clearance: Other security clearance
• Government security clearance: Baseline Personnel Security Standard (BPSS)

Asset protection

• Knowledge of data storage and processing locations: Yes
• Data storage and processing locations:
  • European Economic Area (EEA)
  • Other locations
• User control over data storage and processing locations: No
• Datacentre security standards: Managed by a third party
• Penetration testing frequency: At least once a year
• Penetration testing approach: Another external penetration testing organisation
• Protecting data at rest:
  • Physical access control, complying with another standard
  • 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 importing and exporting

• Data export approach: Users can export their data using the service’s standard export functionality and APIs. Content and related data can be extracted in commonly used formats to support reuse or transition to another service.
• Data export formats:
  • CSV
  • Other
• Other data export formats: JSON
• Data import formats:
  • CSV
  • Other
• Other data import formats: JSON

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: The service is designed to provide high availability using resilient, cloud-based infrastructure. Availability is monitored continuously, and operational processes are in place to minimise service disruption.
• Approach to resilience: The service is delivered using a cloud-native architecture designed for resilience. This includes redundancy across infrastructure components, automated monitoring and alerting, and managed scaling to respond to changes in demand. These measures help minimise the impact of component failures and support continued service availability.
• Outage reporting: Service outages are reported through service notifications and support channels. Users are informed of significant incidents and provided with updates until the issue is resolved.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
• Access restrictions in management interfaces and support channels: Access to management interfaces and support channels is restricted to authorised users only. Access is controlled through authenticated user accounts with role-based permissions, ensuring users can only access functions appropriate to their role. Administrative access is limited to designated personnel and protected using additional security controls such as multi-factor authentication. Access to support channels is restricted to authorised customer contacts, with requests logged and tracked through controlled ticketing processes. Access rights are reviewed and updated as roles change or access is no longer required.
• Access restriction testing frequency: At least once a year
• Management access authentication:
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • 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 contact the support team to get 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: The organisation operates an information security management framework aligned with ISO/IEC 27001. This includes policies and processes for risk assessment, access control, secure development practices, vulnerability and patch management, incident management, data protection, and continuity planning. These policies are maintained and reviewed on an ongoing basis.
• 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: Configuration and change management are governed by documented processes aligned with recognised industry standards. Changes are assessed for risk and impact, reviewed and approved prior to implementation, and tested before deployment. Changes are implemented in a controlled manner, with monitoring in place to identify issues and support rollback where necessary. Configuration baselines and changes are recorded, and processes are reviewed regularly to ensure continued effectiveness.
• Vulnerability management type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Vulnerability management approach: Vulnerabilities are managed through a documented process aligned with recognised security standards. This includes regular vulnerability scanning and assessment, independent security testing, and review of security advisories. Identified vulnerabilities are assessed for risk and prioritised based on impact and likelihood. Remediation actions are tracked and implemented in a controlled manner, with verification to confirm resolution.
• Protective monitoring type: Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
• Protective monitoring approach: Protective monitoring is carried out through continuous logging and monitoring of the service to detect security events and anomalous activity. Logs and alerts are reviewed to identify potential incidents, and monitoring outputs are used to support investigation and response activities. Monitoring processes are aligned with recognised security standards and are reviewed and updated on an ongoing basis.
• 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: Incident management is governed by documented processes aligned with recognised industry standards. Security and service incidents are identified through monitoring and reporting mechanisms, assessed for impact and severity, and managed through defined response and escalation procedures. Incidents are investigated, actions are taken to contain and resolve the issue, and lessons learned are used to inform continuous improvement
• Post-quantum cryptography secure: No

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: No
• Free trial available: Yes
• Description of free trial: A free version of the service is available for users to explore and evaluate core functionality. The free version provides limited access to content management features and is intended for evaluation and non-production use. Usage limits apply, and advanced features, higher usage thresholds, and production use require a paid subscription.

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

• Less than £250,000: 5%
• Between £250,000 and £500,000: 10%
• Between £500,001 and £1,000,000: 10%
• Between £1,000,001 and £2,500,000: 10%
• Between £2,500,001 and £5,000,000: 10%
• Over £5,000,001: 10%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: Yes
• Who accredited the ISO/IEC 27001: NQA
• ISO/IEC 27001 accreditation date: Tuesday 6 February 2024
• What the ISO/IEC 27001 doesn’t cover: The supplier’s ISO/IEC 27001 certification covers the information security management system (ISMS) operated by the supplier, including people, processes, and systems under the supplier’s direct control.; ; The certification does not extend to the underlying cloud infrastructure or SaaS platforms operated by third-party providers (such as Optimizely or Sitecore), which are outside the supplier’s operational control. Those platforms are covered by their own independently audited security certifications and controls.; ; ISO/IEC 27001 certification does not guarantee the absolute prevention of all security incidents, nor does it cover customer-managed configurations, end-user devices, or security controls implemented solely by the customer. Responsibilities are shared in accordance with the service delivery model and contractual arrangements.
• 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: 8e128f4d-1cde-4b93-9caf-a916149b04c3
• Cyber essentials plus: No
• Cyber Essentials Alternative: You do not have a current and valid Cyber Essentials Plus certificate, or will not have in place within 12 months of the date of award but have an IASME certified equivalent.
• 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
    • New apprenticeships on the contract workforce in the relevant area that meet the criteria set out in MAC 1b
    • 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
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • 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
    • 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
    • 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
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Volunteering opportunities for staff
    • 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
    • Means of influencing staff, suppliers, customers, communities and/or any other appropriate stakeholders with respect to modern slavery risks relating to the contract

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 paul@remarkable.global. Tell them what format you need. It will help if you say what assistive technology you use.