Early access. The sandbox is open now; production keys open at launch. How going live works
An embeddable wellbeing pulse, by iframe or API

Give your customers workforce wellbeing measurement they can trust.

The Intelligent Wellbeing Engine is an embeddable wellbeing pulse API. It adds an anonymous three-question check-in to your product, every fortnight. Employers get results with the anonymity rules enforced in the database, so they can show the numbers to anyone. You can build in the sandbox today, and you pay per enrolled user.

10p per enrolled user per month £250 monthly production minimum n≥5 anonymity, enforced by the database

For your engineers: one iframe or a REST API, an OpenAPI spec, and sandbox keys from one call. Watch a number refuse to exist ↓

Built for

HR and people software

HRIS, payroll, rota and scheduling, intranet and internal comms, learning platforms. For platforms.

EAP and occupational health

A workforce signal each fortnight, next to the services you already run. For EAP and OH providers.

Benefits providers

Measurement that sits inside the benefits your clients already give their people.

Employee apps

Frontline and staff apps with a signed-in workforce.

Honesty you can poke

Every wellbeing vendor promises anonymity. Ours is a database CHECK constraint: below five respondents, the value is never stored or returned, so there is nothing to leak, subpoena, or "enterprise-export". Drag the slider. (Simulated data.)

9

The interval uses the real t-quantile for the group size, so small groups get honestly wide ranges. Groups of 5 to 9 are labelled provisional. Below 5, the engine refuses, and the row stores only why it is withheld.

Three things nobody else ships

Structural honesty

The n≥5 floor is CHECK-constrained in the schema. Every figure carries a true 95% interval, its group size, and the completion rate. Suppressed results export their absence, with a coded reason. Your dashboard cannot lie with our numbers, and we certify that before production keys. The full statement is in the honesty rules.

An open standard underneath

Aggregates export as JSON reports modelled on the OWHS aggregate report, an open format your compliance team can read. Your data are portable by design, so the engine has to win on quality. What the export contains.

Safeguarding ships locked

Crisis signposting and safe-messaging copy are part of the engine, rendered from our origin inside the embed, external-first, never editable by the host and never paywalled. Nobody ever sees a personal score, on any surface, and no setting changes that.

Integrate in three steps

Built to be integrated by your team, or your team's AI coding assistant. The OpenAPI spec, docs and this page are machine-readable on purpose. Start at the quickstart.

Sandbox in minutes

Self-serve keys against a synthetic workforce. Run a full cycle, watch suppression fire, pull an OWHS export, before any contract or real user exists.

Embed or go headless

Drop the check-in iframe into your app (a few lines of your own code, postMessage events), or build your own surface on the headless API. The embed quickstart. Your push rails deliver; our API enforces the one-reminder cadence.

Certify, then production

An automated conformance check plus a human review of your rendering (intervals shown, provisional badges, no invented benchmarks) earns production keys and the IWE Certified badge. See every step to going live.

Build it with your AI assistant

Paste this into Claude Code, Cursor or any coding assistant that can read the web. It points the assistant at the guide and the OpenAPI spec and builds against the sandbox, with synthetic people only.

Integration prompt
Integrate the Intelligent Wellbeing Engine (IWE) into this codebase, against its sandbox.

Read these first and treat them as the source of truth:
- Integration guide: https://wellbeingengine.io/guide
- OpenAPI spec: https://wellbeingengine.io/docs/openapi.yaml

Then do this, one step at a time:
1. Get sandbox keys with POST https://sandbox.wellbeingengine.io/sandbox/signups. Put client_id and client_secret in server-side environment variables. Never commit them. Never send them to the browser.
2. On the server, swap the keys for a bearer token at POST /oauth/token (client credentials). Cache the token for about 55 minutes.
3. Add a server route that requests an embed token (POST /embed/tokens) for the signed-in user. Identify people only by a stable opaque partner_user_id, never a name or an email address. In the sandbox, use the synthetic ids, for example syn-normal-01.
4. On our wellbeing page, open the returned embed_url in a plain iframe. There is no package to install. Act on a message only if e.origin is the embed_url's origin, e.source is the iframe's contentWindow and e.data.source is "iwe-embed". The first completed event means the answers are saved: keep the frame open, because the thank-you screen shows crisis signposting. Remove the frame on the second completed event (the person pressed Close) or on dismissed. Add your own Close button next to the frame, because an expired token shows an error and sends no message.
5. Add an employer results view that reads GET /aggregates. Show the confidence interval beside every value. Show a provisional badge when method is "indicative". Render suppressed rows as withheld, with their reason and no value anywhere in the page.
6. Use the certification markup (the data-iwe-* attributes in the guide) so the automated conformance check passes.

Use synthetic sandbox data only. Ask me before you change anything outside the files this needs, and explain each change as you make it.

The prompt only uses sandbox keys. Production keys come later, through going live.

One question decides your price

Whose workforce are you measuring? Your own people: it is free, at any size. Someone else's: you are distributing, and you pay. Nobody in this category publishes a rate card; we publish the whole model on the pricing page.

Measuring your own workforce?

You are in the wrong place, happily. The IWE is free for any employer, forever, at alltoogether.com, including embedding the check-in in your own intranet from your account. There is no card to enter and no call to book. This site is for people building it into products.

Building it into your product? You are home.

Embedding the IWE in a product or service you offer to others: platforms, EAPs, benefits providers, apps. Per enrolled user per month, volume terms above 100,000 users, and each production licensee will have its own database. Certification before production keys. The sandbox's database is hosted in London (UK) and its API runs in Dublin (Ireland). Production is designed to use the same regions. Deep dives come later as an add-on tier.

Researching workplace wellbeing?

Accredited institutions doing bona fide research can use the engine free by agreement: ethics approval, cite the engine and OWHS, publish openly. Email us and we will talk it through.

10p per enrolled user per month, up to 100,000 enrolled users
  • Tier 1: fortnightly pulse engine, honest aggregates, OWHS export, embed surface and headless API, webhooks, usage metering both sides can see
  • Tier 2: validated deep-dive instruments, employee opt-in, n≥5 reporting. Coming, not sold yet: £1 per completed deep dive when it opens
  • £250 a month minimum in production, which covers the first 2,500 enrolled users. No integration fee when you build it yourself
  • Tier 3: intervention signposting to your own service catalogue is coming. It switches on per deployment once its gates are met. Crisis safeguarding is external-first and always on in every tier
  • Above 100,000 enrolled users: volume terms and floor-plus-share structures. Consumer or no-employer deployments are a different product, priced per deployment
Measuring your own people never costs money, hosted or embedded, five staff or fifty thousand. If we ever break that, do not license from us. See the full rate card.