VENTEX Pilot Network
PILOT 02 / OPERATIONAL RECORDTECHSERV ×
ORGANISATIONTECHSERV IMPEX SRL
TECHSERV ×
VENTEX Connect
TECHSERV is evaluating VENTEX Connect in an active controlled pilot across distributed field-service, support and device workflows.
CONTROLLED OPERATIONAL PILOT 02Operational Enterprise Pilot Partner
- LOCATION
- Bucharest, Romania
- YEAR
- 2026
- STATUS
- Active
- CLASSIFICATION
- AFFILIATED OPERATIONAL PILOT
Enterprise IT field service and technical support
Field service · infrastructure rollouts · operational IT supportTECHSERV IMPEX SRL has been registered in Bucharest since December 2005. Its publicly listed principal activity is the repair and maintenance of computers and communications equipment. Aggregated filing data reports 2025 revenue of RON 2,841,751 and an average headcount of 18; these figures describe the filing, not the future pilot scope.
Public professional profiles indicate Vodafone-facing IT support, continuity work, operating-system migrations, equipment replacement across shops and offices, and conferencing installations. Other historical profiles describe printer and multifunction-device support. These are public individual self-reports, not confirmation by the named customers or proof of current contracts.
For VENTEX, this context is relevant as a real operating environment: mobile and office-based work, multiple device classes, technical handovers, workforce changes and communication during live service activity. Pilot users, device classes and timing will only be published once jointly agreed.
Publicly reviewable company basis.
Registry and filing data remain separate from pilot status. They evidence the organisation, not the quality or security of VENTEX Connect.
- Founded
- 2 December 2005
- Registry identity
- CUI 18180664 · EUID ROONRC.J2005020245408
- Principal activity
- CAEN 9510 · repair and maintenance of computers and communication equipment
- 2025 filing
- RON 2,841,751 revenue · average headcount 18 Aggregated public filing data
Defined scope. No pre-empted outcomes.
These entries describe the current evaluation frame. Usage, quality and resilience outcomes will only appear once actually measured and contextualised.
What the pilot observes.
- 01Direct and group messaging
- 02Mission Rooms and protected file exchange
- 03Multi-device and secondary-device workflows
- 04Device revocation and local-data removal
- 05Onboarding, offboarding and administrative workflows
- 06Password change and account recovery
- 07Failure, reconnect and incident scenarios
- 08Hybrid session establishment for capable devices
- 09Double Ratchet session continuity
- 10Message lifecycle and deletion functions
Concrete observation objectives.
- 01Assess whether secure team communication remains usable across field-service and support handovers.
- 02Observe device replacement, revocation, recovery and offboarding in realistic operating workflows.
- 03Document failure, reconnect and compromised-device scenarios in a structured form.
Structured, bounded, reviewable.
- 01A pre-defined scope with named responsibilities and a controlled participant group.
- 02Scenario-based observation rather than blanket partner endorsement.
- 03Issues, reproduction, impact, remediation and re-test are recorded separately.
- 04Outcomes are published only after execution, review and approval.
From product to a reviewable learning cycle.
- 01VENTEX CONNECT
- 02CONTROLLED DEPLOYMENT
- 03TECHSERV
- 04EVIDENCE
- 05PRODUCT IMPROVEMENT
CURRENT, BOUNDARY and OPEN WORK remain separate.
- The company and its operational IT-service context are publicly evidenced.
- The pilot is active; no usage or outcome metrics have been published.
- The proposed scope uses only product workflows documented in the current Connect state.
- TECHSERV is organisationally connected to VENTEX through Mishu Ivanush and is therefore not an independent validator.
- Public staff profiles indicate operating contexts; they are not customer confirmations or evidence of current contracts.
- Connect's PQ component protects hybrid session establishment for capable devices; the following Double Ratchet is not continuously post-quantum secure.
- Agree participant group, device classes, pilot duration and escalation path.
- Document company approval for the name, profile and any official logo.
- Add substantiated operating observations only after pilot start and potential outcomes later.
What supports the profile — and what does not.
Primary sources, company-data aggregations, historical self-reports and VENTEX relationship disclosures are deliberately labelled as different evidence classes.
Identity, formation date, EUID, principal activity and public filing figures.
ListaFirmeCross-check of active status, activity and 2025 filing; management is displayed only by initials.
Termene.roIndicates Vodafone-facing team leadership, IT support, migrations and equipment replacement; not customer confirmation.
LinkedInHistorical indication of printer and multifunction-device service; not evidence of today's scope.
LinkedInTECHSERV and MOVADI appear in the same historical service-unit context. The listed authorisation is historical and does not prove a current partnership between the companies.
Romanian Ministry of FinanceVENTEX states that Mishu Ivanush is connected to TECHSERV and is also listed on the VENTEX organisation page.
VENTEXRELATIONSHIP NOTE / TRANSPARENCY
TECHSERV participates as an Operational Enterprise Pilot Partner in an active, controlled VENTEX Connect evaluation. The collaboration is neither an independent security audit, certification, security approval nor independent product validation.
Mishu Ivanush is connected to TECHSERV and is also listed within the VENTEX organisation. The pilot is therefore transparently classified as an affiliated operational pilot. Its evidence may address operational usability, not independent security assurance.