Question 1

What is Satin?

Accepted Answer

Satin is the company and the product. For people, it’s a Chrome extension that makes supported apps follow your preferred layout, density, labels and shortcuts. For companies, it’s the OwnUX SDK, which lets every user experience your product their way.

Question 2

What is OwnUX?

Accepted Answer

OwnUX is the technology underneath: a way for a person to define their user experience once, and for software to render itself to fit. Products that pass the OwnUX conformance tests will be able to show the OwnUX Ready badge, which is planned.

Question 3

Where does OwnUX come from?

Accepted Answer

OwnUX is an open specification, started by the Satin team in 2026. It builds on decades of research into adaptive and accessible interfaces, and the specification cites that work openly. Anyone can read it, implement it or help shape it.

Question 4

Haven’t adaptive interfaces failed before?

Accepted Answer

Some have. Menus that rearranged themselves taught people that software which moves on its own is hard to trust, and many customisation tools stayed niche because few people ever set them up. OwnUX works differently. You make every change yourself, and nothing moves on its own. Apps take part on purpose, through the OwnUX SDK, which is in development, or through Satin’s adapters over their official APIs. And setup is designed to take about two minutes, or none at all if you skip it.

Question 5

Who governs OwnUX?

Accepted Answer

Today, the Satin team edits the specification, and Pranav Goswami is its editor. The text is licensed CC BY 4.0 and the reference code Apache 2.0, the working draft is public on this site, and anyone can send proposals and comments to hello@usesatin.com. A public home for the specification, with a written contribution process, is planned. Our intent is to move OwnUX to a neutral standards body once independent implementations exist.

Question 6

What is Interface DNA?

Accepted Answer

Your preference profile: layout, density, navigation, labels, interaction style, guidance and accessibility. You can inspect it, change it, export it and delete it. It’s a set of settings you chose, never a hidden psychological profile.

Question 7

Is OwnUX an open standard?

Accepted Answer

OwnUX is an open specification. Working draft v0.1 was published on 23 October 2026. The text is licensed CC BY 4.0 and the reference code Apache 2.0, and proposals and comments are welcome at hello@usesatin.com. It’s a proposal, not an adopted industry standard: that takes independent implementers, and we won’t claim it before they exist.

Question 8

What is DNA Share?

Accepted Answer

Choosing to share selected parts of your Interface DNA with a product that supports OwnUX. You can untick anything and revoke access at any time. The product never sees your other apps or your work in them. DNA Share is planned.

Question 9

How is this different from a theme or a browser extension that restyles pages?

Accepted Answer

Themes change colours. Satin understands what an app can do, such as tasks, statuses and due dates, and builds a clean interface around those capabilities. Every action is verified with the app itself.

Question 10

Which apps does Satin work with?

Accepted Answer

Jira Cloud and Linear at launch, with Asana a possible third. Products that build in the OwnUX SDK, which is in development, will work with your preferences too. We add apps only when we can support them reliably through their official APIs.

Question 11

What are Personal mode and Familiar mode?

Accepted Answer

Personal mode shows your work in Satin’s own task-first view (Today, Next, Blocked) through the app’s official API. It’s being built now, for Jira Cloud first. Familiar mode keeps the original app on screen with lighter, presentation-only changes. It’s planned for a later phase.

Question 12

What can I do in Satin at first?

Accepted Answer

The five core tasks: view my tasks, find a task, change its status, update its due date and assign an owner. They come first because they’re what most people do every day, in every tracker. Everything else stays one click away in the original app.

Question 13

Does Satin change my data?

Accepted Answer

Only when you ask it to, and only in ways you’re already allowed to. Every change goes through the app’s official API and is read back to confirm it worked. If anything fails, Satin tells you and offers a link to do it in the original app.

Question 14

What happens when an app changes its design?

Accepted Answer

Satin checks each connection when it starts and checks every answer it gets back, with continuous checks coming. If something stops matching, it switches that app back to its original interface and lets you know, so nothing breaks in the middle of your work.

Question 15

Can I always get back to the original app?

Accepted Answer

Yes, in one click, everywhere. Satin works alongside the app rather than replacing it, and the app keeps all of its features. Satin only shows the capabilities it has mapped and can verify.

Question 16

My client’s Jira blocks third-party apps. Will Satin still work?

Accepted Answer

Atlassian administrators can block user-installed apps for a site. If yours does, Personal mode can’t connect there. Familiar mode needs no app connection, so it’s designed as the fallback when it arrives. Satin will never ask for your password or a personal API token instead.

Question 17

Does Satin use AI?

Accepted Answer

Every core flow works without AI. An optional command bar is planned for the beta: you type a request, and Satin turns it into a checked action that you confirm. AI never authorises an action, chooses an endpoint or writes code into a page.

Question 18

How do companies add OwnUX?

Accepted Answer

Describe your product’s entities and actions in a capability manifest, map your design-system components, pass the conformance tests, and roll out to a share of users with a holdout group. Design partners get a free 12-week pilot.

Question 19

What does a product team keep control of?

Accepted Answer

You choose the design tokens, approved components and permitted layouts. Billing, security, consent and compliance screens are locked, so OwnUX never re-renders them. Logic, data and permission checks stay in your backend, and you control rollout percentages, version pins and a kill switch.

Question 20

What is the OwnUX Ready badge?

Accepted Answer

A planned badge for products that pass conformance at level L2 or above. L1 Declared: a valid manifest. L2 Verified: every action passes execute, verify, fallback and permission-denial tests. L3 Adaptive, also planned: adds Interface DNA, accessibility checks and locked surfaces. The badge will always state its level.

Question 21

Which frameworks does the OwnUX SDK support?

Accepted Answer

The SDK is web-first and React-first. It runs today as an alpha inside our Reference App, a small task-management product with its own deliberately non-Satin look, which proves that a vendor’s own design system works.

Question 22

How do we know whether OwnUX helps our product?

Accepted Answer

With a holdout group kept on your standard experience. By default, the SDK holds out 15% of new users, and you can change it. Before a pilot starts, we agree one primary metric, such as 7-day activation. Reporting the result with confidence intervals, never with selected anecdotes, is planned.

Question 23

Can government services, hospitals or banks use OwnUX?

Accepted Answer

Not today: that’s part of our vision. In time, a provider could build OwnUX into its own service with the OwnUX SDK, so citizens, patients and customers could use it in their language, at their reading level and in the layout that suits them. The provider would keep full control of its data and rules, and its payment, account and consent screens would stay locked. Satin never runs on banking or payment pages.

Question 24

What is the design partner programme?

Accepted Answer

A free 12-week pilot for B2B SaaS teams in work management or a nearby field, with a React frontend, a named sponsor and enough new users to measure an effect. We agree the primary metric in writing, support the integration and check in weekly.

Question 25

Can my company see what I do in Satin?

Accepted Answer

No. Your work content stays on your device and never reaches Satin’s servers. Products only receive the specific preferences you choose to share with them, and you can revoke that at any time.

Question 26

Does my work content reach Satin’s servers?

Accepted Answer

No. Satin for People is local-first. The extension calls each app’s API directly from your browser, and task titles, descriptions and comments stay on your device, in memory and a short-lived cache that’s cleared when you disconnect.

Question 27

Where are my app connections kept?

Accepted Answer

Tokens are held only by the extension’s background service worker, never in the page. Linear’s sign-in happens in your browser. For Jira Cloud, a small Satin relay adds the secret an extension can’t hold, never stores or logs tokens, and returns them to your browser.

Question 28

Does Satin run on banking or payment pages?

Accepted Answer

Never. Satin doesn’t run on banking or payment pages, and it never reads password fields or payment-card details. It asks for no site access when you install it, and it stays off on every site until you switch it on.

Question 29

Does our product have to send user data to Satin?

Accepted Answer

No. The OwnUX runtime runs in your frontend. Nothing is hosted yet. When Satin’s cloud launches, it will receive only pseudonymous metering counts, any aggregate analytics you opt in to, and DNA Share grants. It will never receive your users’ content.

Question 30

What can the extension access?

Accepted Answer

Nothing until you switch it on. It asks for no website access when you install it. You then allow one Jira Cloud or Linear site at a time, and that app’s API when you connect. Your tasks come from the app’s official API, never from the page. The only websites it can ever ask for are Jira Cloud, Linear, their APIs and, if you turn on sync, Satin’s own account service. The permissions page lists every permission and what it’s used for.

Question 31

Is the extension code public?

Accepted Answer

Not yet. Until it is, the permissions page lists every permission the extension asks for and what each one is used for, taken from its manifest, and the security page explains how your work and sign-ins are protected.

Question 32

Does Satin have security certifications?

Accepted Answer

Not yet. Satin is pre-launch and holds no security certifications. Before any paid launch, we’ve committed to security testing of the extension, the SDK and our servers, access-control and tenancy tests, and an incident-response procedure.

Question 33

How do I remove Satin completely?

Accepted Answer

Disconnect your apps and remove the extension. You can export or delete your Interface DNA at any time, and the local cache is cleared when you disconnect. Satin is designed to leave nothing behind.

Question 34

How much will Satin cost?

Accepted Answer

For people: free for two supported apps, with Pro planned at ₹399 or $8 a month, or ₹3,999 or $80 a year. For products: a free Sandbox, then production plans from $299 a month. All prices are planned launch prices and may change.

Question 35

What does the Free plan include?

Accepted Answer

The core promise: two supported apps, Familiar and Personal modes, one Interface DNA profile stored on your device, the native fallback, and every safety and accessibility control. It’s planned to stay free for good.

Question 36

Are accessibility features ever paid extras?

Accepted Answer

No. Safety controls and core accessibility are never behind a paywall, on any plan.

Question 37

What is an adapted user?

Accepted Answer

The billing unit for Satin for Products: a distinct person who sees at least one OwnUX surface in your product during a calendar month, counted in UTC. People in your holdout group never see OwnUX, so they’re never counted.

Question 38

What if we have more adapted users than our plan includes?

Accepted Answer

The Launch plan includes up to 2,000 adapted users a month and has a hard spending cap. Growth adds usage above its included amount. Overages are always shown openly and capped by default, so a busy month never brings a surprise bill.

Question 39

Will I pay twice if a product I use supports OwnUX?

Accepted Answer

No. Satin for People and Satin for Products are separate contracts. We won’t charge you and a product’s vendor for the same value unless there’s a distinct benefit, clearly disclosed.

Question 40

Why are prices in rupees and US dollars?

Accepted Answer

We’re starting with teams in India and remote contractors around the world, so plans for people are listed in both INR and USD. Taxes may apply. Plans for products are priced in USD.

Question 41

Is there a plan for teams?

Accepted Answer

Teams is planned for later. It adds shared team presets, admin policies, deployment and audit summaries, from ₹299 or $6 per seat a month, with a minimum of five seats.

Question 42

When can I start?

Accepted Answer

Satin’s private beta opens soon. Join it from the early access page, and we’ll invite people in small batches, starting with Jira Cloud and Linear users.

Question 43

Is Satin available today?

Accepted Answer

Not yet: Satin is pre-launch. Satin for People, the Chrome extension, is in development, with Personal mode for Jira Cloud being built now. The OwnUX SDK runs as an alpha in our Reference App, and the conformance CLI, ownux test, exists as v0.

Question 44

Can I sign up now?

Accepted Answer

Yes. Join the waitlist with the form on the early access page, or email hello@usesatin.com. We store your name, email and answers on the beta waitlist and use them only to invite you to the beta. You can ask us to delete them at any time.

Question 45

Which browsers will Satin support?

Accepted Answer

Chrome on desktop first, then Microsoft Edge, which shares Chrome’s engine. Safari and Firefox come after the public beta, once the Chrome and Edge builds are stable.

Question 46

Will there be a public beta?

Accepted Answer

Yes, if the closed beta passes its release gates, including zero wrong-entity writes and measured gains on real tasks. It’s planned as a listing in the Chrome Web Store. We don’t promise dates before we’ve seen those results.

Question 47

Where will Satin be available?

Accepted Answer

We’re starting with India and remote teams worldwide. Satin for People is a Chrome extension, so it works wherever you work in a supported app.

Questions, answered. Straight answers, including what isn’t built yet.

Every answer, in one place. Search, or pick a topic. Press / to jump to search.

Satin for People

Satin for Products

OwnUX

Privacy and security

Pricing

Availability

Not sure which Satin you need? Pick what describes you.

Some answers are always no. Design rules, not settings. They hold on every plan, in every app.

Where things stand. An honest status for everything these answers mention.

The words we use. Eight terms that come up in almost every answer, defined once.

Keep exploring.

Still have a question? Talk to us about your product, or read the specification.