White-Label Pathways
Your brand. The same rules.
Run Zynaut Pathways under your own name, for your own learners, workforce or programme — with the same record, the same ownership and the same limits on who can see what. The brand is yours. The rules are not configurable.
SameRecord.YourName.
What stays the same under your brand
These are not options.
- The person owns the record
- Nobody is scored, ranked or searched
- Sharing is consented and revocable
- Your data stays inside your deployment
- Your brandName, colours, domain and identity
- Your modulesEnable what your programme needs
- Your frameworksQualification frameworks and registries that belong to you
- Your reportingAggregates built for scrutiny, never a person
- The same rulesOwnership and consent are not configurable
A platform you can make your own
Everything your programme needs. Nothing it should not have.
What a deployment configures — and the one thing it cannot: the rules about whose record it is.
- BrandYour name, your colours, your domain and your identity throughout. To the people who use it, the deployment is yours.
- ModulesTurn on the stages and capabilities your programme uses — assessments, learning, guidance, opportunities — and leave off the ones it does not.
- RolesLearners, teachers, counsellors, placement staff and programme administrators, each with a view bounded by the same rules as everywhere else.
- Frameworks and registriesThe qualification frameworks, issuer registries and scheme definitions that belong to your place and programme, held by your deployment rather than by Pathways itself.
- IntegrationsConnections to the systems you already run, each under a declared purpose and a permission. Which integrations exist is stated per deployment, never claimed here.
- ReportingAggregate views of where a cohort or a programme stands, built so no individual can be picked out — and built for an auditor to read.
How a deployment happens
From scope to review, in five steps.
Five steps, each with something written down at the end of it.
1. Scope
Agree who the deployment serves, what it is for, and which rules apply — including the ones that cannot be changed.
2. Configure
Brand, modules, roles, frameworks, registries and integrations, set up against your scope and recorded.
3. Pilot
A bounded group uses it under defined conditions. What was learned is written down before anything opens wider.
4. Open
The deployment opens to the people it was scoped for, with onboarding for each role and a route to report what is wrong.
5. Review
In aggregate: what the programme built against what it set out to build. Then the scope is revisited, not assumed.
Built for your ecosystem
Different programmes. One record, the same rules.
Who a white-label deployment is for, and what each sees.
Schools
- A record that begins at school and leaves with the student
- Teachers issue evidence and see a class in aggregate
- Guardians by a recorded, endable permission
Colleges and universities
- Programme review against what was set out
- A placement office as an adviser a student chooses
- No search over students
Enterprises
- Workforce capability seen in aggregate
- The person still owns the record
- Internal moves the person initiates
Government programmes
- Aggregates built for scrutiny
- No league table, no route to an individual
- Rules a non-specialist can read
NGOs and foundations
- A record for people with only their own word to start
- Evidence from work, care and community counts
- Aggregates for funders, never a person
Your brand, the same rules
What a deployment cannot change.
A white-label deployment changes how Pathways looks and what it includes. It does not change whose record it is. The person owns it, sees all of it, chooses who sees what and can take it back; institutions see aggregates; nobody is scored, ranked or searched. Those rules are the product.
- The person owns the record, under any brand
- Aggregates only, for the institution
- No score, no ranking, no search
- Consent recorded, purpose stated, revocable
- Your data stays inside your deployment
Same record. Same rules. Your name on the door.
Deployments
BharatSamarth: the first white-label deployment
One deployment is recorded, and it is named here at the status it actually holds.
The version of Pathways being built for India, under its own name: the same record and the same rules about who can and cannot see it, with only the Indian qualification frameworks, issuer registries and scheme integrations belonging to it rather than to Pathways itself. This site once listed it as an offering in its own right; it is one branded instance of the flagship.
Status: In development
Active implementation exists. General availability is not claimed. An implementation exists for this market and is being built against. General availability is not claimed for it, and its progress does not imply the platform's.
No other deployment is named. A deployment appears on this site only when it exists and its owner has agreed to be named, and it carries its own status — the maturity of one instance is not the maturity of the platform.
- Your brandName, colours, domain
- Your modulesOnly what the programme needs
- Your frameworksHeld by your deployment
- Tenant-separatedNo route to another deployment
- The person owns the recordUnder any brand
- In developmentNo date and no price claimed
Questions people ask
White-label, in plain answers
What can we change, and what can we not?
You can change the brand, the modules, the roles, the frameworks and registries, the integrations and the reporting views. You cannot change whose record it is, who may see what, or the rule that nobody is scored, ranked or searched. Those are the product.
Is white-label Pathways available now?
Not yet. Pathways is in development: an implementation exists and is being built against, but it is not generally available and no date is claimed. One white-label deployment, BharatSamarth, is being built for India under the same status.
What does it cost?
Pricing is not published, for the same reason no date is: it is not finalised. When it is, the pricing page will say what each plan covers. A demo request is the way to talk about a specific programme now.
Does our data mix with anyone else's?
No. A deployment's records, registries and integrations belong to it, and there is no route from one deployment to another. The people in it own their records, the institution sees aggregates, and Zynaut engineers the platform without owning either.
Do we get reporting on individual learners?
No. Reporting is built as aggregates so no individual can be picked out, and it is built for an auditor to read. A view of one person reaches you only as a view that person chose to share. What is shown for very small groups is a rule still to be published.
Can we run our own qualification frameworks?
Yes. That is what the frameworks and registries configuration is for. The qualification frameworks, issuer registries and scheme definitions that belong to your place and programme are held by your deployment rather than by Pathways itself.
