VisionVision · not available today. Satin never runs on banking or payment pages.
Where OwnUX is goingClaims, approvals and applications people can follow. Every customer sees where they stand and what’s next.
Vision · SDK in development · Illustrative screens · Never on banking or payment pages
Claim CL-20481 · Motor, own damage
Pending adjudicationSurveyor assessment in progress. Awaiting repair estimate (CL-7).
Action required
Outstanding: supplementary documentation, repair estimate (form CL-7). Assessment SLA paused pending receipt.
Where customers get lost, and what changes. Long journeys, codes, jargon. OwnUX lets each person read the same journey their way.
Where they stand. Each stage of a claim or application in plain or expert words, current one marked.
What to do next. One clear next step, written for the reader, instead of a list of reference codes.
Their language and reading level. From the translations and plain versions your team writes and approves.
Larger text, calmer layouts. Text size, contrast and density from the customer’s Interface DNA, across every adaptable screen.
Staff views that fit the job. Claims handlers, underwriters and managers each get their preferred density and terms, under the same permissions.
Keyboard-first back office. Queues and approvals with shortcuts that stay the same from screen to screen.
Locked surfaces
Money screens stay yours. OwnUX adapts the journey around them, never the screens themselves.
Payments, account and card details, sign-in, one-time codes, terms and consent are always listed as locked. OwnUX never touches them: they render exactly as you built them. Only the journey around them, such as a claim’s status, could adapt.
- Locked screens are never re-rendered, whatever a person asks for.
- Business logic, data and permission checks stay in your backend.
- OwnUX never takes a sensitive action on its own.
Personal loan application
3 sections adapt · 3 stay locked
About you
Their language, reading level, layout and text size, from their Interface DNA.
- Language
- Reading level
- Layout
- Text size
Two products, one clear line. This page describes a future use of the SDK. Neither product runs on banking or payment pages.
The Satin extension
For people in work apps, in development: Jira Cloud first, then Linear
- Never runs on banking or payment pages
- Never reads password or card fields
- Never moves money or trades
- Planned for the beta: stands aside on any product that has OwnUX built in
The OwnUX SDK
Vision: for providers, inside their own claims and application journeys
- Runs in your frontend, with your components and tokens
- Adapts only the screens you allow
- Calls your own API, which keeps every permission check
- Leaves your locked screens exactly as you built them
- Never on online banking or payment pages: those stay locked
Start with one journey. How a provider brings OwnUX to its customers.
- 1
Pick the journey
Start where customers struggle most, such as a claim status page or an application form.
- 2
Declare, then lock
List the actions OwnUX may offer and the screens it must never touch, in one capability manifest.
- 3
Run ownux test
Check that every action executes, verifies and fails safely, including when permission is denied.
- 4
Measure against a holdout
Roll out to a share of customers and compare your agreed metric with people who don’t have OwnUX.
In developmentThe OwnUX SDK is in development. Today’s alpha runs in our Reference App, works with React and covers tasks. Claims and applications need capabilities beyond the alpha.
Questions, answered.
No. Satin never runs on banking or payment pages, and never reads password or card fields. This page describes a possible future use of the OwnUX SDK in claims and application journeys, not online banking.