Adopting companies
Businesses that would rather not hold personal data at all.
Workstreams serving them9
- Proxy identifiers
- Deploying into your own cloud
- SEO and content
- PR / SNS
- Sales
- Help content
- CS / QA
- Feature requests
- Billing
ONENYM TEAM
15 workstreams, one context each.
OneNym.id keeps personal data out of the systems that run a business: what would hurt if it leaked is never held there in the first place. Every workstream exists to keep that design intact.
WHO IT IS FOR
Who OneNym.id is built for
The company adopting it, the developers wiring it in, the people answerable for security, and the person the data is about.
Developers
The people connecting it to systems that already exist.
Workstreams serving them4
- Proxy identifiers
- Purpose-limited API
- MCP / API
- Help content
Security and legal
The people who have to answer for it afterwards.
Workstreams serving them5
- Encrypted vault
- Purpose-limited API
- Audit trail
- Feature requests
- Security
Individuals
The person the data is actually about.
Workstreams serving them1
- Encrypted vault
THE ROSTER
The workstreams behind OneNym.id
One workstream, one objective. What follows is not a snapshot of who is busy today — it is the set of workstreams this product needs.
Holding the data
5
The core: keeping personal data apart from the systems that use it. Nothing else matters if this slips.
Proxy identifiers
Hand business systems a proxy ID, and never the person behind it.
Companies Developers
Encrypted vault
Store the personal data encrypted, and keep the keys in few hands.
Legal Individuals
Purpose-limited API
Return data only against a stated purpose, never just because someone asked.
Developers Legal
Deploying into your own cloud
Run inside the customer's own Azure, not only ours.
Companies
Audit trail
Make who looked, when, and why answerable after the fact.
Legal
Connecting it up
1
What the screens can do should be reachable from outside tools and AI agents too.
MCP / API
Let outside tools and AI agents work with OneNym.id's features and data.
Developers
Getting found, and sold
3
Building it is not enough. These carry someone from never having heard of it to using it.
SEO and content
Be findable, and say what it does before anyone has to ask.
Companies
PR / SNS
Keep saying, outside, what this is actually for.
Companies
Sales
Find the right prospects, make the case, and keep the thread alive. An agent researches and drafts; a person has the conversation.
Companies
Standing behind it
2
Nobody gets stuck after they start, and what they tell us turns into a fix.
Help content
Let people solve it themselves instead of waiting for support.
Developers Companies
CS / QA
Answer what comes in, and turn it into a fault that cannot happen twice.
Companies
Deciding what comes next
1
The workstream that runs before anything is built: what was asked for, read against how it is used.
Feature requests
Gather what users ask for and what usage shows is missing, and decide what gets built next.
Companies Legal
Holding it up
3
It stays up, it stays protected, and the billing adds up.
Server watch / log analytics
Find errors and slowness first, so nobody meets them mid-task.
Security
Check on every change that what must be protected still is.
Legal
Billing
Bill what was used, correctly and on time.
Companies
THE LOOP
How one workstream moves
Every workstream turns the same way. A person sets the objective, an agent does the work, and the decision to ship comes back to a person.
See the eight steps-
01
Set the objective
An adopting company, a developer or the legal side — who it gets better for, and how. People decide that.
-
02
Open the session
One session per workstream, started with the code conventions, the past decisions and the current numbers already in hand. A workstream that turns into a long piece of work gets a branch of its own.
-
03
Build it, review it
Changes go out small, through review and an automated test suite, onto a staging environment — and a person makes the call to put them live.
-
04
Check the number
How much personal data actually left the business systems. We do not measure this in features shipped.
ONE AT A TIME
That is how this much stays covered
The workstreams do not all run at once — one moves at a time. Features can be added without widening what we hold because one conversation only ever holds one workstream.
Instructions do not mix
Work on the purpose-limited API does not queue behind the audit trail. The protective workstreams never end up last.
What is shared, and what is not
Code conventions and the quality bar are the same across the whole project. What stays separate is the mission and the context around it.
Context survives
Decisions accumulate inside each workstream, so picking it up again does not start from zero.
Long ones get their own branch
When a workstream turns into a long piece of work, it moves to a branch of its own. The work is kept apart the same way the context is.
Ship small
Many small changes rather than one large one — each inside a range we can roll back.
STILL OURS
What people decide
More agents does not move the responsibility. That stays with people.
-
How much we hold
Which data we take, and how much ever goes back out. People draw that line before anything is built.
-
What we will not do
We can do more than before. That is exactly why the decisions worth our time are the ones to decline.
-
What we promise clients
Dates, estimates, quality. A company promises those, and a company is people.
-
What goes to production
Review and merge. A person presses the last button.
LET'S TALK
Your product can move the same way.
The way we run OneNym.id is the way we run the work clients bring us. Tell us what you need moved first.
Talk to us