LINKSPREED Opens Its Beta Program to More Trusted Testers
Applications for the Trusted Tester Program are now open. A verified UIID is required to apply, and access to pre-release UIID applications is granted through the identity layer itself.
Applications now open — a UIID is mandatory.
LINKSPREED is expanding the group of people who get early, hands-on access to new applications built on the UIID identity infrastructure. Until now, early access has been limited to a small internal circle of testers. From today, we are opening the Trusted Tester Program to a broader group of users, developers, security researchers and partner organizations who want to work with our products before they become generally available.
If you want to take part, send an email to [email protected], tell us which projects you are interested in, and include your UIID. Applications without a UIID will not be evaluated.
Why we are opening the program
UIID is not a single product. It is an identity layer, and an identity layer only proves itself when real people use it in real conditions — on their own devices, in their own networks, with their own habits and their own edge cases. Internal testing catches functional defects. It does not catch the things that matter most to us: whether a flow feels obvious the first time you see it, whether an error message actually helps, whether a recovery path works when you are stressed and in a hurry, or whether a feature behaves the same way on a five-year-old Android phone in one country as it does on a current desktop browser in another.
The portfolio of applications we are building on top of UIID has grown considerably. Several of these products are now at the stage where structured external feedback is more valuable than another internal iteration. Rather than run a series of separate, ad-hoc invitations, we are consolidating early access into one program with one entry point.
What a Trusted Tester actually does
Being a Trusted Tester is not a passive newsletter subscription. It is a working relationship. Accepted testers:
- Receive pre-release access to one or more applications before public availability, including builds that are deliberately incomplete.
- Use the software in real conditions rather than in a scripted demo — this is the part that produces the feedback we cannot generate ourselves.
- Report defects, friction and confusion through the channels we provide, including the things that are hard to articulate, such as “this step made me hesitate” or “I did not understand what this was asking me to confirm.”
- Discuss the product with our team, in structured feedback rounds for some projects and in direct written exchange for others.
- Keep unreleased information confidential for the duration of the program.
Testers are not obliged to find a fixed number of defects, write formal reports or dedicate a set number of hours per week. We would rather have honest, occasional, high-quality feedback than a filled-in template.
heroImage: ./uiid-trusted-tester-program/3.png
Every Trusted Tester signs an NDA
Access to unreleased software is granted under a non-disclosure agreement. This is not a formality, and we want to be transparent about why it exists.
Pre-release builds contain functionality that is not finished, interfaces that will change, and architectural details that are still being validated. Publishing screenshots, behavior or technical details of an unfinished identity product creates three concrete problems: it sets user expectations against a version that will never ship; it creates a misleading public record of how our security model works; and, in an identity system specifically, it can expose implementation detail before the corresponding hardening work is complete.
The NDA is therefore scoped to exactly that: unreleased material. It does not restrict a tester’s ability to discuss publicly released UIID features, to publish security research through our disclosure process, or to criticize our products once they ship. We are not asking testers to be advocates. We are asking them not to publish work in progress.
The NDA is sent after an application is accepted. Access is granted once it is signed and once the tester’s UIID has been verified.
The UIID requirement
A UIID is mandatory for every application. Please include it in your email.
This requirement is deliberate, and it is not administrative box-ticking. There are three reasons for it.
First, it is the product. The Trusted Tester Program exists to test applications built on the UIID identity layer. Access to those applications is granted through UIID itself. Without an identity, there is nothing for us to grant access to.
Second, it establishes accountability. A Trusted Tester receives unreleased software under a confidentiality agreement. That agreement has to attach to an identity that is stable, verifiable and controlled by the person signing it — not to an email address that can be discarded and re-registered in thirty seconds.
Third, it is how access is revoked. If a tester leaves the program, or a build has to be withdrawn, access is withdrawn at the identity layer. This is cleaner, faster and more auditable than maintaining separate invitation lists per project.
Applications that arrive without a UIID are not rejected with an explanation — they are simply not evaluated. Please include it.
If you do not yet hold a UIID, you can create one free of charge at uiid.me before applying.
Which projects can you apply for?
We do not publish a single static list of beta projects, because the set changes as products enter and leave the beta phase. Everything currently in beta can be found in three places:
| Source | What you will find | Address |
|---|---|---|
| Press releases | Formal announcements of new projects, capabilities and platform releases | Published through our usual channels |
| Blog | Product background, technical explanations and beta announcements | blog.linkspreed.com |
| Help Center | Documentation, setup guides and support articles for live and beta features | help.linkspreed.com |
Before you apply, look through those sources and decide which projects genuinely interest you. Then name them in your email.
This matters more than it might appear. We match testers to projects, not to the program as a whole. A tester who tells us they want to work on the developer tooling will be evaluated against that project’s needs; a tester who tells us they want to test the mobile identity experience will be evaluated against that one. An application that says “I am interested in everything” gives us nothing to match against and is significantly less likely to be accepted.
heroImage: ./uiid-trusted-tester-program/1.png
How to apply
Send an email to [email protected] containing:
- Your UIID — mandatory. Applications without it are not evaluated.
- The projects you are interested in — named specifically, based on what is currently in beta.
- Why those projects — one or two sentences is enough. Tell us what you would actually do with them.
- Your relevant context — your platform and devices, your technical background if any, and the country you would be testing from. Geographic spread is genuinely useful to us.
There is no deadline. Applications are reviewed on a rolling basis.
What happens after you apply
Applications are reviewed against the current needs of each project. Being accepted for one project does not automatically grant access to others, and being declined for one round does not remove you from consideration for later ones. We keep accepted applications on file and contact testers when a project that matches their stated interests enters the beta phase.
Accepted applicants receive the NDA, and access is provisioned against their UIID once it is signed.
We will not be able to accept every application. Some projects require a specific device, platform or professional context; others are limited in size on purpose, because a small group that is genuinely engaged produces better results than a large group that is not.
A note on what we expect from ourselves
Opening a beta program creates obligations in both directions. Testers give us their time, their attention and their honest judgement. In return we commit to reading what they send us, to responding to it, and to telling them what happened to their feedback — including when we decided not to act on it and why.
A tester who reports something and never hears back has been asked for a favor, not invited into a program. We intend to run this the second way.
Ready to apply?
Email [email protected] with your UIID and the projects you are interested in.
Don’t have a UIID yet? Create one at uiid.me.
Looking for the current beta projects? Check blog.linkspreed.com and help.linkspreed.com.