AWS Software / SaaS United Kingdom

Humanising Autonomy

Risk Management

The company’s goal is to make automation human centric by teaching machines to better understand people and using this layer of human context to help companies develop next-generation products and services, create safer environments for people, and to elevate the customer experience.

Using AWS, it takes just 30 minutes.
“Using AWS, it takes just 30 minutes and all it needs is a few minutes to set up.

Reported impact

Business outcome

Using AWS, Humanising Autonomy has launched its new software-as-a-service platform to improve its customers’ experience, make engineering processes smoother, and help it grow.

  • Risk Reduction
  • Scalability
  • Speed to Market

Solution

Humanising Autonomy was already using Amazon Web Services (AWS) for training, researching, and refining its machine learning (ML) models. Humanising Autonomy decided to expand its use of AWS and now uses multiple services for its customer-facing website, which lets users access software and other services. The company processes a vast amount of data uploaded from CCTV cameras, in-vehicle dashcams, and other input devices. Whether it’s metadata or raw data generated from these devices, Humanising Autonomy uses AWS encryption services—such as AWS Key Management Service and AWS CloudHSM—to take measures to protect, secure, and anonymize data that it processes on behalf of its customers.

Data flow

This capability is made possible by Amazon Simple Storage Service (Amazon S3), which is capable of retrieving vast amounts of data from multiple locations to allow Humanising Autonomy’s customers to connect to its software.

Solution architecture

5 components · 5 layers
  1. Compute
    • Amazon EC2 Provides elastic compute capacity for application, analytics, and infrastructure workloads.
  2. Storage
    • Amazon S3 Stores datasets, objects, model artifacts, or binary assets at scale.
  3. Serving
    • Amazon API Gateway Publishes and secures APIs that front application and model services.
  4. Orchestration
    • Amazon EventBridge Coordinates event-driven processing across application components.
  5. Governance
    • Amazon CloudWatch Monitors application, infrastructure, and operational health signals.

Architecture clues

  • Humanising Autonomy has used AWS to build a serverless online platform and a scalable infrastructure that can expand as the business grows.
  • Humanising Autonomy uses a number of services to uphold applicable data privacy standards and the company’s policies on the ethical use of personal data (for example, any persons appearing in images taken by any of the cameras or input devices owned by its customers).
  • It maintained its local edge machines for near real-time image processing, but used AWS for many of its workloads, from finance and human resources systems to sandboxed AI development and research, and delivering final software to customers.
  • The services— AWS X-Ray Amazon CloudWatch AWS Control Tower —help Humanising Autonomy monitor and manage internal developer access to such personal data, ensure tight controls over its personnel to maintain high compliance and security standards, and deliver appropriate separation firewalls over its customer’s data.

Evidence from the source

For example, in Nextbase dashcams, Humanising Autonomy’s software flags collision warnings and driver blind spots.
Humanising Autonomy, founded in 2017 by Maya Pindeus, Raunaq Bose, and Leslie Nooteboom, develops ethical behavior AI that is changing how machines understand people.
Humanising Autonomy’s AI software analyzes, classifies, and interprets human behavior captured from video cameras, using both live, real-time footage, and historic, pre-recorded footage.
Humanising Autonomy’s technology considers the cognitive processes people use every day to understand the social and environmental context of what’s happening around them—and translates this into a language that machines can understand.
The company’s goal is to make automation human centric by teaching machines to better understand people and using this layer of human context to help companies develop next-generation products and services, create safer environments for people, and to elevate the customer experience.
Transparency Evidence & methodology 95/100 reference value · 87% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value95/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth20/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence87%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. AWS

    Humanising Autonomy customer story

    First-party
    https://aws.amazon.com/solutions/case-studies/humanising-autonomy/
    Source type
    Vendor-published customer story
    Published
    Jan 2, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.