Manage virtual machines
Create VMs and discover existing vm-bhyve guests. Configure CPU, RAM, disks, networks, ISO images and autostart.
α Alpha
My Hyve SCP
Your FreeBSD/bhyve hosts. One control panel.
Connect servers without reinstalling FreeBSD. Manage virtual machines, snapshots, backups and schedules from your browser.
ONE WORKSPACE
Your hosts, virtual machines and resource metrics in one place.
FreeBSD/bhyve · No host reinstall · Private alpha
01 / Hosts02 / CPU & memory03 / Virtual machines
SEE THE WORKFLOW
From your infrastructure to a single VM.
Explore the MY HYVE SCP interface: hosts, virtual machines, jobs, snapshots and backups.
Choose a step or select Next. Enlarge any screenshot to inspect details.
01 / 06
Complete infrastructure information.
Host availability, CPU and memory use, and VM counts on one page.
02 / 06
Monitor individual hosts.
System information, hardware and resources of the selected host.
03 / 06
Full VM management.
Virtual machine configuration, status and controls.
04 / 06
Monitor your jobs.
Operation progress, status and results.
05 / 06
Use snapshots to track changes.
Virtual machine snapshots and saved states in one section.
06 / 06
VM backups and recovery.
Virtual machine backups and recovery tools.
Ready to explore it in your own lab?
Tell us about your infrastructure to discuss joining the private test.
WHAT EXISTS TODAY
Tools for your daily workflows
Tested on a real FreeBSD/bhyve host.
VM creation and discovery of existing vm-bhyve guests
Configuration management and a browser console
Snapshots, backups and schedules
MFA, resource-scoped permissions and operation audit
This is not a new hypervisor. My Hyve SCP does not require you to reinstall FreeBSD or migrate your infrastructure to a specialized distribution. Install a lightweight agent on an existing or newly prepared FreeBSD/bhyve server and connect the host to MY HYVE SCP.
FEATURES
Everyday bhyve management in one place
From creating a virtual machine to recovering its state and managing team access.
Open a browser console
Built-in noVNC through an authorized panel connection. No direct public exposure of the host VNC port is required.
Keep a history of states
Hot and cold snapshots, branch history and the contents of each point. Return to a saved state while retaining the previous branch.
Back up your virtual machines
Local destinations, NFS v4 and SMB. Restore into the current VM or a new copy, including on another host. Optional archive encryption.
Schedule recurring work
VM groups, one-time and recurring runs, and time zones. Retention policies based on copy count and age.
Manage ZFS and networks
Pools, datasets and VM datastores. Compression and recordsize settings, supported VLAN switches and network status.
Monitor your resources
CPU, memory, network and disk activity history for hosts and VMs. Observed ZFS usage separate from virtual disk capacity.
Manage access
Users and groups, resource and action permissions. LDAP/LDAPS, OIDC, MFA and an audit log.
BACKUP AND RECOVERY
Save your VMs. Recover the state you need.
Use local or network storage, set schedules and restore VMs on the original host or another compatible host.
- Choose your destination
A local or mounted path, NFS v4 or SMB. Enrollment checks writing, reading and a checksum.
- Choose a recovery point
The latest or a historical point within a supported archive. Restore into the current VM or a new copy with new UUIDs and MAC addresses.
- Restore on another host
Import the archive, map networks and create a new VM on a compatible host. No connection to the original server is required.
- Encrypt archives when needed
Optional encryption of content and configuration. Keep your recovery key: decryption is impossible without it.
AUTOMATION
Set a schedule for a group of VMs.
Choose virtual machines, run frequency, capture mode and retention. Follow operation progress and results in Jobs.
- One-time, daily, weekly or monthly runs.
- Separate snapshot and export frequencies; hot or cold capture.
- Count and age retention. Deleting a schedule preserves completed backups.
Example policy
- Group
- Lab VMs
- Run
- Daily · 02:00
- Time zone
- Europe/Moscow
- Actions
- Snapshots and backups
- Retention
- 7 latest copies
- Choose VMs
- Set the schedule
- Review Jobs
ACCESS FOR YOUR TEAM
Bring your team. Assign the right access.
Organize sites and hosts by organization. Scope permissions to resources and actions, and track changes in the audit log.
Sign-in
Local users, LDAP/LDAPS and corporate OIDC.
MFA
TOTP for password sign-in; MFA assertions from the OIDC provider.
Permissions
Groups and permissions scoped to resources.
Audit
Access, settings, certificate changes and jobs.
PRODUCT READINESS
Capabilities and support conditions
As of October 9, 2026. Implemented workflows support defined configurations; production readiness is assessed separately.
| Capability | Status |
|---|---|
| VM management, configuration and consolevm-bhyve creation and discovery, power controls, hardware and noVNC. | Implemented |
| Monitoring, ZFS and networksMetric history, pools and datasets, and supported VLAN switches. | Implemented |
| Snapshots, backups and recoverySupported baseline workflows. Backup covers file disks in one ZFS filesystem. | Implemented |
| Schedules and archive encryptionVM groups, calendar schedules, retention and optional encryption. | Implemented |
| Corporate accessLDAP/LDAPS, OIDC, MFA, resource-scoped permissions and audit. | Implemented |
| Advanced recovery and history cleanupSpecific host profiles, TPM and dependencies require validation and approval. | With limitations |
| HA, replication, migration and libvirt-bhyveNot offered as active capabilities of the current release. | Unavailable |
HOW IT WORKS
How the bhyve control panel connects to FreeBSD
Central API and UI; host-local agents; outbound secure communication.
My Hyve SCP
MY HYVE Secure Control Panel
Agent
FreeBSD / bhyve
Agent
FreeBSD / bhyve
Agent
FreeBSD / bhyve
Connect with separated privileges
The network agent runs without root and initiates an outbound mTLS connection. A separate executor performs privileged actions. Host enrollment uses a one-time token, administrator approval and a certificate; trust can be revoked.
ABOUT MY HYVE
Built from a practical need.
MY HYVE began with a practical goal: make day-to-day bhyve administration more convenient and centralized, closer to the experience available with other virtualization platforms.
What to know before testing
Can I add new hosts?
Yes. Prepare a new FreeBSD/bhyve server, install the agent and connect the host to My Hyve SCP. Existing and new hosts can be managed together in the same control panel.
What is My Hyve SCP?
My Hyve SCP is a web control panel for managing FreeBSD/bhyve infrastructure. Connect existing hosts or add new ones. It brings host information, virtual machine inventory, resource metrics and job status into one browser interface. The product is currently in private alpha.
What can I see in the bhyve web interface?
Host overview, VM creation and configuration, a built-in console, snapshots and history branches, backups and schedules, ZFS, networks, metrics and jobs. The screenshots above show real MY HYVE SCP screens.
Which hosts can I connect?
The primary VM manager is vm-bhyve. The current target environment is FreeBSD 15 amd64, with the panel on Ubuntu Linux. Include your versions and lab details in the request; other configurations are reviewed before enrollment.
How does a snapshot differ from a backup?
A snapshot keeps a state on the local ZFS pool and lets you return to a selected point. It depends on the original storage. An archive backup can be stored separately; independent recovery requires an accessible archive and, when encrypted, the corresponding key.
Which storage configurations support backup?
Local and mounted paths, NFS v4 and SMB are supported. The baseline profile covers VM file disks in one ZFS filesystem. External disks, zvols and nested datasets are not automatically covered; compatibility is reviewed before testing.
Can I restore a VM on another host?
Existing archive import, scanning, network mapping and new VM creation on another host are implemented without contact with the original server. A compatible profile, archive and trust data are required; encrypted copies also need the key. Full disaster recovery after losing both the panel and original node still requires a separate test.
What does a hot snapshot preserve?
A hot snapshot is crash-consistent. RAM and application consistency are not captured automatically. A group run does not provide a simultaneous application state across multiple VMs.
Do I need to expose a VNC port to the internet?
No. Built-in noVNC uses an authorized connection through the API and agent to the host-local VNC service. Direct public exposure of the VNC port is not required.
How does user access work?
Local users and groups, LDAP/LDAPS and corporate OIDC are supported. Password sign-in uses TOTP MFA; OIDC requires acceptable MFA assertions from the provider. Permissions are scoped to resources and actions, and the API checks them when executing operations.
Can snapshot history be cleaned up automatically?
Manual, report-only and automatic modes support history age, count and budget policies. Advanced cleanup and dependency changes are disabled by default until the exact host and profile receive independent validation and approval.
Are HA, replication and migration available?
These capabilities are not offered in the current release. libvirt-bhyve integration is also temporarily disabled. The primary supported virtual machine manager is vm-bhyve.
How did MY HYVE start?
MY HYVE started from a practical need. I wanted a comfortable way to manage the bhyve hypervisors I use at work — with the kind of centralized experience I was already used to with other virtualization platforms. That idea grew into MY HYVE Secure Control Panel — a centralized management interface for existing FreeBSD/bhyve infrastructure.
Will there be a ready-to-install hypervisor platform?
That is part of the longer-term direction. The current priority is MY HYVE SCP itself: making the Secure Control Panel reliable and completing its core workflows for existing FreeBSD/bhyve environments. A ready-to-install platform for new infrastructure can follow once the SCP foundation is mature.
How can I try MY HYVE?
Use the short request form in the Alpha section or email hello@myhyvescp.com. Start with your FreeBSD/vm-bhyve versions, host and VM counts, and test goals. Detailed configuration can be discussed afterward.
Do I need to reinstall my FreeBSD hosts?
No. MY HYVE SCP is being built for existing FreeBSD/bhyve environments. The goal is to bring existing infrastructure under centralized visibility and management rather than require a new hypervisor installation.
Does MY HYVE manage hosts over SSH?
MY HYVE uses an agent running on each managed FreeBSD host. The agent communicates with MY HYVE SCP using outbound mTLS connections; host management is not based on arbitrary root SSH commands from the central server.
Is MY HYVE production-ready?
Not yet. MY HYVE SCP is currently Alpha. Core parts of the system are already working, while several architecture, security and operational workflows are still being completed and tested.
JOIN THE PRIVATE TEST
Your lab. Real tasks. Useful feedback.
We are looking for FreeBSD/bhyve administrators who want centralized visibility and are ready to share test results.
You have a test host
A separate FreeBSD/bhyve lab and verified backups for experiments.
You have a workflow to test
Existing VM discovery, multiple-host visibility or resource monitoring.
You can share feedback
Report errors and explain what helps or gets in the way.
How participation works
- Send a short request
Versions, lab size and your test goals.
- Review the environment
Discuss compatibility, access and test workflows.
- Connect and test
Once agreed: alpha access, agent enrollment and feedback on the results.
ALPHA
Private alpha. Tested on a real host.
We are accepting requests for individual private testing. Core workflows have been tested on a real FreeBSD/bhyve host; compatibility with your lab will be reviewed before enrollment. The alpha is not production-ready.
Start with your lab
Four fields to get acquainted. Detailed configuration can follow afterward.
Use a separate test environment and verified backups. The alpha may contain bugs and cause data loss or downtime.
You can also email us directly: hello@myhyvescp.com