
WOVENN › Product
Your data, kept apart and in your hands.
How WOVENN protects each company's records, and what it does and does not share.
Each company in its own vault. Only what an order needs crosses.
A brand's purchase order and the factory's production order exchange two fixed summaries. Nothing else crosses between companies.
- Styles and tech packs
- Purchase orders
- Retail price
- Target cost
- Its floor and lines
- Production orders
- Its other buyers
- Its own costs
Six things you can count on.
Kept apart
Each company in its own vault.
Never in search
Only the public site is indexed.
Yours to take
Download everything you hold.
Sign-in your way
Passkeys, company sign-on, allowed networks.
Partners see their part
Never your price or target cost.
Every change recorded
Who, what and when.
Each sees only what its job needs.

Everything here is live today.
Last updated 8 November 2026
Signing inTwo-step, passkeys, company sign-on
- One sign-in for every role, with each role checked against WOVENN’s own records on every request — never trusted from the browser.
- Two-step sign-in with an authenticator app or a passkey, and one-time recovery codes. An organization can require it of its whole team, or of its admins and anyone who manages access.
- A company can sign its people in through its own identity provider, by SAML or OpenID Connect, and require it. Its directory can add, change and remove people over SCIM, so leavers lose access the moment they leave.
- A company can keep its team to its own networks, such as its offices and VPN; from anywhere else its workspace does not open. Buyers’ and partners’ portals follow their own rules.
- Sessions end after 12 hours however active, and after the organization’s own idle time. Everyone can see their signed-in devices, sign any of them out, or sign out everywhere.
- Removing a person’s last role signs them out on every device.
Keeping organizations apartEach company under its own path
- Every organization’s records sit under its own path, and every read and write goes through one place that builds it from the signed-in organization.
- Partners and designers receive a style without its costs and prices — removed from what is sent, not only hidden on screen.
- Another system reaches WOVENN only through the public API, with a key an organization issues and can revoke, limited in what it may do and how often.
- WOVENN calls out only where a company switches it on: webhooks to an address it names, https only and never to a private or internal network, each delivery signed so the receiver can check it came from WOVENN.
EncryptionIn transit and at rest
- Every connection is HTTPS; browsers are told to use nothing else.
- Stored data is encrypted at rest by Google Cloud.
- Factory operators’ names and two-step sign-in secrets are also encrypted by WOVENN under its own key before they are stored, so a copy of the database holds neither.
The audit trailEvery change, who and when
- Every change made in WOVENN records who made it, from which device, what it was and whether it was done or refused.
- An organization’s admins search and export their own audit log, and can download everything the organization holds.
- Roles are the company’s own: each person’s access can be limited by season, category, buyer, partner, unit or line, can end on a date, and downloading is a right of its own.
- A copy goes to a separate log store that the application can add to but never change or delete, kept 400 days.
In the browserOnly WOVENN's scripts run
- A content security policy with a fresh code for every page lets only WOVENN’s own scripts run.
- WOVENN can’t be shown inside another site’s frame, and forms post nowhere but WOVENN.
- Requests are limited per person and per address, so a script or a stolen session can’t hammer the service.
Backups and recoveryAny minute of the last seven days
- The database can be read back as it was at any minute of the last seven days, and is backed up daily.
- The database is protected against deletion.
How WOVENN is builtChecked, tested, then released
- Every change is checked automatically for vulnerable dependencies, security flaws in the code and secrets, and a bill of materials of every component is produced.
- Dependency updates wait two weeks after release before they are taken.
- Changes go to a separate test environment first and are tested there by hand before release.
Sub-processorsWho processes data for WOVENN
The service providers that process data for WOVENN:
- Google Cloud and Firebase — website hosting, database, file storage, sign-in, background processing, logs and AI models (Vertex AI).
- Cloudflare — form verification (Turnstile).
- Resend — sending e-mail notifications.
Reporting a vulnerabilitysecurity@wovenn.world
If you think you have found a security problem in WOVENN, write to security@wovenn.world with what you found and how to reproduce it. Please don’t access other people’s data, degrade the service or share the problem publicly before it is fixed. We reply to every report.
The same address is in security.txt.
See WOVENN on one of your own styles.
An hour with us on styles like yours, from the first sketch to the store shelf.











