Skip to content

About

Enterprise workload mobility starts with honest offline export.

Topics

Resources

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Latest commit

 

History

71 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Transiva — Community Edition

CI Latest release Go 1.27+ License: Apache 2.0

Book a demo 30-day PoC Quickstart

Transiva - Escape the renewal trap. Export becomes a job.

Escape the renewal trap. Export becomes a job.

Enterprise workload mobility starts with honest offline export. Transiva Community Edition is a Go control plane that discovers, inventories, and orchestrates workload exports from VMware vSphere and Nutanix AHV, handing artifacts to h2kvm for conversion. Fleet jobs run over REST and CLI — Apache-2.0, no guest agent, source VM untouched until cutover.

2 source hypervisors (CE) · 1 workflow for both · 0 guest agents · Resumable export jobs · CLI + REST

Platform docs · Nutanix guide · Out of Nutanix in minutes · OpenAPI · Community vs Platform


Why Transiva

When this happens… Transiva gives you…
Every hypervisor renewal buries your VMs deeper in someone else's proprietary API Discovery via the provider API and an inventory of workloads before you export anything
Getting out means a spreadsheet, a maintenance window and a pile of one-off ovftool invocations Export as a job: interactive CLI for one-offs, transivad plus REST for fleets
An export fails mid-transfer and starts again from zero Resumable jobs via transivad and REST
Part of the estate is on vSphere, part on Nutanix AHV Two sources, one workflow: same CLI, same jobs, same output layout
Nobody will approve an agent in production guests Offline artifacts, no guest agent, the source VM untouched until cutover
The export is only step one of the exit A clean hand-off: artifacts flow into h2kvm and GuestKit, then KVM, KubeVirt and Zeus OS

Capabilities at a glance: Discover, Export, Automate, Hand off


Transiva vs ovftool scripts

Transiva vs ovftool scripts: from one-off commands to export jobs

Transiva CE ovftool scripts (the usual way out)
Unit of work An export job you submit, track and resume One ovftool invocation per VM
Fleet control transivad REST daemon and transivactl (list, export, info, submit) Shell loops and a spreadsheet
Failure mid-transfer Resumable job Run it again
Sources VMware vSphere and Nutanix AHV, one workflow VMware products
Discovery Provider API discovery and inventory before export Not part of the tool
API REST, described in openapi.yaml Command line only
Choose ovftool when You have a handful of one-time exports from vSphere and a script is enough

How it fits together

Export with Transiva, convert with h2kvm

VMware to KubeVirt, four tools one path: Transiva exports, h2kvm converts and deploys, GuestKit assures, Zorvia operates, each with Community and Enterprise tiers.

Export with Transiva → convert with h2kvm → assure with GuestKit → operate on Zeus OS or the open-source Zorvia. Each is a separate tool; Zorvia's own importer is Experimental.

Where this fits: the Zyvor suite

transiva (discover · export) → h2kvm (convert to QCOW2) → GuestKit (inspect · repair) → KVM · libvirt · KubeVirt → Zeus OS (day-2).

Methodology: Discover → Assess → Convert → Deploy → Operate → Optimize. This repo covers discover + export in CE. Full hypervisor-exit route → · The diagram and stage table: docs/suite-fit.md.


Quickstart

Requires Go 1.27+ to build (go.mod), and a vSphere or Nutanix AHV endpoint to export from.

git clone https://github.com/zyvorai/zyvor-transiva.git
cd zyvor-transiva
./scripts/build.sh

cp config.example.yaml config.yaml
# edit config.yaml for your vSphere endpoint
./bin/hyperexport --config config.yaml

Nutanix AHV, the daemon and REST API, and the binaries table are in docs/quick-start.md; the Nutanix walkthrough is docs/nutanix.md. Legacy hyper* binaries remain compatibility aliases for at least one major release.

Binary Role
transivaexport (compat: hyperexport) Interactive CLI exports (vSphere, Nutanix, …)
transivad (compat: hypervisord) REST API daemon
transivactl (compat: hyperctl) Job control — list, export, info, submit
nutanix-pickup Standalone Nutanix discovery/pickup

The example config's daemon address is 0.0.0.0:8080 (daemon_addr in config.example.yaml).


The renewal trap — escaped with an API

Every hypervisor renewal buries your VMs deeper in someone else’s proprietary API. Getting out usually means a spreadsheet, a maintenance window, and a pile of one-off ovftool invocations. Transiva turns that into a job.

2 source hypervisors (CE) 1 workflow for both 0 guest agents
Apache-2.0 CLI + REST Offline export — source VM untouched
Discover and inventory
Discover via the provider API and inventory workloads before you export anything.
The renewal trap
Resumable exports
Export fails mid-transfer? Resumable jobs via transivad and REST, not a restart from zero.
Quick start
Two sources, one workflow
vSphere and Nutanix AHV behave identically: same CLI, same jobs, same output layout.
Nutanix guide
Offline, no guest agent
Offline artifacts; the source VM is untouched until cutover.
Why teams start here
Scriptable end to end
Interactive CLI for one-offs; daemon plus REST for fleets. Source, Docker and RPMs.
OpenAPI
Clean handoff
Artifacts flow into h2kvm and GuestKit, then KVM, KubeVirt and Zeus OS.
Where it fits


Community Edition vs Transiva Platform

CE proves export. Platform runs the hypervisor-exit program.

CE is free forever for labs — two sources, CLI, GitHub Issues. If you are moving an estate: no CBT, no waves, no SSO, no named owner on cutover night. Buy Platform.

Community Edition (this repo) Transiva Platform
Who it is for Labs · PoC · single-host Platform / SRE leads · 50–10,000+ VMs
Sources vSphere, Nutanix AHV 10–11 providers — Hyper-V, AWS, Azure, GCP, OCI, OpenStack, Proxmox, KubeVirt, …
Incremental Full exports only CBT + smart fallback — windows that fit change freeze
Security Config-file credentials Vault · SSO/OIDC/SAML · RBAC · audit · air-gap packs
Support GitHub Issues SLA · workshops · hypervisor-exit PS

Full feature matrix →

Bring us your worst estate. 30-day PoC · Platform demo · Pricing


Development

make test
make lint

PRs welcome. Security reports → SECURITY.md.

Support the project

Transiva Community Edition is free and open source, maintained by Susant Sahani at Zyvor AI Labs.

Production / Platform Book a demo · 30-day PoC · sales@zyvor.dev
Community GitHub Issues
General info@zyvor.dev

Related repositories (h2kvm, guestkit, chimera, netevd), social assets and more: docs/support-and-related.md.

Documentation

Topic Doc
Every page, in one list docs/documentation-map.md
Quick start, binaries, Nutanix docs/quick-start.md · docs/nutanix.md
The renewal trap and why teams start here docs/renewal-trap.md
Where Transiva fits in the Zyvor suite docs/suite-fit.md
Community Edition vs Platform docs/ce-vs-enterprise.md (canonical matrix)
REST API openapi.yaml

Maturity

Maturity (honest): CE covers two sources and full exports (no CBT, no multi-provider dashboard). Ten-plus providers, waves, SSO, and cutover-night support are Transiva Platform — feature matrix.

Legacy hyper* binaries remain compatibility aliases for at least one major release.


Part of the Zyvor stack

Product Role next to Transiva
Transiva Discover and export VMs from vSphere and Nutanix AHV, as jobs
Scout Pairs with Transiva before export: read-only readiness scoring and migration-wave planning
h2kvm Converts Transiva's exported artifacts to QCOW2 and deploys them
GuestKit Inspects and repairs the converted guests
Zorvia Open-source KubeVirt platform to operate the workloads on

→ zyvor.dev


Donate

Free under Apache-2.0. If it helps you, you can donate any amount you like: https://rzp.io/rzp/utwdYh3. A donation is voluntary and supports development and maintenance. It is not a purchase: it buys no support, SLA, features, priority or license, and it is not tax-deductible (Zyvor AI Labs Private Limited is a company, not a charity). Support contracts are separate: sales@zyvor.dev.

License

Transiva Community Edition is free and open source under the Apache License, Version 2.0 (see NOTICE). You may use, modify, and run it for personal, lab, and commercial production use at no charge, subject to Apache-2.0 (preserve notices / NOTICE where required). That does not change.

Zyvor Enterprise adds what production teams ask for: supported releases, deployment and upgrade guidance, priority incident triage, a named technical contact and 24x7 critical intake. Plans and terms: docs/SUBSCRIPTION-MODEL.md · Pricing · sales@zyvor.dev.

Security reports → SECURITY.md.


Bring us your worst estate

Book a demo 30-day PoC Pricing Contact sales Star on GitHub

About

Enterprise workload mobility starts with honest offline export.

Topics

Resources

Security policy

Stars

4 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages