ambivalence is designed to run at council scale — multi-tenant, analytics-rich, and interoperable with whatever LMS your organisation already uses. Single authority, combined authority, mayoral office, or national body: we align how you licence the platform with the way your organisation already works.
Every institutional deployment includes the core three capabilities below. Anything else — cohort design, custom rubrics, white-labelled badges — is a conversation, not a paywall.
Your own isolated workspace. Create cohorts, assign episodes, issue invite tokens, manage seats and licence periods from a single admin dashboard — no support ticket required for the everyday things.
Active learners, badge distribution, domain strength, completion rates — sliced by cohort and role. The kind of evidence that wins the next training budget conversation, not the kind that gets hand-waved.
Full Arabic localisation with RTL support; French, German, and Japanese infrastructure in place. Targeting WCAG 2.2 AA. Read the accessibility statement →
Most teams begin with a short call and a clear pilot shape: who the first learners are, what success looks like, and how ambivalence sits next to your existing L&D stack. From there we stay alongside your procurement and governance colleagues — no need to unpick your internal process on a marketing page.
We agree scope, timeline, and support together before anything is signed. You get plain language on what's in the licence, what we run for you, and what your team owns — then a proposal your organisation can take through its usual approvals.
We're set up to work with the ways UK public organisations typically procure learning and digital services. If your organisation uses a particular framework or panel, we'll map to it with your commercial team — you don't need the detail here to book an initial conversation.
If you prefer to buy through an L&D partner, university, or consortium you already trust, we can support that model. The goal is the same: your people get ambivalence without unnecessary friction.
Every episode and interaction in ambivalence maps to a specific rubric cell in the 9 × 4 competency framework. Progress is never a completion percentage — it's an evidence-backed position on a civic competency map your organisation can audit, report on, and share. When learners cross a cell's rubric threshold, the platform issues a signed Open Badges 3.0 credential that goes with them.
ambivalence is built to sit alongside your existing LMS, not to replace it. Learning data flows from ambivalence into your central reporting via xAPI — so you don't have to ask your organisation to make a hard choice between platforms.
Compatible with Moodle, Canvas, Blackboard, Totara, or any LRS-connected platform. Learners access episodes through ambivalence; records flow into your centralised reporting.
We can operate a managed Learning Record Store on your behalf, or point ambivalence at your own LRS endpoint. Data residency stays UK/EU throughout.
Where xAPI isn't available, we provide a SCORM 1.2/2004 wrapper for direct LMS import — useful for legacy infrastructure, at the cost of less granular data than native xAPI.
All platform data lives on UK/EU infrastructure. We operate under UK GDPR and provide a Data Processing Agreement as standard with any institutional licence. Our security posture is aligned to the NCSC Cloud Security Principles, and we benchmark against ISO 27001 and the NHS DSPT.
Thirty minutes, no deck required. Tell us the shape of your organisation, your L&D stack, and what a sensible first step would look like. We'll follow up with a concise proposal you can share internally.
Slots are drawn live from our team calendar and refreshed every working day — if it's shown here, it's genuinely open. Click a slot to open a pre-filled email; we'll confirm by reply within one working day, or propose the nearest alternative. Prefer a different time? Email us directly.