Customer-owned
You choose the compatible Linux VM, own the provider account and bill, and administer DNS, TLS, firewall, backups and recovery.
Relay Host · Portable Linux VM playbook
Your Relay Host. Your cloud account.
Run Relay Host on a compatible Linux VM in the cloud account you choose, with checked release-matched assets, no cloud credentials handed to Orionfold and no product secrets placed in cloud user-data.
Secret-free setup
Cloud user-data prepares the machine only. Model keys, Relay Host licenses and customer credentials are added after bootstrap.
Receipt-driven
The playbook verifies the release, writes a preparation receipt and keeps the exact configuration available for review and recovery.
Portable, not provider-managed
A repeatable machine contract. Not a cloud service.
The playbook prepares a compatible Linux VM and records what it did. It does not create your cloud account, choose a provider for you, configure every provider-specific firewall or operate the server after handoff. You retain the infrastructure bill, administrator responsibility and failure boundary.
DigitalOcean is the current named live-verified path. A portable Linux contract makes other compatible VMs reviewable; it does not turn untested providers into verified promises.
Portable contract
A compatible Linux VM can be evaluated against the checked, release-matched machine contract.
Provider-verified
Orionfold has a dated receipt for an exact provider topology. DigitalOcean is the first.
Not yet provider-verified
A provider may satisfy the portable contract, but Orionfold does not make a provider-specific promise before its own receipt passes.
From VM to governed Host
Seven checks keep preparation, authority and operation separate.
- 01
Choose a compatible VM
Start with Ubuntu 24.04 x64 and at least 2 vCPU, 4 GB RAM and 80 GB disk. This baseline prepares Relay Host; local-model workloads may require materially more memory or GPU capacity.
- 02
Pin the Relay release
Use the exact supported release named by the guide. The playbook and deployment assets move together, so a floating branch cannot silently change the machine contract.
- 03
Prepare without product secrets
Run the checked cloud-init preparation with no cloud-provider token, model API key, Relay license, customer credential or recovery secret embedded in user-data.
- 04
Verify the preparation receipt
Confirm the prepared state and its release identity before adding a Host license, model runtime or customer data. A receipt is evidence of preparation, not an uptime promise.
- 05
Configure Host authority
Free Relay Core can operate directly and one unmanaged Cell. The paid Relay Host right authorizes managed multi-Cell lifecycle within the signed capacity you bought.
- 06
Add secrets after bootstrap
Transfer the Host license, model credentials and recovery material over an authenticated operator channel, then keep encrypted recovery outside the Host.
- 07
Operate, update and recover
Use the release-matched guide for installation, access, updates, export and recovery. Existing managed Cells continue if the annual license lapses; new managed Cell creation and forward paid updates stop.
Free operating path
Relay Core + one unmanaged Cell
Use Relay directly and operate one unmanaged Cell without buying Relay Host. You still own the machine, credentials, data and operating work.
Paid managed authority
One Host · up to ten managed Cells
Relay Host adds signed managed lifecycle authority, capacity enforcement, forward Host updates and support for $1,499/year. Premium Packs remain separate.
Review Relay Host pricing and terms →Portable playbook FAQ
Ownership stays explicit.
Is this hosted by Orionfold?
No. Relay Host runs in infrastructure you or your customer controls. Orionfold does not own the provider account, operate the VM or promise its uptime.
Does Orionfold need my cloud API key?
No. You create the VM in your provider account. The portable playbook prepares that machine and deliberately excludes provider credentials and product secrets from cloud user-data.
Does this mean every cloud provider is verified?
No. The portable contract targets a compatible Linux VM. DigitalOcean is the only named provider with a current accepted live receipt; other providers need their own dated proof before Orionfold names them as verified.
What is free and what requires Relay Host?
Relay Core, direct use and one unmanaged Cell remain free. The paid Relay Host license covers managed multi-Cell lifecycle for one Host with up to ten managed Cells. Premium Packs remain separate.
What happens if my Relay Host license ends?
Existing managed Cells remain startable, stoppable, exportable, recoverable and purgeable. New managed Cell creation and forward paid updates stop; compatible critical-security fixes remain included.
Can I use an existing server?
Yes, if it meets the documented Linux, architecture, storage, networking and administration prerequisites. Review it as carefully as a new VM because the playbook does not erase unrelated services or make an unsafe host trustworthy.
Is the minimum VM enough for a local model?
Not necessarily. The 2 vCPU, 4 GB RAM and 80 GB disk baseline is for Relay Host preparation and lightweight operation. Size local models separately for their memory, accelerator and throughput needs.