Ciright
V2X — Connected Mobility
Connected mobility needs trusted participants.
Program boundaries
What this area does — and does not — offer.
Ciright and Keyra describe hardware engineering, device identity, authorization and enterprise integration for connected mobility. This site does not certify V2X hardware, invent SKUs, or claim that an offering is deployed without configuration evidence.
Direct path
Compatible nearby endpoints exchange direct V2X messages under the applicable radio/message/trust profile. It must not gain synchronous dependencies on Ciright cloud, Keyra login, SS7/SMS, billing, human approval or a carrier-core round trip.
Network / application path
Approved connectivity and backhaul support permitted enrollment, credential operations, diagnostics, updates, fleet services and enterprise integration.
Identity types stay distinct
Subscriber authentication, person authentication, device binding, authorization, V2X certificate acceptance and physical ownership are separate concepts.
Signature ≠ safety
A valid signature does not establish sensor truth, accurate location, safe driving, ownership or authority for unrelated actions.
No website actuation
This corporate site and any illustrative simulator have no live braking, steering, traffic-signal or road-infrastructure control.
Audience entry
Start from your role.
OEM / Tier 1
Hardware-rooted trust modules, vehicle identity relationships and enterprise orchestration for platform programs.
Discuss a vehicle programCarrier
Participating connectivity for enrollment, credential operations, diagnostics and fleet services on the network path.
Review connectivity boundariesInfrastructure / agency
Roadside and intersection contexts with clear limits: no live signal control from the corporate website.
Explore infrastructure contextsFleet / micromobility
Fleet, motorcycle and micromobility configurations with VRU-aware scenario framing and pilot design.
See road-user coverageDeveloper
Interface status, sandbox honesty and production prerequisites — without fabricating interoperability.
Open developer status
Offering families
Coverage mapped; readiness labeled.
Prior names such as K-VTM, Trust Core/Connect, K-B2V, K-S2V, K-M2V and K-VRU are source-document concept references, not established shipping SKUs. Current public readiness defaults to Unverified until the product owner attaches evidence.
- Onboard / Vehicle Trust ModuleUnverified
Ciright Enterprise integration, offering records and authorized orchestration surfaces.
Keyra Hardware-rooted trust and sensitive-action authority where Keyra is in scope.
Prior name K-VTM is a source-document concept reference, not an established shipping SKU.
- Roadside infrastructureUnverified
Ciright Enterprise operations and inquiry routing for agency/operator engagement.
Keyra Credential and authority boundaries for authorized roadside contexts.
No live traffic-signal or road-infrastructure control from this website.
- Motorcycle and micromobilityUnverified
Ciright Program packaging and pilot intake for micromobility operators.
Keyra Device/person relationship and credential lifecycle where approved.
B2V is ambiguous across source material — bicycle-related vs building-related meanings must be spelled out per record. Marked Unverified until resolved.
- Hardware-rooted trustUnverified
Ciright Enterprise service contracts via approved api.ciright.com boundary.
Keyra Hardware-rooted identity and approval of sensitive actions.
Do not reuse subscriber network secrets as application signing keys.
- Person / vehicle / device relationshipsDocumented design
Ciright Canonical Core person, organization, subscription and asset records.
Keyra Binding and authorization for protected account contexts.
Administrative identity stays separate from operational pseudonymous credentials.
- Credential lifecycleUnverified
Ciright Enterprise enrollment and operational tooling on the network path.
Keyra Verification and resource authorization for protected functions.
Revocation limitations are explained honestly; no instantaneous global revocation promise.
- Participating telecom integrationProposed integration
Ciright Operator-facing engagement and dependency documentation.
Keyra Separates subscriber authentication from V2X trust credentials.
A SIM is not a direct radio.
- Enterprise operationsDocumented design
Ciright Fleet services, diagnostics, updates and CRM/Core synchronization where approved.
Keyra Protected workspace and approval boundaries.
Direct V2X message exchange must not depend on Ciright cloud round trips.
- Charging / parking / tolling / maintenance (separately authorized)Unverified
Ciright Discussable only where separately authorized commercial terms exist.
Keyra As applicable to authorized service scopes.
Availability is a separate business fact from engineering discussability.
- Sansar explanation / trainingUnverified
Ciright Spatial / training explanation where supported by approved materials.
Keyra Not automatically in scope.
Retain source distinction among Core, Applied, Radar, spatial offerings, Sansar and Keyra.
- Developers / integrationUnverified
Ciright Canonical developer destinations and production prerequisites.
Keyra Required for protected developer functions.
Proposed interfaces labeled proposed; sandbox states stay honest.
- Engineering and pilotsProposed integration
Ciright Owned next-step delivery for discovery, architecture review and pilot design.
Keyra Verification when protected pilot records are involved.
Accepted inquiry ≠ booked pilot. Scheduling confirmation is separate.
Explore the V2X area
Thirteen hubs. Distinct content.
- How it worksPlain-language V2V, V2I, V2N and V2P; direct versus network paths; equipment prerequisites; FAQ without certification claims.
- PlatformCapability families, identity/authority boundaries and where Ciright cloud participates — never as a dependency of direct radio safety messaging.
- HardwareConfiguration boundaries for onboard, roadside and VRU equipment. Exact profiles remain Unverified until product evidence is attached.
- VehiclesIndustry fit for cars, trucks/buses, motorcycles, bicycles, scooters and pedestrians — with supported versus configuration-specific limits labeled honestly.
- InfrastructureRoadside equipment contexts for agencies and operators. No live signal or infrastructure control from this website.
- Use casesSubstantive scenario families for discovery — illustrative unless a configuration-specific evidence record says otherwise.
- TelecomOperator dependencies and limits for the network path. A SIM is not a direct radio; subscriber secrets are not V2X signing keys.
- Trust & securityAuthenticity, authority, freshness and plausibility are separate. A valid signature is not sensor truth or safe actuation.
- DevelopersCanonical developer destinations and honest status for proposed versus available interfaces. No invented SDK readiness.
- Partners & pilotsApproved intake for engineering discovery, architecture review, integration assessment and controlled pilot design — without invented scheduling.
- ReadinessConfiguration-scoped readiness labels. Geography and standard versions recorded only when evidenced.
- ResourcesDeeper future-of-mobility editorial kept distinct from dated verified developments. Industry context is not Ciright certification.
Take a reliable next step.
Public education stays readable. Protected accounts, pilot records and privileged functions require Keyra verification. General corporate inquiry assurance policy is preserved until product/security owners change it.