Wrist and finger hardware
Who wears it matters as much as what it measures — the same identity logic applies to a watch on one resident in a shared flat.
- Home
- AI Memory Platform
AI Memory Platform: One Device, Several People — and the Manufacturer Keeps Control
A companion robot in a living room, a learning device in a shared flat, a unit in a care-home room: within a day it is spoken to by a resident, two relatives, a carer on shift and someone passing through. Most products treat all of that as one speaker, which is why the memory, the permissions and the privacy all blur. We deploy the missing layer — who is speaking, what may be remembered, what must be deletable — as a hosted integration for hardware makers, free of a platform licence fee for a small number of evaluated partners each quarter.
Free: hosted standard integration + 6 weeks of engineering support · Paid: private deployment, data migration, deep customisation, 24/7 operations
Why we give this away
Hosting is the part we can still be responsible for
Deployment itself is the cheap week. The expensive part is every day afterwards: upgrades, backups, certificate rotation, alert response, and who picks up the phone when something fails at night.
So the split follows the responsibility, not the marketing. We give away the layer where we remain the operator — a hosted tenant per product line, with our own monitoring and our own name on the incident. We charge for the layer where the machine sits in somebody else's datacentre and our engineer and your IT point at each other across a firewall while a product launch waits.
That is also why this is a quota, not an open door. Two or three partners per quarter, evaluated on a real product and a real production plan. An unlimited free offer attracts exactly the projects that consume an engineering team and ship nothing.
What a partner can verify in the first meeting, not in year two: register two voices in one room and ask each a different question; ask the console to export one member's record and nothing else; delete one member's data and prove it is gone from the live record, the index and the cache; then ask who can see a carer's own conversation. If a supplier cannot demonstrate those four in front of you, the architecture is not there.
What we will not build for you: medical framing. We do not write fall prevention, remote monitoring as medical supervision, or "help is certain to arrive" into a manual or a listing. A device describes; a person interprets and signs.
The offer
What is free, and what is deliberately not
| Included at no platform licence fee | What you actually get | Duration |
|---|---|---|
| Dedicated hosted tenant | Isolated per product line: accounts, device registry, voiceprint store, memory storage and retrieval, per-resident partitions. No shared data space with another brand. | From integration until six months after your first production run |
| Standard capability integration | Voiceprint enrolment with an explicit "unidentified" state, per-member memory isolation, content permission tiers (child / adult / caregiver), family whitelist calling, per-person export and deletion. | |
| Tooling and documentation | SDK and API reference, pairing and binding flow, operations console with shift-handover records and read-attribution, staged rollout and rollback. | |
| Six weeks of engineering support | One technical contact and one project contact, joint firmware debug against your samples, and a written acceptance review at pilot end. |
| Not free | Why it is priced |
|---|---|
| Private deployment into your or your customer's datacentre | Implementation plus certificate rotation, backup and restore drills, upgrade windows and on-call — an ongoing operational relationship, not a one-off install. |
| Migration of existing accounts and data | Your users' history has to move without inventing a schema nobody signed off. This is where trust is lost if it is done carelessly. |
| Deep customisation | Your own models, private content policy, sector compliance packs, custom review workflows. Each one changes the audit story we have to be able to tell. |
| On-site and 24/7 operations | Response commitments require staffed rotations. We will not sign a number we cannot answer at 3 a.m. |
Fit
Who qualifies for a quarterly slot
- A real productAI hardware in sale or design-frozen: toys, companion or service robots, elder-care devices, wearables, translation hardware
- A first run of 300 units or moresolution houses may substitute a frozen reference design plus a customer order intention
- An app, or a definite plan for oneotherwise the account and consent surface is our work instead of yours, and we scope it as such
- Acceptance of the four data and exit termsbefore integration, not at renewal
- Two or three partners per quarterordered by application date, so our engineering calendar stays honest
Send these four and you get a written feasibility answer within one business day — what works, what does not, and where the boundary is:
- Product and module — category, main SoC, screen or no screen, camera or no camera, launch status and first-run quantity.
- Current state — existing app or mini-program, any account system, any cloud, any memory feature already shipped.
- Scenario — one person one device, shared household, or one device per care-home room; whether children or older users are involved.
- Decision path — who signs, and the date the feature has to be demonstrable.
Delivery
Six weeks, in writing
| When | We do | You do |
|---|---|---|
| D0 | Feasibility answer: can do / cannot do / where the line is | Send the four items above |
| Day 5 | Integration plan, account and permission model draft | Confirm data fields and branding scope |
| Weeks 1–2 | Tenant opened, device registry, provisioning and pairing joint debug | Provide sample units and current firmware |
| Week 3 | Voiceprint enrolment, member isolation and permission tiers working | Internal trial with your own households |
| Week 4 | Calling path: whitelist, missed-call escalation, one attributable record per call | Agree the family-facing wording and console fields |
| Week 5 | Handover records, audit trail, staged rollout and rollback rehearsed | Pick one real setting: a household or one care-home room |
| Week 6 | Pilot acceptance review, production integration schedule | Decide on production and commercial terms |
What you put in — said up front, because this is where free projects die. One engineer for firmware, pairing and the app; one product owner for permission scopes and wording; pilot devices and testers; and your own privacy notice. We supply the data-flow description, the field list and templates, but the party that tells the user what is happening is the brand, not the platform vendor.
Operations
Who does what after go-live
| Responsibility | Hosted integration (free) | Private deployment (paid) |
|---|---|---|
| Upgrades and rollback | Us, with a notified window | Your team, from our package and runbook |
| Backup and restore drill | Us; recovery target written in the agreement | Your operations |
| Certificates and key rotation | Us | Your operations |
| Incident response | Critical faults answered within 4 hours; other issues next business day | Only under a signed operations contract — we do not sell an on-call rotation we cannot staff |
| Data location and processor identity | Stated in the data-processing agreement | You decide, you carry the compliance |
The four exit terms, before integration
- The data belongs to the brand. For end users, the brand is the controller and we are the processor.
- Full export, self-service. Members, memories, permission scopes and audit logs, in a documented format, without a support ticket.
- Deletion that is verifiable. Live records, derived indexes, caches and export packages, with a stated deadline — a delete that clears one table is not a delete.
- Termination defined. Who may push firmware afterwards, for how long we support in parallel, and when our copies expire.
Related engineering reading: the platform journal index, AI health monitoring notes, one device per room, care-home data isolation, family calling — and how the hardware itself is built and tested on the factory page.
Apply for a slot
Two to three partners per quarter
Send the four items and we answer within one business day: whether it can be done, where the limits are, and which of our engineers would sit on it. No list purchase, no newsletter, no fee to ask.
- Answered byan engineer plus a project contact, not an autoresponder
- You receivefeasibility answer, permission and data model draft, six-week plan, the free-window terms in writing
- Not acceptedconcept-stage projects, competitor intelligence, or medical or safety claims we cannot evidence
Prefer to talk? WhatsApp the factory or write to wangkf@wingworld.cn.
Questions manufacturers ask first
- Do you keep the audio?
- No. A non-replayable voice feature is extracted on the device and the audio is discarded after processing. What persists is the feature, the text memory and attribution — stored apart from the identity table, so a single breached store cannot be reassembled into a named person.
- What happens when the device is not sure who is speaking?
- It says so. Unidentified speakers get shared content and no memory write. Silently assigning a sentence to somebody is how both memory pollution and privacy incidents actually happen, and we will not ship that behaviour to protect a demo.
- Can it tell two children of similar age apart?
- That is the hard case, not the easy one — similar voices, both developing. We do not publish an accuracy figure for it; we ask to test in your household or your rooms, because the answer depends on the acoustic reality of the place, not on a datasheet.
- Does the free window end abruptly?
- No. It runs from integration until six months after your first production run; the terms are given before work starts rather than at renewal, and anything you have exported remains yours whatever happens next.
- We already have an app and a backend. Is this still useful?
- Usually the value is narrower and more concrete: voiceprint routing, per-member isolation, deletion propagation and the audit trail are the parts nobody enjoys building. We integrate behind your app rather than replacing it, and the account model stays yours.
- Can you make our device a medical or safety product?
- No, and we will not write the wording that pretends otherwise. A device describes what it observed; a person interprets it. Claims that a device prevents falls, or that help is certain to arrive, are the fastest route to a liability you cannot transfer to us.
Where this sits next to the hardware
Companion and service robots
Illustrative rendering. The devices most often asked for this layer, and the ones where a blended persona breaks the product.
OEM and ODM work
Branding, firmware, app skin and now the memory layer — one scope conversation rather than three vendors arguing.
Two to three slots this quarter
Send the four items — product and module, current app, scenario, decision path. A feasibility answer within one business day, including what we would refuse to build.