For companies

Reviewed paths for organizations building on U-net.

Companies can apply for official accounts, propose miniapps or web services, and work toward new attestation types through reviewed release flows — not a generic self-service directory.

Reviewed entry

Company, origin, manifest, support, and policy details give the network a concrete basis for trust.

Scoped reach

Programs connect organizations to holders without handing over unrelated identifiers or private device state.

Trust-sensitive changes

Profile, notification, attestation, and release changes stay under review when they affect holder expectations.

Programs are how external trust enters U-net

Each path defines what an organization can ask for, how holders see it, and when U-net should review changes.

01

Submit the surface

Provide the company profile, policy links, support details, proposed service, and any requested holder permissions.

02

Review the trust boundary

U-net checks origins, manifests, requested scopes, notification behavior, and attestation release details where applicable.

03

Operate with holder control

Approved providers receive scoped credentials and stay accountable to the permission model holders see in U-net.